Thread (2 messages) 2 messages, 2 authors, 2013-05-10

Re: mdraid autodetect partially failing after disk replacement

From: Sam Bingner <hidden>
Date: 2013-05-10 04:08:44

On May 8, 2013, at 3:20 PM, Ricky Burgin [off-list ref] wrote:
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
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help