FS#27574 - [mdadm] complains 'not enough to start the array' during boot, but assembles just fine
Attached to Project:
Arch Linux
Opened by Simon Wydooghe (HyperBaton) - Wednesday, 14 December 2011, 15:05 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 15 December 2011, 13:15 GMT
Opened by Simon Wydooghe (HyperBaton) - Wednesday, 14 December 2011, 15:05 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 15 December 2011, 13:15 GMT
|
Details
Description:
When booting, I get this boot info on my screen: ... :: Running Hook [mdadm] mdadm: /dev/md1 has been started with 2 drives. mdadm: /dev/md0 assembled from 2 drives - not enough to start the array. ... /dev/md1 is my raid1 root filesystem and /dev/md0 is my raid5 data filesystem. When booted, md0 is mounted and assembled as it should be, so I'm not sure why I'm getting this info during boot. Additional info: In /etc/mkinitcpio.conf, I have these settings: MODULES="raid1 radeon" HOOKS="base udev autodetect pata mdadm filesystems" In /etc/mdadm.conf, I have the following: DEVICE partitions ARRAY /dev/md1 metadata=0.90 UUID=e87063ec:2d555021:52419904:51489ef3 ARRAY /dev/md0 metadata=0.90 UUID=17ab166a:3ebcdc94:5c1158ab:0b0c6d11 Let me know if I can help out with other info, logs, etc. |
This task depends upon
Closed by Dave Reisner (falconindy)
Thursday, 15 December 2011, 13:15 GMT
Reason for closing: Not a bug
Additional comments about closing: see comments
Thursday, 15 December 2011, 13:15 GMT
Reason for closing: Not a bug
Additional comments about closing: see comments
Comment by
Dave Reisner (falconindy) -
Thursday, 15 December 2011, 01:42 GMT
Comment by
Simon Wydooghe (HyperBaton) -
Thursday, 15 December 2011, 07:39 GMT
Comment by
Dave Reisner (falconindy) -
Thursday, 15 December 2011, 10:51 GMT
Comment by
Simon Wydooghe (HyperBaton) -
Thursday, 15 December 2011, 13:06 GMT
Do you have multiple types of disk controllers, or are _all_ disks
(particularly in /dev/md0) attached to a PATA controller?
All 6 disks in the raid5 /dev/md0 are attached to the onboard SATA
controller. The 2 disks for my root raid1 /dev/md1 are attached to
the onboard PATA controller.
I'll bet this goes away if you add the sata hook to your config
and regenerate.
That did fix it indeed. Thanks a lot and sorry for the bug report.
Should have asked this in forum instead probably.