| 1 |
On Tuesday, 29 January 2019 09:20:46 GMT Mick wrote: |
| 2 |
|
| 3 |
Hello Mick, |
| 4 |
|
| 5 |
--->8 |
| 6 |
|
| 7 |
> Do you have CONFIG_MD_RAID1 (or whatever it should be these days) built in |
| 8 |
> your kernel? |
| 9 |
|
| 10 |
Yes, I have, but something else was missing: CONFIG_DM_RAID=y. This is in the |
| 11 |
SCSI section, which I'd overlooked (I hadn't needed it before because the main |
| 12 |
storage is an NVMe drive). After setting that and rebooting, mdadm --create is |
| 13 |
working as expected. |
| 14 |
|
| 15 |
The wiki needs a small addition. I submitted a bug against it but was told not |
| 16 |
to use bugs for this purpose: I should use the wiki page's discussion page. I |
| 17 |
see more head-scratchery coming on... |
| 18 |
|
| 19 |
--->8 |
| 20 |
|
| 21 |
> You need to update your initramfs after you configure your array, so your |
| 22 |
> kernel knows what to assemble at boot time when it doesn't yet have access |
| 23 |
> to your mdadm.conf. |
| 24 |
|
| 25 |
I'd rather not have to create an initramfs if I can avoid it. Would it be |
| 26 |
sensible to start the raid volume by putting an mdadm --assemble command into, |
| 27 |
say, /etc/local.d/raid.start? The machine doesn't boot from /dev/md0. |
| 28 |
|
| 29 |
-- |
| 30 |
Regards, |
| 31 |
Peter. |
Archives