| 1 |
Hello, All. |
| 2 |
|
| 3 |
On Tue, Jan 29, 2019 at 09:32:19 -0700, Grant Taylor wrote: |
| 4 |
> On 01/29/2019 09:08 AM, Peter Humphrey wrote: |
| 5 |
> > I'd rather not have to create an initramfs if I can avoid it. Would it |
| 6 |
> > be sensible to start the raid volume by putting an mdadm --assemble |
| 7 |
> > command into, say, /etc/local.d/raid.start? The machine doesn't boot |
| 8 |
> > from /dev/md0. |
| 9 |
|
| 10 |
> Drive by comment. |
| 11 |
|
| 12 |
> I thought there was a kernel option / command line parameter that |
| 13 |
> enabled the kernel to automatically assemble arrays as it's |
| 14 |
> initializing. Would something like that work for you? |
| 15 |
|
| 16 |
> I have no idea where that is in the context of what you're working on. |
| 17 |
|
| 18 |
I use mdadm with a RAID-1 pair of SSDs, without an initramfs (YUCK!). |
| 19 |
My root partition is on the RAID. |
| 20 |
|
| 21 |
For this, the kernel needs to be able to assemble the drives into the |
| 22 |
raid at booting up time, and for that you need version 0.90 metadata. |
| 23 |
(Or, at least, you did back in 2017.) |
| 24 |
|
| 25 |
My command for building my array was: |
| 26 |
|
| 27 |
# mdadm --create /dev/md2 --level=1 --raid-devices=2 \ |
| 28 |
--metadata=0.90 /dev/nvme0n1p2 /dev/nvme1n1p2. |
| 29 |
|
| 30 |
However, there's another quirk which bit me: something in the Gentoo |
| 31 |
installation disk took it upon itself to renumber my /dev/md2 to |
| 32 |
/dev/md127. I raised bug #539162 for this, but it was decided not to |
| 33 |
fix it. (This was back in February 2015.) |
| 34 |
|
| 35 |
> -- |
| 36 |
> Grant. . . . |
| 37 |
> unix || die |
| 38 |
|
| 39 |
-- |
| 40 |
Alan Mackenzie (Nuremberg, Germany). |
Archives