Summary: | raid devices not detected as expected | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | RWeber <r.weber> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED NEEDINFO | ||
Severity: | normal | ||
Priority: | Low | ||
Version: | 2006.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
RWeber
2006-12-15 10:23:35 UTC
i cant read your mind ... you didnt really say what the problem is, you just show a bunch of raid stuff on your machine the output shows that before the reboot, there are md[0-3] but afterwards there are md[0-2,4] (no md3). I'd wager that 'md3' has a wrong minor number. examine /dev/sda4 with mdadm -E and see what persistant minor there is. got ya ... not a userspace bug vapier: no i meant that it's probably a human-error. See comment #2. Sorry for the 'hidden' problem description. Exactly, md4 should actually be md3. I did a mdadm -E on all drives now. Here is the result: # Major Minor 0 8 1 0 active sync /dev/sda1 0 8 2 0 active sync /dev/sda2 0 8 3 0 active sync /dev/sda3 0 8 4 0 active sync /dev/sda4 The funny thing is, that md0-2 are build as expected. I did the Raid creation on the same way for all nodes (md0 to md3). What exactly did you reopen this bug for? Check the node for sdb4 which is faulty: <snip> md4 : active raid1 sdb4[1] sda4[2](F) 46114496 blocks [2/1] [_U] </snip> you where right. I found preferred minor is set wrong for sda4. Thanks! |