Arch Linux

simplisticways

Member

Registered: 2015-12-03

Posts: 49

Computer fails on booting every second or third boot.

Hi guys!

My build is:
GPU: Nvidia GTX1070
CPU: AMD Ryzen 5 1600X
Kernel:  4.11.2-1-ARCH 4.11.2-1-ARCH
Xorg-server: 1.19.3
Nvidia: 381.22-2
RAM: 16gb Ripjaws ddr4

Computer fails on booting every second or third boot. Not sure whats the problem also I shouldn't have plymouth so the error is even stranger to me.

Sep 28 16:54:47 hardwork audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-lvmetad comm="s>
Sep 28 16:54:47 hardwork systemd[1]: systemd-rfkill.socket: Succeeded.
Sep 28 16:54:47 hardwork systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Sep 28 16:54:47 hardwork systemd[1]: Mounting /home/userus/Storage...
Sep 28 16:54:47 hardwork systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Sep 28 16:54:47 hardwork mount[631]: mount: /home/userus/Storage: /dev/sdb1 already mounted on /boot.
Sep 28 16:54:47 hardwork systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) be>
Sep 28 16:54:47 hardwork systemd[1]: Stopping LVM2 metadata daemon...
Sep 28 16:54:47 hardwork systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Sep 28 16:54:47 hardwork systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Sep 28 16:54:47 hardwork systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Sep 28 16:54:47 hardwork systemd[1]: Condition check resulted in Create System Users being skipped.
Sep 28 16:54:47 hardwork systemd[1]: lvm2-lvmetad.service: Succeeded.
Sep 28 16:54:47 hardwork systemd[1]: Stopped LVM2 metadata daemon.
Sep 28 16:54:47 hardwork systemd[1]: home-userus-Storage.mount: Mount process exited, code=exited, status=32/n/a
Sep 28 16:54:47 hardwork systemd[1]: home-userus-Storage.mount: Failed with result 'exit-code'.
Sep 28 16:54:47 hardwork systemd[1]: Failed to mount /home/userus/Storage.
Sep 28 16:54:47 hardwork systemd[1]: Dependency failed for Local File Systems.
Sep 28 16:54:47 hardwork systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Sep 28 16:54:47 hardwork systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Sep 28 16:54:47 hardwork systemd[1]: systemd-ask-password-console.path: Succeeded.
Sep 28 16:54:47 hardwork systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Sep 28 16:54:47 hardwork systemd[1]: systemd-ask-password-wall.path: Succeeded.
Sep 28 16:54:47 hardwork systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Sep 28 16:54:47 hardwork audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=emergency comm="sys>
Sep 28 16:54:47 hardwork systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Sep 28 16:54:47 hardwork systemd[1]: Started Emergency Shell.
Sep 28 16:54:47 hardwork systemd[1]: Reached target Emergency Mode.
Sep 28 16:54:47 hardwork systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
Sep 28 16:54:47 hardwork systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
Sep 28 16:54:47 hardwork systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Sep 28 16:54:47 hardwork systemd[1]: Condition check resulted in Update is Completed being skipped.
Sep 28 16:54:47 hardwork systemd[632]: emergency.service: Executable /bin/plymouth missing, skipping: No such file or dir>
Sep 28 16:54:47 hardwork kernel: audit: type=1130 audit(1569678887.608:16): pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
Sep 28 16:55:06 hardwork systemd[1]: Removed slice system-getty.slice.
Sep 28 16:55:06 hardwork systemd[1]: Stopped target Local Encrypted Volumes.
Sep 28 16:55:06 hardwork systemd[1]: Stopped target Emergency Mode.
Sep 28 16:55:06 hardwork systemd[1]: Stopped target Login Prompts.
Sep 28 16:55:06 hardwork systemd[1]: Stopped target Network is Online.
Sep 28 16:55:06 hardwork systemd[1]: Stopped target Network.
Sep 28 16:55:06 hardwork systemd[1]: Stopped target Paths.
Sep 28 16:55:06 hardwork systemd[1]: Stopped target Remote File Systems.
Sep 28 16:55:06 hardwork systemd[1]: Stopped target Slices.
Sep 28 16:55:06 hardwork systemd[1]: Removed slice User and Session Slice.
Sep 28 16:55:06 hardwork systemd[1]: Stopped target Sockets.
Sep 28 16:55:06 hardwork systemd[1]: Stopped target Timers.
Sep 28 16:55:06 hardwork systemd[1]: lvm2-lvmpolld.socket: Succeeded.
Sep 28 16:55:06 hardwork systemd[1]: Closed LVM2 poll daemon socket.
Sep 28 16:55:06 hardwork systemd[1]: Unmounting /boot...
Sep 28 16:55:06 hardwork systemd[1]: Unmounting Temporary Directory (/tmp)...
Sep 28 16:55:06 hardwork systemd[1]: Stopping Emergency Shell...
Sep 28 16:55:06 hardwork systemd[1]: Starting Generate shutdown-ramfs...
Sep 28 16:55:06 hardwork systemd[1]: systemd-binfmt.service: Succeeded.
Sep 28 16:55:06 hardwork systemd[1]: Stopped Set Up Additional Binary Formats.
Sep 28 16:55:06 hardwork audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-binfmt

c00ter

Member

From: Alaskan in Washington State

Registered: 2014-08-28

Posts: 421

Re: Computer fails on booting every second or third boot.

Have you considered https://bugs.archlinux.org/task/63697?p … ng=systemd ?

Downgrading to the SystemD 242-series fixed this bug for me, for the time being.

---

UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn

2ManyDogs

Forum Fellow

Registered: 2012-01-15

Posts: 4,648

Re: Computer fails on booting every second or third boot.

Please edit your post and use [ code ] tags when posting output.

https://wiki.archlinux.org/index.php/Co … s_and_code
https://bbs.archlinux.org/help.php#bbcode

c00ter

Member

From: Alaskan in Washington State

Registered: 2014-08-28

Posts: 421

Re: Computer fails on booting every second or third boot.

You're also running a dated xorg and very old kernel. Any reason for those?

---

UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn

loqs

Member

Registered: 2014-03-06

Posts: 19,100

Re: Computer fails on booting every second or third boot.

Sep 28 16:54:47 hardwork systemd[1]: home-userus-Storage.mount: Mount process exited, code=exited, status=32/n/a
Sep 28 16:54:47 hardwork systemd[1]: home-userus-Storage.mount: Failed with result 'exit-code'.
Sep 28 16:54:47 hardwork systemd[1]: Failed to mount /home/userus/Storage.
Sep 28 16:54:47 hardwork systemd[1]: Dependency failed for Local File Systems.
Sep 28 16:54:47 hardwork systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Sep 28 16:54:47 hardwork systemd[1]: local-fs.target: Triggering OnFailure= dependencies.

The mount failure causes the target local-fs.target to fail which triggers emergency.target

Sep 28 16:54:47 hardwork systemd[632]: emergency.service: Executable /bin/plymouth missing, skipping: No such file or dir>

emergency.target starts emergency.service which checks for the presence of  /bin/plymouth and skips as it is not present.

Please post the full journal for that boot in code tags.