Arch Linux

monksy

Member

Registered: 2013-12-30

Posts: 23

How would you increase the time out time for doing a file system check

I'm occasionally having an issue with booting my machine. Occasionally the root filesystem needs an FSCK, and the machine won't boot.

As a result I'm blocked from entering emergency mode because "the root file system is locked".

Logs I'm seeing:

OK - Reached target Basic system
[TIME]  Timed out waiting for device /dev/nvme0n1p7
[DEPEND] Dep failed for initrd root device
[DEPEND] Dep failed for /sysroot
[DEPEND] Dep failed for initrd root file system
[DEPEND] Dep failed for filesystem check for /dev/nvm0n1p7

If I wait about 5-7ish minutes and restart, this clears up. So this leads me to believe that it's doing a filesystem check in the background.

The fstab entry is:

UUID=934c[end of uuid]       /               ext4            rw,relatime,x-systemd.device-timeout=300s,x-systemd.mount-timeout=4min  0 1

The timeouts do not work and it's always only waiting 90 seconds.

Ideas?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,395

Re: How would you increase the time out time for doing a file system check

The system times out waiting for the device, not the mount. You're not waiting for an fsck, those are not time constrained.
Is /dev/nvme0n1p7 even the root filesystem?

Please post the output of "lsblk -f" and your fstab (the UUIDs are not private data but exist to prevent collisions, you can pseudonymize them if you want, but they need to be identifiable)

Why does "Occasionally the root filesystem needs an FSCK" that leads to "the machine won't boot"?
Is there a parallel windows installation?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

monksy

Member

Registered: 2013-12-30

Posts: 23

Re: How would you increase the time out time for doing a file system check

Windows is installed on the machine, but it hasn't been booted in a long time. /mnt/other is an encrypted drive.

This only happens, I believe on unclean restarts,which is why I believe that this is a background FSCK that's causing the issue. It correct's it's sel if I wait 6+ minutes when the emergency console can't be accessed.

Fstab:

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p8
UUID=934c0800-b860-48e3-91e0-0bcf7e9337d5       /               ext4            rw,relatime,x-systemd.device-timeout=300s,x-systemd.mount-timeout=4min  0 1

# /mnt/other/home
/other/home             /home           none            rw,bind         0 3

# /mnt/other/var
/other/var              /var            none            rw,bind         0 3

# /mnt/other/opt
/other/opt              /opt            none            rw,bind         0 3

# /dev/nvme0n1p1 LABEL=SYSTEM
UUID=6AD2-10E0          /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro   0 2

# /dev/nvme0n1p7
UUID=8f661d9a-637a-45c7-b89d-3ca6b442b611       none            swap            defaults        0 0

/dev/mapper/other                               /other          ext4            defaults        0 2

lsblk -f

NAME        FSTYPE      FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
nvme1n1                                                                                    
├─nvme1n1p4 ext4        1.0            41875fc5-4dd2-4efd-b268-aa998c76a267                
└─nvme1n1p5 ext4        1.0            ba2ccb02-741f-45eb-b8a4-bc048ad664b4                
nvme0n1                                                                                    
├─nvme0n1p1 vfat        FAT32 SYSTEM   6AD2-10E0                             950.4M    26% /boot
├─nvme0n1p2                                                                                
├─nvme0n1p3 ntfs              OS       7856D3F556D3B1DC                                    
├─nvme0n1p4 ntfs              RECOVERY 220A8A790A8A4A2D                                    
├─nvme0n1p5 ntfs              RESTORE  5808390D0838EB9E                                    
├─nvme0n1p6 swap        1              8f661d9a-637a-45c7-b89d-3ca6b442b611                [SWAP]
├─nvme0n1p7 ext4        1.0            934c0800-b860-48e3-91e0-0bcf7e9337d5   11.6G    61% /
└─nvme0n1p8 crypto_LUKS 2              2eb6aeb9-8726-4228-b0db-c966fbd826ad                
  └─other   ext4        1.0            a23c17da-0aa8-4810-bb4d-15ae898ba2ec     19G    90% /var
                                                                                           /opt
                                                                                           /home
                                                                                           /other

Last edited by monksy (2024-01-24 21:08:12)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,395

Re: How would you increase the time out time for doing a file system check

Please use [code][/code] tags. Edit your post in this regard.

The see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
It doesn't matter how often you boot windows.

Seeing the two nvme's what's most likely happening is that they switch order.
What's your bootloader? Grub? Please post its config (/boot/grub/grub.cfg, in case)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

monksy

Member

Registered: 2013-12-30

Posts: 23

Re: How would you increase the time out time for doing a file system check

My bootloader is systemd-boot.

title        Arch
linux        /vmlinuz-linux
initrd      /amd-ucode.img
initrd      /initramfs-linux.img
options     root=/dev/nvme0n1p7 rw 
#nvidia-drm.modeset=1

Everything else is auto generated.

Last edited by monksy (2024-01-24 21:11:17)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,395

Re: How would you increase the time out time for doing a file system check

options     root=UUID=934c0800-b860-48e3-91e0-0bcf7e9337d5 rw

Never use device names, UUIDs exist for pretty much this reason only.

Last edited by seth (2024-01-24 21:15:50)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

monksy

Member

Registered: 2013-12-30

Posts: 23

Re: How would you increase the time out time for doing a file system check

How does that help? the mount point it's trying to reach is the correct one: /dev/nvme0n1p7.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,395

Re: How would you increase the time out time for doing a file system check

The point is that nvme0n1 and nvme1n1 can switch their positions any time, so you're trying to mount/access /dev/nvme0n1p7 but there's no /dev/nvme0n1p7 because it's the drive that in the posted lsblk only had nvme1n1p4 and nvme1n1p5 (ie. now nvme0n1p4 and nvme0n1p5)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

monksy

Member

Registered: 2013-12-30

Posts: 23

Re: How would you increase the time out time for doing a file system check

Dude..  I think you're right on the device switching. I don't know how you knew that or why it happens. But thank you!

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,395

Re: How would you increase the time out time for doing a file system check

Because I read the wiki
https://wiki.archlinux.org/title/Persis … ice_naming

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

monksy

Member

Registered: 2013-12-30

Posts: 23

Re: How would you increase the time out time for doing a file system check

touche