Arch Linux

shelbydz

Member

Registered: 2014-03-16

Posts: 58

several journalctl errors, failed to startup, but everything works

I all,
when i boot up, I get several errors and then Im prompted to log into recovery mode by systemctl. I can also bypass and continue the bootup, which succeeds.

The errors in journalctl are:

Jan 27 16:26:20 systemd-fsck[241]: fsck failed with error code 8.
Jan 27 16:26:20 systemd[1]: Failed to mount /boot.
Jan 27 16:26:20 systemd[1]: Dependency failed for Local File Systems.
Jan 27 16:26:20 rpc.statd[276]: Failed to open directory sm: No such file or directory
Jan 27 16:26:20 rpc.statd[276]: failed to create RPC listeners, exiting
Jan 27 16:26:20 systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 27 16:26:25 systemd[261]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
Jan 27 16:27:50 systemd[1]: Timed out waiting for device sys-subsystem-net-devices-enp3so.device.
Jan 27 16:27:50 systemd[1]: Dependency failed for dhcpcd on enp3so.

I've also pulled the surrounding journal entries out, and that's available here:
http://pastebin.com/K8NFS2pF

These all seem unrelated and sort of random. The weird thing is once i continue with the boot, everything is fine and all these systems work; /boot is mounted, NFS works, my NIC is connected. Anyone have thoughts on fixing these? Or should I even be worried?

Thanks,

Leonid.I

Member

From: Aethyr

Registered: 2009-03-22

Posts: 999

Re: several journalctl errors, failed to startup, but everything works

Well, for starters, you apparently have plymouth.service enabled (?); disabling it will most likely get rid of the /bin/plymouth error.

I'd be worried about the /boot complaint. Can you post your fstab?

---

Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd

shelbydz

Member

Registered: 2014-03-16

Posts: 58

Re: several journalctl errors, failed to startup, but everything works

Here's the fstab:

#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/sde2 UUID=f34b2965-0dbd-4959-874b-1cb0b68f3f32
LABEL=root              /               ext4            rw,relatime,data=ordered        0 1

# /dev/sde1 UUID=145010cb-3b85-419f-9110-ea4de1f098c8
LABEL=boot              /boot           ext4            rw,relatime,data=ordered        0 2

# /dev/sda2 UUID=6c205833-2baf-43fd-b7cf-402f74c4f642
LABEL=var               /var            ext4            rw,relatime,data=ordered        0 2

# /dev/sda3 UUID=f9413cd7-1627-4b04-8ae5-3d6c4605f715
LABEL=home              /home           ext4            rw,relatime,data=ordered        0 2

# /dev/md127 UUID=b1bc4fa9-4eda-4f8d-baf3-c412e0ca1060
LABEL=raid              /media/raid     ext4            rw,relatime,stripe=32,data=ordered      0 2

# /dev/sda1 UUID=0c3341a9-4794-4b98-9cf1-0c662406a03f
/dev/sdc1               none            swap            defaults        0 0

Stupid thing is, if I tell systemctl to continue booting and ignore the errors /boot mounts automatically

$ls /boot
initramfs-linux-fallback.img  initramfs-linux.img  lost+found  syslinux  vmlinuz-linux

Is systemctl just failing out because it reached a certain number of errors on bootup?
thx