Skip to contentSkip to conversation

mdraid autodetect partially failing after disk replacement

DISCUSSION Ricky Burgin 2 participants 2 messages May 9, 2013 – May 10, 2013 MD RAID

lore
Share & tools
lore
#0 lore raw

Hello again,

Little bit of progress since I last dropped a message in (sorry for the duplicate, didn't think the initial one got through).

The kernel has mdraid built into it and all disks are using 0.90 superblocks, all 'fd' partitions, but only 2 or 4 disks are being recognised and applied to the freshly created raid array which works fine when mounted on any other OS.

Any suggestions for what could cause disks to be overlooked by mdraid before the root device is even attempted to be mounted would be very helpful, I'm now totally at a loss as to what to do from here.

Kind regards,
Ricky Burgin

#1 lore raw
Quoted 14 lines · Ricky Burgin

Hello again,

Little bit of progress since I last dropped a message in (sorry for the duplicate, didn't think the initial one got through).

The kernel has mdraid built into it and all disks are using 0.90 superblocks, all 'fd' partitions, but only 2 or 4 disks are being recognised and applied to the freshly created raid array which works fine when mounted on any other OS.

Any suggestions for what could cause disks to be overlooked by mdraid before the root device is even attempted to be mounted would be very helpful, I'm now totally at a loss as to what to do from here.

Quoted 6 lines

Kind regards,
Ricky Burgin
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Is it possible that you still have 1.x superblocks on two drives that are being detected before the 0.9 superblocks on this OS? I don't know if this is or is not possible, but that is the only strangeness I see from your prior posts etc.

You should probably boot that version of CentOS's rescue mode and see if you have the same issues there...

Sam