Arch Linux

jlmr

Member

Registered: 2014-10-26

Posts: 14

System always starts fsck's at boot and can't start normally.

First of all, let me say that this forum is awesome. I've just started my first real ArchLinux experiment and you guys have helped me out so much already!

Anyway, my system keeps starting fsck's at boot. It then starts counting to 1 minute and 30 seconds, after which it stops the fsck and drops into into emergency mode. I can only boot by passing the "fsck.mode=force" parameter to the kernel from the boot manager.

I copied what I think are the relevant lines from journalctl:

Oct 28 20:18:33 argon systemd[1]: Starting EFI System Partition Automount.
Oct 28 20:18:33 argon systemd[1]: Set up automount EFI System Partition Automount.
Oct 28 20:18:33 argon systemd[1]: Expecting device dev-disk-by\x2duuid-6a7e8bc0\x2d2e45\x2d4915\x2da0df\x2dc2b53783831e.device...
Oct 28 20:18:33 argon systemd[1]: Expecting device dev-disk-by\x2duuid-e784d1a6\x2d648a\x2d423f\x2d9fd2\x2de8b5975672d4.device...
Oct 28 20:18:33 argon systemd[1]: Expecting device dev-disk-by\x2duuid-4631\x2d3940.device...
Oct 28 20:18:33 argon systemd[1]: Expecting device dev-disk-by\x2duuid-bc7d204d\x2df19b\x2d4238\x2da539\x2dccee44b83a7c.device...
Oct 28 20:18:33 argon kernel: EXT4-fs (dm-0): re-mounted. Opts: discard,data=ordered
Oct 28 20:18:33 argon systemd[1]: Created slice system-lvm2\x2dpvscan.slice.
Oct 28 20:18:33 argon systemd[1]: Starting LVM2 PV scan on device 8:18...
Oct 28 20:18:33 argon systemd[1]: Starting LVM2 metadata daemon...
Oct 28 20:18:33 argon systemd[1]: Started LVM2 metadata daemon.
Oct 28 20:18:33 argon systemd[1]: Found device Crucial_CT256MX100SSD1 EFI\x20system\x20partition.
Oct 28 20:18:33 argon systemd[1]: Starting File System Check on /dev/disk/by-uuid/4631-3940...
Oct 28 20:18:33 argon systemd[1]: Starting LVM2 PV scan on device 8:34...
Oct 28 20:18:33 argon lvmetad[221]: Cannot lock lockfile [/run/lvmetad.pid], error was [Resource temporarily unavailable]
Oct 28 20:18:33 argon systemd-fsck[225]: fsck.fat 3.0.26 (2014-03-07)
Oct 28 20:18:33 argon systemd-fsck[225]: /dev/sda2: 176 files, 51065/97280 clusters
Oct 28 20:18:33 argon systemd[1]: Started File System Check on /dev/disk/by-uuid/4631-3940.
Oct 28 20:18:33 argon systemd[1]: Mounting /boot...
Oct 28 20:18:34 argon systemd[1]: Found device /dev/disk/by-uuid/6a7e8bc0-2e45-4915-a0df-c2b53783831e.
Oct 28 20:18:34 argon systemd[1]: Starting File System Check on /dev/disk/by-uuid/6a7e8bc0-2e45-4915-a0df-c2b53783831e...
Oct 28 20:18:34 argon systemd[1]: Mounted /boot.
Oct 28 20:18:34 argon systemd-fsck[256]: /dev/mapper/SSDGroup-lvolhome: clean, 10177/12976128 files, 3039756/51897344 blocks
Oct 28 20:18:34 argon systemd[1]: Started File System Check on /dev/disk/by-uuid/6a7e8bc0-2e45-4915-a0df-c2b53783831e.
Oct 28 20:18:34 argon systemd[1]: Mounting /home.
Oct 28 20:20:03 argon systemd[1]: Job dev-disk-by\x2duuid-bc7d204d\x2df19b\x2d4238\x2da539\x2dccee44b83a7c.device/start timed out.
Oct 28 20:20:03 argon systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-bc7d204d\x2df19b\x2d4238\x2da539\x2dccee44b83a7c.device.
Oct 28 20:20:03 argon systemd[1]: Dependency failed for /mnt/media.
Oct 28 20:20:03 argon systemd[1]: Dependency failed for Local File Systems.
Oct 28 20:20:03 argon systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Oct 28 20:20:03 argon systemd[1]: Dependency failed for /var/lib/mpd/music.
Oct 28 20:20:03 argon systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/bc7d204d-f19b-4238-a539-ccee44b83a7c.
Oct 28 20:20:03 argon systemd[1]: Job dev-disk-by\x2duuid-e784d1a6\x2d648a\x2d423f\x2d9fd2\x2de8b5975672d4.device/start timed out.
Oct 28 20:20:03 argon systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-e784d1a6\x2d648a\x2d423f\x2d9fd2\x2de8b5975672d4.device.
Oct 28 20:20:03 argon systemd[1]: Dependency failed for /backup.
Oct 28 20:20:03 argon systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/e784d1a6-648a-423f-9fd2-e8b5975672d4.

I hope you can help me fix the problem or further diagnose it.

Spider.007

Member

Registered: 2004-06-20

Posts: 1,175

Re: System always starts fsck's at boot and can't start normally.

Oct 28 20:20:03 argon systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-bc7d204d\x2df19b\x2d4238\x2da539\x2dccee44b83a7c.device.

It seems there is a problem mounting /home. What device do you mount there; and does that exist when you end up in the rescue-shell?

jlmr

Member

Registered: 2014-10-26

Posts: 14

Re: System always starts fsck's at boot and can't start normally.

Hi,

Sorry for the long delay: my system suddenly booted normally a couple of times. Now it hung again. When I enter the rescue-shell, I can normally access /home and all files located therein. On home (and almost everywhere else) I mount a LVM Logical Volume.