Bug 804654 - kernel > 3.2.10 does not see my /home raid 1 partition and blocks at boot
Summary: kernel > 3.2.10 does not see my /home raid 1 partition and blocks at boot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-19 14:16 UTC by ypagani
Modified: 2012-03-21 10:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 10:06:18 UTC
Type: ---


Attachments (Terms of Use)

Description ypagani 2012-03-19 14:16:42 UTC
Description of problem:

I have a soft raid 1 partition for my /home. The raid partitions have the fd flag (as indicated by fdisk -l).

The kernel 3.2.10 does not see it and blocks at boot because of selinux relabelling. After a minut, the system asks me to give the root password to fix the problem or ^D to continue.

When I hit Ctrl+D, the system can not boot.
When I give the root password, it seems that my raid partitions are not detected.


I tried to add the rd.md.uuid and rd.dm.uuid parameters, but it did not work.

The kernel 3.2.9-2 boots my system without problems.

Version-Release number of selected component (if applicable):

kernel-3.2.9-2.fc16
kernel-3.2.10-3.fc16
mdadm-3.2.3-6.fc16

I don't know which other informations are relevant so if more details are needed I will happily give them.

Comment 1 ypagani 2012-03-21 08:24:31 UTC
I just tried with the kernel 3.3.0-2.fc16 and I have the same problem.
The message is :

Dependency failed. Aborted start of /home
Dependency failed. Aborted start of Relabel all filesystems, if necessary
Dependency. failed. Aborted start of Mark the need to relabel after reboot
Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode.


To continue the boot I need to do :
mdadm --assemble --scan
mount -a
and the systemctl default

It appears that the required "mdadm --assemble --scan" is not launched. But I don't know if it dues to a missed dependency in initrd or a systemD problem.

Comment 2 ypagani 2012-03-21 10:06:18 UTC
after doing a "mdadm --detail --scan > /etc/mdadm.conf" and a reboot all is working.

sorry for the noise


Note You need to log in before you can comment on or make changes to this bug.