https://bugzilla.novell.com/show_bug.cgi?id=843317 https://bugzilla.novell.com/show_bug.cgi?id=843317#c0 Summary: (systemd-)fsck hangs at boot, system unbootable Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Yarny@public-files.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=560908) --> (http://bugzilla.novell.com/attachment.cgi?id=560908) packages updated/installed before bug occured User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 After I called "zypper patch ; zypper update" on my laptop today, it refused to reboot: shutdown went fine, but after grub and initrd showed their output, systemd indicated that it is waiting for several fsck processes. The final lines on the screen read something like
Starting File System Check on /dev/toshibasysvg/tmp Starting File System Check on /dev/toshibasysvg/home
Reproducible: Always Ctrl-Alt-Del works and causes a reboot. With fsck.mode=skip in the kernel command line the system boots as expected. With systemd's debug-shell.service enabled, I was able to look into the status of one of the fsck services while the boot process hangs:
systemd-fsck@dev-toshibasysvg-tmp.service - File System Check on /dev/toshibasysvg/tmp Loaded: loaded (/usr/lib/systemd/system/systemd-fsck@.service; static) Active: activating (start) since Mon, 2013-09-30 20:06:02 CEST; 1min 59s ago Docs: man:systemd-fsck@.service(8) Main PID: 579 (systemd-fsck) CGroup: name=systemd:/system/systemd-fsck@.service/dev-toshibasysvg-tmp ├ 579 /usr/lib/systemd/systemd-fsck /dev/toshibasysvg/tm... └ 580 /sbin/fsck -a -T -l -M -C5 /dev/toshibasysvg/tmp
Sep 30 20:06:02 toshiba.site systemd[1]: Starting File System Check on /dev/toshibasysvg/tmp... Then I rebooted with systemd.unit=emergency.target and issued both commands manually (the second with -C5 replaced by -C1) --- they exited instantly and fsck reported that the filesystem is clean.
/dev/toshibasysvg/tmp /tmp ext4 acl,user_xattr,relatime 1 2 /dev/toshibasysvg/home /home ext4 acl,user_xattr,relatime 1 2 /dev/disk/by-id/scsi-SATA_Hitachi_HTS54323121204E2M312BL2SGM6S-part1 /boot ext2 acl,user_xattr,relatime,nodev,nosuid 1 2 The lvm volume group "toshibasysvg" resides on the second (luks-encrypted)
Additional information: My system has three filesystems which are to be fsck'ed after the root-fs is mounted. Corresponding lines in fstab read: partition of my harddisk. However, I don't think luks/lvm affect this problem in any way since they are all loaded by the initrd. Before the bug occured, I called "zypper patch ; zypper up" to install some updated. Attached you find the relevant lines of /var/log/zypp/history. I didn't modify the system in any other way since the last successfull boot (without fsck.mode=skip). I'm having two more machines around here, and I tried to find out if a particular patch to be installed by zypper is causing this problem. After installing all patches one by one on these machines the bug did not show up there. The only difference between my affected laptop and those non-affected machines is that my laptop is a 64bit system while the non-affected machines are 32bit. Sorry, I have no idea what exactly is causing this bug. -- 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.