Boot failure with root on /dev/md* (raid)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mdadm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: mdadm
Description: Ubuntu 11.04
Release: 11.04
Package: mdadm
Version: 3.1.4+8efb9d1ub
There are several bugs relating to boot failures when the root partition is on an mdadm managed RAID array, however none of them seem to describe the problem I am seeing with 11.04.
Some context:
- Ubuntu 11.04 x86_64 upgraded from 10.10 x86_64 using update-manager
- three raid arrays across 9 partitions on three physical disks - /dev/md125 (raid10), /dev/md126 (raid5), /dev/md127 (raid10)
- root partition is /dev/md127p3 with /boot on /dev/md127p1
- fstab and grub.cfg refer to partitions using UUID, not device names
Expected behaviour:
System boots from root partition on an mdadm managed raid array
Actual behaviour:
When booting with rroot partition on an mdadm managed raid array the process fails, with the udevd daemon hanging right after the init-premount and local-top scripts execute. The error message, repeatead for each array, is:
"udevd[PID] worker [PID] unexpectedly returned with status 0x0100"
From my debugging efforts it would seem that there is an issue with how mdadm 3.x communicates with udevd, or the other way round. While the arrays get detected, assembling them at boot causes udevd to hang. The only way to solve this problem for the moment was (for me at least) to force-downgrade mdadm from 3.1.4+8efb9d1ub
Identical issue exists on my system when started from the LiveCD for 11.04.
If I install mdadm from 11.04 repos *and* leave udev running the udev daemon hangs a few seconds after "mdadm --assemble --scan" is executed. If I disable the udev service first, all raid arrays are assembled and started within a second or two. Again, downgrading mdadm to 2.6.7.1-1ubuntu16 solves the problem.
The very same setup previously worked flawless both in Ubuntu 10.04 LTS and 10.10.
| ptashek (ptashek) wrote | #1 |
| trendle (trendleforum) wrote | #2 |
| molostoff (molostoff) wrote | #3 |
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in mdadm (Ubuntu): | |
| status: | New → Confirmed |
I think I'm being plagued by the same issue. Like you I was using 10.04 LTS in the first place with mdadm.
However in 10.04LTS I had upgraded my mdadm to 3.1.4+8efb9d1ubuntu and I've had that running for some time.
It is now my misfortune to have chosen to upgrade to 11.04, there goes another few days of my life :-(
The upgrade was a complete bust, and stopped working.
I've now tried to do a fresh install of the ubuntu alternative install disk on a new clean HD (but the mdadm RAID-6 is still connected inside the box).
So now I get these udevd fail messages then the system hangs completely. So now I'll need to rip it down again.