Mounting of local Disk fails - Timeout

General system Kernel, boot, graphics & hardware
1

Heya, I have an issue with one of my HDDs (specifically the last HDD, all other drives are flash-based). The mounting during boot fails sometimes. If the error occurs I boot into emergency mode:

PXL_20240601_143354322
PXL_20240601_1433543221920Ă—1080 218 KB

This is my disk setup:

udo blkid -s NAME -s UUID -s LABEL
/dev/nvme0n1p1: UUID="BDEB-C54C"
/dev/nvme0n1p2: LABEL="endeavouros" UUID="178ba18b-3faa-4b38-b7e5-5b0f5d2f285c"
/dev/sdb2: LABEL="Stuff" UUID="545f70e0-5226-4d38-862e-cf159fbf6e7f"
/dev/sdb3: LABEL="backup" UUID="8c7a3875-418a-49de-8a6e-47a480315c22"
/dev/sdb1: LABEL="Misc" UUID="e0e1bff4-1418-4574-b3da-823cfe4fc668"
/dev/nvme1n1p2: LABEL="endeavouros" UUID="178ba18b-3faa-4b38-b7e5-5b0f5d2f285c"
/dev/nvme1n1p1: UUID="5B0B-DC27"
/dev/sda1: LABEL="Data" UUID="fc6a43bb-ec9a-4f23-94e9-eff7cf5f250c"
/dev/zram0: LABEL="zram0" UUID="d497e170-de2a-4076-b4ec-04a7633aaccd"

I mount during boot time via fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=BDEB-C54C                            /boot/efi      vfat    defaults,noatime 0 2
UUID=178ba18b-3faa-4b38-b7e5-5b0f5d2f285c /              btrfs   subvol=/@,defaults,noatime,compress=zstd 0 0
UUID=178ba18b-3faa-4b38-b7e5-5b0f5d2f285c /home          btrfs   subvol=/@home,defaults,noatime,compress=zstd 0 0
UUID=178ba18b-3faa-4b38-b7e5-5b0f5d2f285c /var/cache     btrfs   subvol=/@cache,defaults,noatime,compress=zstd 0 0
UUID=178ba18b-3faa-4b38-b7e5-5b0f5d2f285c /var/log       btrfs   subvol=/@log,defaults,noatime,compress=zstd 0 0
UUID=178ba18b-3faa-4b38-b7e5-5b0f5d2f285c /Virtual       btrfs   subvol=/@virtual,defaults,noatime,compress=zstd 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

#local disks
UUID=fc6a43bb-ec9a-4f23-94e9-eff7cf5f250c /Data          ext4    defaults,noatime 0 2
UUID=e0e1bff4-1418-4574-b3da-823cfe4fc668 /Misc          ext4    defaults,noatime 0 2
UUID=545f70e0-5226-4d38-862e-cf159fbf6e7f /Stuff          ext4    defaults,noatime 0 2
UUID=8c7a3875-418a-49de-8a6e-47a480315c22 /backup          ext4    defaults,noatime 0 2

# NFS shares
---- snipped because NFS irrelevant ---

Any ideas what’s going on here? It does not matter what I do in emergency mode - reboot, shutdown, continue, as soon as I am in the GUI I can use the HDD just as normal. Confusing…

2

Check the health of the disk, and also check that it is getting enough power at boot if it is an external drive.

This won’t fix the issue with the disk, but one way to make this much less annoying would be to add the nofail mount option. That way if the disk can’t be mounted in time at startup, it won’t cause the whole boot to fail–instead, the disk simply won’t be mounted and the rest of the startup routine will finish without it.

1 Like
3

First of all Smart test short:

sudo smartctl -t short /dev/sdb
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.9.2-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 1 minutes for test to complete.
Test will complete after Sun Jun  2 09:09:02 2024 CEST
Use smartctl -X to abort test.

Result:

sudo smartctl -H /dev/sdb
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.9.2-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

Looks good so far. Will now backup the whole drive (nothing important on it, otherwise it would have been in my backup-schedule. Thing is: This harddisk is part of my backup schedule - it is the target for the local backup part. all flashdisks will be daily backupped to this harddisk. And weekly to my NAS.
Power shouldn’t be an issue - these are 650Watts provide by a Seasonic Power Supply. Neither the 5950x nor the 6800xt have any issues, and those draw way more power. Ya, I know that harddisks pull 5v, but the other (flash)disks show no issue at all, even when I am torturing them…

4

I am still in the backup and checking for a spare drive process, but something came to my mind: I don’t think it’s the drive! Because /data fails also to mount, and this is on a different physical drive…