Bug 487965

Summary: No boot with mdadm 3.x
Product: [Fedora] Fedora Reporter: Nicolas Mailhot <nicolas.mailhot>
Component: mdadmAssignee: Doug Ledford <dledford>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: bruno, dledford, krnlbg, sander
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-18 17:10:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 446451    
Attachments:
Description Flags
kernel logs none

Description Nicolas Mailhot 2009-03-01 19:54:34 UTC
My /boot is on a raid-1 /dev/md0 device (everything else is lvm-ed over /dev/md1)

Since the mdadm update the boot process fails after the handover from the kernel to init. /boot can not be mounted. When I log-in at the error prompt I always find one of the two pieces of /dev/md0 mounted as /dev/md127 and the other as /dev/md0

Manually stoping /dev/md127 and /dev/md0, then re-assembling /dev/md0 and remounting pretty much everything else permits a successful init 5

Till the next reboot :(

Comment 1 Nicolas Mailhot 2009-03-01 19:58:54 UTC
Created attachment 333660 [details]
kernel logs

Comment 2 Sander Hoentjen 2009-03-04 14:19:30 UTC
exactly the same here, only i can't seem to start with the newer kernel at all, I still use an f10 kernel

Comment 3 Vlad 2009-03-13 18:19:34 UTC
I have the same proplem, after upgrade f10 to f11 alpha.

Comment 4 Bruno Wolff III 2009-03-15 14:59:41 UTC
As a work around try removing /etc/udev/rules.d/70-mdadm-assemble.rules .
I have been doing that since getting mdadm 3.
This still has problems if a device gets booted out of an array, as udev will try to start separate arrays with the failed devices. If this happens, you can use mdadm to add them back in and reboot.

Comment 5 Doug Ledford 2009-03-18 17:10:43 UTC

*** This bug has been marked as a duplicate of bug 488038 ***

Comment 6 Vlad 2009-03-31 19:16:20 UTC
It seems to fixed for me in bunch of last updates.