You are not logged in.

#1 2016-06-09 13:50:12

JonnyRobbie
Member
Registered: 2015-04-28
Posts: 153

[SOLVED] Timed out waiting for device dev-disk-by\x2duuid-...

During the boot, systemd fails on one partition. http://i.imgur.com/ObfjzIx.jpg

`systemctl default` (or ^D) advice works fine and the system loads after that. The problem is how to fix that so the system fine by itself? I've tries checking fstab, but is doesn't seem to contain anything unusal:

$ cat /etc/fstab 
# 
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/sda1
UUID=a52ca77b-e5c2-4e7e-8b3f-057e7615e56e       /               ext4            rw,relatime,data=ordered        0 1

# /dev/sda3
UUID=d9488bde-7d35-462f-b14c-1e9cb6dce34f       /home           ext4            rw,relatime,data=ordered        0 2

# /dev/sda4
UUID=d593b199-1cbf-4b61-b55c-ed8f36e2207c       /data           ext4            rw,relatime,data=ordered        0 2

# /dev/sda2
UUID=758d1264-249d-41b3-ab5b-fe6e5f41113d       none            swap            defaults        0 0

lsblk also doesn't seem to point to anything wrong:

$ lsblk -fs
NAME  FSTYPE LABEL   UUID                                 MOUNTPOINT
sda1  ext4           a52ca77b-e5c2-4e7e-8b3f-057e7615e56e /
└─sda                                                     
sda2  swap           758d1264-249d-41b3-ab5b-fe6e5f41113d [SWAP]
└─sda                                                     
sda3  ext4           d9488bde-7d35-462f-b14c-1e9cb6dce34f /home
└─sda                                                     
sda4  ext4           d593b199-1cbf-4b61-b55c-ed8f36e2207c /data
└─sda                                                     
sdb1  ntfs   My Book DA1E35F71E35CCEF                     /run/media/marek/My Book
└─sdb                                                     
sr0

(all that is after successful boot with default.target)

default.target seems to point to graphical.target

$ systemctl get-default             
graphical.target
$ systemctl --version
systemd 230
+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
$ uname -roms
Linux 4.5.4-1-ARCH x86_64 GNU/Linux

How would I go around fixing that timeout issue?

Last edited by JonnyRobbie (2016-06-21 13:10:34)

Offline

#2 2016-06-10 01:28:19

syg00
Member
Registered: 2006-01-11
Posts: 31

Re: [SOLVED] Timed out waiting for device dev-disk-by\x2duuid-...

systemd errors in the boot sequence are a royal PITA. Have been since the beginning, and fsck service is probably worst in the sense it is most pervasive in the community.
I have one system using btrfs that I had to remove from fstab - for over 18 months now.

Try the following (reboot after each change to check):
i) set the final field in the fstab entry for /data to 0 (zero)
ii) pass "fsck.mode=skip" to the kernel on boot.

In addition to (both) the above I tried disabling and masking the fsck service for my filesystem as well as setting up a null fsck.btrfs - all to no effect. Who designs this stuff ?.

Offline

#3 2016-06-10 07:25:07

JonnyRobbie
Member
Registered: 2015-04-28
Posts: 153

Re: [SOLVED] Timed out waiting for device dev-disk-by\x2duuid-...

Isn't disabling fsck on boot kinda dangerous? If I lose power (or other forced showdown) for example, wouldn't fsck recover some files with the help of journal caused by improper unmount?

Besides (as far as I understand - correct me, please), the fsck seems to have failed as a dependency not as a cause.

Offline

#4 2016-06-10 08:08:50

Docbroke
Member
From: India
Registered: 2015-06-13
Posts: 1,176

Re: [SOLVED] Timed out waiting for device dev-disk-by\x2duuid-...

as per uuid, error is in finding your data partition.
As a temporary solution, mask corresponding line in your fstab, you can mount your data partition later manually.


Arch is home!
cwm rofi vimb vifm vim lizzy pass

Offline

#5 2016-06-10 08:21:40

JonnyRobbie
Member
Registered: 2015-04-28
Posts: 153

Re: [SOLVED] Timed out waiting for device dev-disk-by\x2duuid-...

But that ^D or default.target works fine. It doesn't completely stop me from booting. It just interrupts at this stage.

Offline

#6 2016-06-10 08:25:38

Docbroke
Member
From: India
Registered: 2015-06-13
Posts: 1,176

Re: [SOLVED] Timed out waiting for device dev-disk-by\x2duuid-...

Your computer will boot faster by removing /data partition from fstab.
You may also try using /dev/sda4 in place of UUID in your fstab.


Arch is home!
cwm rofi vimb vifm vim lizzy pass

Offline

#7 2016-06-10 08:31:21

syg00
Member
Registered: 2006-01-11
Posts: 31

Re: [SOLVED] Timed out waiting for device dev-disk-by\x2duuid-...

As always, it's your data, so it's ultimately your choice.

This is *not* disabling fsck - it's telling systemd to get out of the way.
ext4 runs fsck as needed on mount - it is no longer dependent on mount count and/or time; and hasn't been for over 5 years. Systemd is simply forcing unnecessary extra fsck runs, then tripping over itself.

The fsck (on the filesystem) hasn't failed at all - a systemd imposed (maybe non-existent) dependency can't be finished. Run a fsck on that filesystem yourself - unmounted - and see what happens.

Offline

#8 2016-06-11 08:22:09

JonnyRobbie
Member
Registered: 2015-04-28
Posts: 153

Re: [SOLVED] Timed out waiting for device dev-disk-by\x2duuid-...

I've tried this https://wiki.archlinux.org/index.php/Fs … th_systemd, and since the original issue didn't happen 100% of the time, I'm currently testing if it helped.

Offline

#9 2016-06-21 13:10:14

JonnyRobbie
Member
Registered: 2015-04-28
Posts: 153

Re: [SOLVED] Timed out waiting for device dev-disk-by\x2duuid-...

It haven't appeared in a few days, so I guess I can mark it solved.

Last edited by JonnyRobbie (2016-06-21 13:10:56)

Offline

Board footer

Powered by FluxBB