[Bug 316670] Re: Raid10 array not assembled at boot, all disks are marked as spare
sbeattie at ubuntu.com
Fri Apr 17 15:36:26 UTC 2009
On Fri, Apr 17, 2009 at 12:59:18PM -0000, lunomad wrote:
> Just adding my experience here, not sure if it is related.
> I upgraded last night to the Jaunty Release Candidate.
> Gdebi indicates that my installed mdadm is the same version as the AMD64
> version from http://people.ubuntu.com/~kirkland/316670/
> My root is on a regular sata disk, and I mount sdb1 and sdc1 as a Raid 1
> mdadm+lvm2 (as /dev/md0 and /lvm/lvm-raid/homelv) on /home
> The default upgrade did not find my md0, and instead puts sdc1 into a
> false md_d0.
> Every time I boot, I have to drop into a console, execute mdadm
> --assemble --scan and manually mount the /dev/lvm-raid/homelv . These
> steps work, except my md0 is degraded to just one disk (sdb1)
Are you able to hot-add back /dev/sdc1 to the array (e.g. mdadm /dev/md_d0
--add /dev/sdc1)? If so, after successfully resync'ing, does the following
boot still drop you to the busybox shell? Also, before you're dropped
to the shell, are you being asked to boot in degraded mode (the timeout
while waiting for the root filesystem to come up is long, but the boot
degraded question timeout is quite short)?
> I checked /proc/mdstat before the upgrade and everything was fine, so
> I'm wondering if this is the same bug or a different one?
This is likely a separate bug, please open a new one (though feel
free to report the bug number here). Thanks!
<sbeattie at ubuntu.com>
Raid10 array not assembled at boot, all disks are marked as spare
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
More information about the kernel-bugs