Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Dependency failed for Local File Systems

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
avelach
Posts: 17
Joined: 2009-09-24 17:58
Has thanked: 4 times
Been thanked: 1 time

Dependency failed for Local File Systems

#1 Post by avelach »

Hi all,

This started to happen some weeks ago after upgrading to Bullseye. My mobo holds two software-mirrored SDD (RAID 1) for the OS and one HDD for /var/lib/backuppc. Since then for some unknown (at least to me) reason booting the system (either from suspend-to-RAM, reboot or poweroff) sometimes (around one out of three tries) fails to mount the HDD partition leading the system to interrupt the boot process so I have to manually comment out the offending line in /etc/fstab, reboot, restore the line and mount the partition after the system has booted succesfully.

The error message sequence is:

Failed to start File System <UUID>
Dependency failed for /var/lib/backuppc
Dependency failed for Local File Systems


I tried replacing UUID with the explicit device /dev/sdX1 to no avail.

Any suggestion shall be welcome as this behavior never happened before the upgrade.

Regards,
Antonio

User avatar
bw123
Posts: 4015
Joined: 2011-05-09 06:02
Has thanked: 1 time
Been thanked: 28 times

Re: Dependency failed for Local File Systems

#2 Post by bw123 »

Any suggestion shall be welcome as this behavior never happened before the upgrade.
Did you restore your backup and confirm it is related to the upgrade? Where's fstab? smartmontools? Age of drive?

An error message is just really not much to go on, have you used the interwebz to look it up, or should I do that?

It's odd to me that any mount in fstab would fail, and you could continue to boot, comment it out and reboot. A failing mount in fstab is generally a fatal error?
resigned by AI ChatGPT

avelach
Posts: 17
Joined: 2009-09-24 17:58
Has thanked: 4 times
Been thanked: 1 time

Re: Dependency failed for Local File Systems

#3 Post by avelach »

Did you restore your backup and confirm it is related to the upgrade? Where's fstab? smartmontools? Age of drive?
I don't backup the system, just some data so I cannot fully confirm that (just suspicious). Here is my fstab (which has remained untouched since more than one year):

Code: Select all

# /dev/mapper/vg1-lvroot
UUID=69372865-7982-4c69-90ff-88bb3d4c5b91       /       ext4    noatime,nodiratime,errors=remount-ro    0       1

# /dev/mapper/vg1-lvhome
UUID=eb07d8a4-29fc-45e2-a259-c9c24fcb9c64       /home   ext4    noatime,nodiratime      0       2

# /dev/mapper/vg1-lvdatos
UUID=c7857248-a36c-44f6-84d1-e1ac836ed2db       /usr/local/share/datos  ext4    noatime,nodiratime      0       2

# /dev/sdc1 --- ##### FAILING LINE BELOW ######
UUID=c060fc8e-efb0-4906-b19a-cc886f4d7107       /var/lib/backuppc       ext4    defaults        0       2
Smartmontools show no issues though it is quite an old disk (with more than 3.5 years of flying hours but still reliable):

Code: Select all

smartctl -A /dev/sdc
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-9-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate     0x000f   081   063   006    Pre-fail  Always       -       145327861
3 Spin_Up_Time            0x0003   098   096   000    Pre-fail  Always       -       0
4 Start_Stop_Count        0x0032   098   098   020    Old_age   Always       -       2048
5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
7 Seek_Error_Rate         0x000f   076   060   045    Pre-fail  Always       -       42690931
9 Power_On_Hours          0x0032   066   066   000    Old_age   Always       -       30294
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       2031
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       0 0 4
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   061   053   040    Old_age   Always       -       39 (Min/Max 22/42)
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       2108
194 Temperature_Celsius     0x0022   039   017   000    Old_age   Always       -       39 (0 17 0 0 0)
195 Hardware_ECC_Recovered  0x001a   001   001   000    Old_age   Always       -       145327861
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       30115h+28m+52.703s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       8207525031
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       26378589730

Code: Select all

smartctl -A -P show /dev/sdc
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-9-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

Drive found in smartmontools Database.  Drive identity strings:
MODEL:              ST1000DM003-1SB102
FIRMWARE:           CC43
match smartmontools Drive Database entry:
MODEL REGEXP:       ST(1000|1500|2000|2500|3000)DM00[0-3]-.*|APPLE HDD ST3000DM001
FIRMWARE REGEXP:    .*
MODEL FAMILY:       Seagate Barracuda 7200.14 (AF)
ATTRIBUTE OPTIONS:  188 Command_Timeout
240 Head_Flying_Hours
An error message is just really not much to go on, have you used the interwebz to look it up, or should I do that?
I don't know what interwebz is. I'll take a look at it.
It's odd to me that any mount in fstab would fail, and you could continue to boot, comment it out and reboot. A failing mount in fstab is generally a fatal error?
As the failing mount is not a system one the boot process drops into a prompt asking for the root password. There I can modify the fstab to comment out the offending line and reboot thereafter (resuming the boot process will also fail even having the fstab modified so I'm being forced to reboot).

Thanks for your help.

avelach
Posts: 17
Joined: 2009-09-24 17:58
Has thanked: 4 times
Been thanked: 1 time

Re: Dependency failed for Local File Systems

#4 Post by avelach »

An error message is just really not much to go on, have you used the interwebz to look it up, or should I do that?
Alas I'm so bad at English... Yes I have looked for that message but always get bad UUID related fixes or multipath issues (which is not the case for me). I have not changed the disk UUID entry since the system installation days plus it is also nonsense having both failing and succesful boots with the same UUID. For the record I have also tested having the device pointer (/dev/sdc1) into the fstab but the behavior remains the same.

p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: Dependency failed for Local File Systems

#5 Post by p.H »

avelach wrote: 2021-11-26 18:32 I tried replacing UUID with the explicit device /dev/sdX1 to no avail.
That would only make it worse. /dev/sd* device names are not persistent across reboots.

Next time it happens, use the emergency prompt to gather information with

Code: Select all

lsblk
blkid
dmesg | grep sdX # where sdX is the HDD if present
To be compared with the same information when it boots fine.
Note that you can add "nofail" to the options field in fstab to make the error non fatal.

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 461 times

Re: Dependency failed for Local File Systems

#6 Post by sunrat »

Back up your data. See my signature.
That disk will fail one day and you will lose everything on it. With that high Raw_Read_Error_Rate it will probably be soon.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

Post Reply