On Tuesday, 29 January 2019 16:08:27 GMT Peter Humphrey wrote: > On Tuesday, 29 January 2019 09:20:46 GMT Mick wrote: > > Hello Mick, > > --->8 > > > Do you have CONFIG_MD_RAID1 (or whatever it should be these days) built in > > your kernel? > > Yes, I have, but something else was missing: CONFIG_DM_RAID=y. This is in > the SCSI section, which I'd overlooked (I hadn't needed it before because > the main storage is an NVMe drive). After setting that and rebooting, mdadm > --create is working as expected.
Good! I had assumed this was already selected. ;-) > > You need to update your initramfs after you configure your array, so your > > kernel knows what to assemble at boot time when it doesn't yet have access > > to your mdadm.conf. > > I'd rather not have to create an initramfs if I can avoid it. Would it be > sensible to start the raid volume by putting an mdadm --assemble command > into, say, /etc/local.d/raid.start? The machine doesn't boot from /dev/md0. I think yes, as long as OS filesystem(s) are not on the array, or not mounted until the array has been assembled with the correct mdadm.config. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
