Mailinglist Archive: opensuse-bugs (2150 mails)

< Previous Next >
[Bug 749732] systemd: if fsck fails, system continues to boot.

https://bugzilla.novell.com/show_bug.cgi?id=749732

https://bugzilla.novell.com/show_bug.cgi?id=749732#c9


Thomas Blume <thomas.blume@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |thomas.blume@xxxxxxxx

--- Comment #9 from Thomas Blume <thomas.blume@xxxxxxxx> 2014-04-15 09:21:28
UTC ---
This is fixed in the current openSUSE Version.
I've checked on openSUSE 13.1.
The failing fsck goes into the emergency shell:

-->--
+++ echo -e '\e[1mUnlocking root (/dev/sda2)\e[m'
Unlocking root (/dev/sda2)
[...]
+++ cryptsetup --tries=1 luksOpen /dev/sda2 root
Enter passphrase for /dev/sda2:
[ 21.980267] sha256_ssse3: Using SSSE3 optimized SHA-256 implementation
[ 22.137189] bio: create slab <bio-1> at 1
[ 22.419649] bio: create slab <bio-1> at 1
+++ ret=0
+++ return 0
[...]
+++ fsck -t ext4 -V -a /dev/disk/by-id/dm-name-root
fsck from util-linux 2.23.2
[/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/mapper/root
fsck.ext4: Bad magic number in super-block while trying to open
/dev/mapper/root
/dev/mapper/root:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystemGive root password for maintenance
(or type Control-D to continue):
--<--

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >