FS#34705 - systemd: fails to boot from software raid (md,mdadm)

Attached to Project: AUR web interface
Opened by Daan van Rossum (drrossum) - Tuesday, 09 April 2013, 16:51 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 09 April 2013, 17:14 GMT
Task Type Bug Report
Category Backend
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 2.0.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

with Systemd-200 I can't boot from software raid, md-raid1. This setup has been working flawlessly since 2009. All packages up-to-date.

this is the boot message:
----
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/md1 ...
:: performing fsck on '/dev/md1'
fsck.ext2: Invalid argument while trying to open /dev/md1
/dev/md1:
The superblock could not be read or does not describe a correct ext2
...
...
You are now being dropped into an emergency shell.
----

From that shell, `cat /proc/mdstat` shows all arrays in place correctly. Note, that md1 is an ext4 file system, not ext2. I guess, they were not present yet at the time fsck starts???

Turning off fsck with the fastboot kernel parameter results in an error saying that /dev/md1 is not available (sorry, I'll try to reproduce and make a photo of the screen with the exact error message).

Reverting back to systemd-198-2 fixed the issue.
This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 09 April 2013, 17:14 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#34706 
Comment by Dave Reisner (falconindy) - Tuesday, 09 April 2013, 17:14 GMT
Please please please please please do not open multiple bug reports. Tasks can be moved.

Loading...