You are not logged in.
I have two sata disks configured using ICH8R firmware fakeraid on an Intel board in Raid1 (mirror), and I use dmraid to activate them. When rc.conf was changed to include the following:
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="yes"
this worked fine for a few weeks. However, as of yesterday, it appears that mdadm runs before dmraid during boot. From dmesg:
..
[ 6.106011] md: bind<sdc>
[ 6.109667] md: bind<sdd>
[ 6.111597] mdadm[581]: segfault at 2c ip 0000000000424795 sp 00007fffbaea8810 error 4 in mdadm[400000+61000]
..
[ 7.106830] device-mapper: uevent: version 1.0.3
[ 7.107150] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com
[ 7.121061] device-mapper: table: 253:0: mirror: Device lookup failure
[ 7.121362] device-mapper: ioctl: error adding target to table
..
Then, I have to reverse what mdadm has done before dmraid will activate my array:
# dmraid -ay
RAID set "isw_dhejfidjg_FAILSAFE" was not activated
ERROR: device "isw_dhejfidjg_FAILSAFE" could not be found
# mdadm -S /dev/md127
mdadm: stopped /dev/md127
# dmraid -ay
RAID set "isw_dhejfidjg_FAILSAFE" was activated
device "isw_dhejfidjg_FAILSAFE" is now registered with dmeventd for monitoring
RAID set "isw_dhejfidjg_FAILSAFEp1" was activated
I do not know what has changed to cause this behavior. I have not added anything to modprobe or mkinitcpio. Does anyone know how to stop mdadm from binding during boot? Thank you.
Last edited by meop (2011-08-01 13:49:49)
Offline
You could try this: mdadm (RAID5) - how disble auto assemble on boot ?
Offline
Thank you for replying. That does disable both mdadm and device-mapper. This:
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="yes"
still works.
Last edited by meop (2011-08-01 13:49:19)
Offline