Arch Linux

gecici90

Member

Registered: 2007-10-19

Posts: 17

force fsck on boot and timeout waiting for device issues [SOLVED]

Archlinux starts checking fs on every boot since linux and systemd packages were updated last night.
systemd --->213-5
linux ---->3.14.5-1

Another issue appears with last update
Timed out waiting for device dev-disk-by\x2duuid-9f780ada\x2d0671\
Dependency failed for /dev/disk/by-uuid/9f780ada-0671-43d8-b036-f9
Dependency failed for Swap.

I have this issue on my laptop which was updated yesterday.I have also desktop running archlinux again I've just checked out the systemd and linux versions.The systemd package is not the latest one it's 212-3.I havent any problem on that machine.I guess systemd is responsible of this cause.

I've just reboot and realized that systemd-fsck says Super block last write is in the future.Date and time is correct in BIOS same as on linux

Last edited by gecici90 (2014-06-05 21:10:52)

omeleet

Member

Registered: 2014-06-05

Posts: 2

Re: force fsck on boot and timeout waiting for device issues [SOLVED]

I had the same problem, I get in the recovery console after forced fsck.
But downgrading systemd and systemd-sysvcompat to their previous version made it all work back again.

The sorted list of the upgraded packages:

[2014-06-05 21:11] [PACMAN] installed libx264           (1:142.20140311-4)
[2014-06-05 21:11] [PACMAN] upgraded btrfs-progs        (3.14.1-1 -> 3.14.2-2)
[2014-06-05 21:11] [PACMAN] upgraded cifs-utils         (6.2-1 -> 6.3-1)
[2014-06-05 21:11] [PACMAN] upgraded imagemagick        (6.8.9.1-2 -> 6.8.9.1-3)
[2014-06-05 21:11] [PACMAN] upgraded filesystem         (2013.05-2 -> 2014.05-2)
[2014-06-05 21:11] [PACMAN] upgraded lib32-libdbus      (1.8.0-1 -> 1.8.2-1)
[2014-06-05 21:11] [PACMAN] upgraded libproxy           (0.4.11-2 -> 0.4.11-3)
[2014-06-05 21:11] [PACMAN] upgraded libpurple          (2.10.9-1 -> 2.10.9-2)
[2014-06-05 21:11] [PACMAN] upgraded libsystemd         (212-3 -> 213-5)
[2014-06-05 21:11] [PACMAN] upgraded libwbclient        (4.1.7-1 -> 4.1.8-1)
[2014-06-05 21:11] [PACMAN] upgraded openssl            (1.0.1.g-1 -> 1.0.1.h-1)
[2014-06-05 21:11] [PACMAN] upgraded perl               (5.18.2-2 -> 5.20.0-2)
[2014-06-05 21:11] [PACMAN] upgraded perl-xml-parser    (2.41-4 -> 2.41-5)
[2014-06-05 21:11] [PACMAN] upgraded perl-yaml-syck     (1.27-1 -> 1.27-2)
[2014-06-05 21:11] [PACMAN] upgraded pidgin             (2.10.9-1 -> 2.10.9-2)
[2014-06-05 21:11] [PACMAN] upgraded postgresql-libs    (9.3.4-1 -> 9.3.4-2)
[2014-06-05 21:11] [PACMAN] upgraded python2            (2.7.6-3 -> 2.7.7-1)
[2014-06-05 21:11] [PACMAN] upgraded smbclient          (4.1.7-1 -> 4.1.8-1)
[2014-06-05 21:11] [PACMAN] upgraded subversion         (1.8.9-1 -> 1.8.9-2)
    [2014-06-05 21:11] [PACMAN] upgraded systemd            (212-3 -> 213-5)
    [2014-06-05 21:11] [PACMAN] upgraded systemd-sysvcompat (212-3 -> 213-5)
[2014-06-05 21:11] [PACMAN] upgraded x264               (1:142.20140311-1 -> 1:142.20140311-4)
[2014-06-05 21:11] [PACMAN] upgraded xchat              (2.8.8-13 -> 2.8.8-14)
[2014-06-05 21:11] [PACMAN] upgraded xfconf             (4.10.0-3 -> 4.10.0-4)

Downgrading systemd and systemd-sysvcompat makes my computer boots normally:

[2014-06-05 21:43] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/systemd-212-3-x86_64.pkg.tar.xz /var/cache/pacman/pkg/systemd-sysvcompat-212-3-x86_64.pkg.tar.xz'
[2014-06-05 21:43] [PACMAN] downgraded systemd            (213-5 -> 212-3)
[2014-06-05 21:43] [PACMAN] downgraded systemd-sysvcompat (213-5 -> 212-3)

gecici90

Member

Registered: 2007-10-19

Posts: 17

Re: force fsck on boot and timeout waiting for device issues [SOLVED]

Marked as SOLVED

Here's the description

Here's the key line that is responsible of this issue on boot
"Super block last write time is in the future"
1.  I have enabled the ntp on date and time settings on arch
2.

timedatectl status

on terminal when the command works it says

Warning: The RTC is configured to maintain time in the local time zone. This
         mode is not fully supported and will create various problems with time
         zone changes and daylight saving time adjustments. If at all possible, use
         RTC in UTC by calling 'timedatectl set-local-rtc 0'

Be warned that, if the hardware clock is set to localtime, dealing with daylight saving time is messy. If the DST changes when your computer is off, your clock will be wrong on next boot (there is a lot more to it). Recent kernels set the system time from the RTC directly on boot, assuming that the RTC is in UTC. This means that if the RTC is in local time, then the system time will first be set up wrongly and then corrected shortly afterwards on every boot. This is the root of certain weird bugs (time going backwards is rarely a good thing)..

time title on arch wiki

3. to fix this

sudo timedatectl set-local-rtc 0

after all reboot works fine, other problems are dissappeared itself such as activating swap as i described before message

Last edited by gecici90 (2014-06-06 07:56:56)

Demon

Member

From: Republic of Srpska, BA

Registered: 2008-03-02

Posts: 246

Re: force fsck on boot and timeout waiting for device issues [SOLVED]

My RTC is set to UTC and still I have this problem. Had to set noauto option under home and swap partitions in fstab to successfully boot. (But then I must manually mount those partitions, which is pain in the a$$.)