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

 

 

 

File system check error on boot

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
User avatar
Linuxembourg
Posts: 25
Joined: 2021-11-24 00:41
Has thanked: 4 times
Been thanked: 3 times

File system check error on boot

#1 Post by Linuxembourg »

This morning I was unable to boot into my system. It failed a few times with variations of "failed to start file system check on /dev/disk" eventually with messages "failed to start file system check onn /dev/disk-by-UUID/long-strings-of-hexadecimal".

Initially I had a slightly different message relating to "/dev/sda1" which I was unable to do fsck on because the target was mounted and unable to umount because target was busy.

After I got the "UUID....." message I resolved the issue by typing a rather long command "systemctl status --nopager --full systemd-fsck@dev-disk-by\\x2duuid....." followed by adding the long string of hex separated by "\\" and "x2d" and ".service" at the end.

E.g. systemctl status --nopager --full systemd-fsck@dev-disk-by\\x2duuid-000000\\x2d0000\\x2d0000\\x2d000000.service

I then got an error telling me I had to run fsck manually on /dev/sda6/ which I did, and it has resolved the issue for now.

I am running Debian 11 XFCE stable with unattended upgrades turned on.

What I would like to understand is what possibly caused the issue. The hard drive on the laptop (from about 2006) might be on its way out?

Maybe something to do with hibernation? Or maybe because it ran completely out of battery and the system clock reset? My laptop isn't set to do anything when battery reaches a critical level and I think I fell asleep with it running on battery.

I didn't do anything else yesterday that I can think would've caused it. The only thing I can think I ran as sudo yesterday was installing the email program evolution. Other than that I was browsing (in an appimage of Chromium) and playing around with a bash script to integrate appimages (no sudo).

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

Re: File system check error on boot

#2 Post by p.H »

What inconsistencies or errors did manual fsck report and fix ?
Did you ckeck the kernel logs for drive errors ?
Did you check the SMART status of the drive with smartctl from package smartmontools ?

User avatar
Linuxembourg
Posts: 25
Joined: 2021-11-24 00:41
Has thanked: 4 times
Been thanked: 3 times

Re: File system check error on boot

#3 Post by Linuxembourg »

p.H wrote: 2021-11-28 13:41 What inconsistencies or errors did manual fsck report and fix ?
Did you ckeck the kernel logs for drive errors ?
Did you check the SMART status of the drive with smartctl from package smartmontools ?
I can't remember exactly. I have found the fsck log but it only contains the record of the last successful check I made before successfully booting up. There was quite a few things to say yes to. Some were to do with "inorphaned node"

I can't find anything in the kernel logs. In the boot logs I can find details of the error I got but not the fsck info.

Regarding the smart status, it seems to indicate that the drive is on its way out.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1019
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2350
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 41
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 053 053 000 Old_age Always - 18832
10 Spin_Retry_Count 0x0033 146 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1717
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 1295
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 97
193 Load_Cycle_Count 0x0032 074 074 000 Old_age Always - 269082
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 37 (Min/Max 9/53)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 22
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 6
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 2
222 Loaded_Hours 0x0032 059 059 000 Old_age Always - 16536
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 367
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
Here are the last five errors. Not sure if they mean anything or not. I think they all relate to me running out of power rather than booting up. I'm basing that on powered-up time because it's the only bit that's a human thing in the whole message! :lol:
Error 631 occurred at disk power-on lifetime: 18829 hours (784 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 0a 01 a0 dc 6f Error: UNC at LBA = 0x0fdca001 = 266117121

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 08 00 a0 dc 40 00 00:25:39.468 READ FPDMA QUEUED
ef 10 03 00 00 00 a0 00 00:25:39.462 SET FEATURES [Enable SATA feature]
ef 10 02 00 00 00 a0 00 00:25:39.462 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 00:25:39.462 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 00:25:39.462 IDENTIFY DEVICE

Error 630 occurred at disk power-on lifetime: 18829 hours (784 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 02 01 a0 dc 6f Error: UNC at LBA = 0x0fdca001 = 266117121

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 00 00 a0 dc 40 00 00:25:35.151 READ FPDMA QUEUED
60 28 f0 58 a0 9c 40 00 00:25:35.151 READ FPDMA QUEUED
60 20 e8 38 a0 9c 40 00 00:25:35.150 READ FPDMA QUEUED
60 30 e0 a8 a0 9c 40 00 00:25:35.135 READ FPDMA QUEUED
60 08 d0 30 a0 5c 40 00 00:25:35.118 READ FPDMA QUEUED

Error 629 occurred at disk power-on lifetime: 18829 hours (784 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 c2 01 a0 dc 6f Error: UNC at LBA = 0x0fdca001 = 266117121

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 18 f8 80 a0 dc 40 00 00:25:23.290 READ FPDMA QUEUED
60 38 c0 00 a0 dc 40 00 00:25:23.279 READ FPDMA QUEUED
60 28 b0 80 a0 9c 40 00 00:25:23.180 READ FPDMA QUEUED
60 38 a8 00 a0 9c 40 00 00:25:23.172 READ FPDMA QUEUED
60 10 90 80 a0 5c 40 00 00:25:23.165 READ FPDMA QUEUED

Error 628 occurred at disk power-on lifetime: 18828 hours (784 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 2a 01 a0 dc 6f Error: WP at LBA = 0x0fdca001 = 266117121

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 80 00 cf 43 40 00 00:00:55.508 WRITE FPDMA QUEUED
61 08 78 38 ce 43 40 00 00:00:55.508 WRITE FPDMA QUEUED
61 08 70 b0 cd 43 40 00 00:00:55.508 WRITE FPDMA QUEUED
61 08 68 a0 cd 43 40 00 00:00:55.508 WRITE FPDMA QUEUED
61 08 60 b8 cc 43 40 00 00:00:55.508 WRITE FPDMA QUEUED

Error 627 occurred at disk power-on lifetime: 18828 hours (784 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 1a 00 a0 dc 6f Error: WP at LBA = 0x0fdca000 = 266117120

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 d8 00 08 00 40 00 00:00:50.892 WRITE FPDMA QUEUED
61 08 28 00 08 84 40 00 00:00:50.849 WRITE FPDMA QUEUED
60 08 20 78 a0 dc 40 00 00:00:50.847 READ FPDMA QUEUED
60 08 18 00 a0 dc 40 00 00:00:50.847 READ FPDMA QUEUED
60 20 10 00 79 38 40 00 00:00:50.847 READ FPDMA QUEUED

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

Re: File system check error on boot

#4 Post by p.H »

Linuxembourg wrote: 2021-11-28 15:09 Some were to do with "inorphaned node"
Orphaned inode errors are filesystem inconsistencies which may indicate incomplete file deletion caused by unclean shutdown.
Linuxembourg wrote: 2021-11-28 15:09 5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 41
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 22
These values indicate that the drive has 41 reallocated sectors : sectors which were replaced before or after they failed.
Linuxembourg wrote: 2021-11-28 15:09 5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 41
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 22
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 6
This value indicates that the drive has 6 currently unreadable bad sectors. Usually, it's not going to get better over time. If a bad sector contains critical metadata, it may prevent to mount the filesystem.
Linuxembourg wrote: 2021-11-28 15:09 Here are the last five errors. Not sure if they mean anything or not. I think they all relate to me running out of power
I don't think so. They are physical read errors which are the consequence of the unreadable sectors (UNC=uncorrectable).
Linuxembourg wrote: 2021-11-28 13:30 Maybe something to do with hibernation? Or maybe because it ran completely out of battery and the system clock reset? My laptop isn't set to do anything when battery reaches a critical level and I think I fell asleep with it running on battery.
Hibernation (suspend to disk) or suspend to RAM ? Hibernation completely shuts down the computer, so running out of battery does nothing. However running out of battery during suspend to RAM has the same effect as an unclean shutdown.

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

Re: File system check error on boot

#5 Post by bw123 »

I think you are lucky you got a warning like this. Replace it, drives are cheap now.

18832 hours of use is 784 days, or over 2 years continuous, that's a nice drive!
resigned by AI ChatGPT

CwF
Global Moderator
Global Moderator
Posts: 2638
Joined: 2018-06-20 15:16
Location: Colorado
Has thanked: 41 times
Been thanked: 192 times

Re: File system check error on boot

#6 Post by CwF »

bw123 wrote: 2021-11-29 00:43 18832 hours of use is 784 days, or over 2 years continuous, that's a nice drive!
wow, I consider that young!

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

Re: File system check error on boot

#7 Post by bw123 »

https://www.extremetech.com/computing/1 ... y-live-for

This article is 8 yrs old, and they tested the drives mentioned for four years. SO eight years ago, four year old drives had about a 3-4 yr lifespan before they started failing at a rate above 11%

I'm not aware of any study on the rate of failure lately of modern electronics, but I am an old codger, and I assume it has gone down.
resigned by AI ChatGPT

User avatar
Linuxembourg
Posts: 25
Joined: 2021-11-24 00:41
Has thanked: 4 times
Been thanked: 3 times

Re: File system check error on boot

#8 Post by Linuxembourg »

p.H wrote: 2021-11-28 17:28 Hibernation (suspend to disk) or suspend to RAM ? Hibernation completely shuts down the computer, so running out of battery does nothing. However running out of battery during suspend to RAM has the same effect as an unclean shutdown.
Thank you for the knowledge and information. Unfortunately I cannot give the post a thumbsup as I am the thread starter.

It was set up to do nothing at critical battery level (not my smartest move). But set to hibernate if the laptop lid was closed. I am pretty sure it just run out of battery.

User avatar
Linuxembourg
Posts: 25
Joined: 2021-11-24 00:41
Has thanked: 4 times
Been thanked: 3 times

Re: File system check error on boot

#9 Post by Linuxembourg »

bw123 wrote: 2021-11-29 00:43 I think you are lucky you got a warning like this. Replace it, drives are cheap now.

18832 hours of use is 784 days, or over 2 years continuous, that's a nice drive!
:lol:

It's a 2006 Sony VAIO laptop, one of my mates old laptops. It wouldn't be worth it really, it'd be easier and better to just buy a newer old laptop!

When I ran the hw-probe testing tool it linked me to a page giving a summary of my hardware. There was a "note" next to my processor. When I clicked to see what it was, it was simply "this processor is slow". I didn't need a testing tool to tell me that! :lol:

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

Re: File system check error on boot

#10 Post by bw123 »

Sorry for the late bump, I was checking some older replies. About filesystem checking on boot:

What I do about twice a year is add fsck.mode=force to the kernel line in grub. you can check it out:
https://html.duckduckgo.com/html/?q=fsck.mode=force
because from what I understand a full fsck is only triggered on boot if the filesytem is flagged as 'dirty' because /etc/mke2fs.conf disabled periodic fsck several releases ago. They also got rid of 'touch /forcefsck' which was really a convenient way of getting it done. A full periodic fsck is a good practice IMNSHO and it should be done at least twice a year.
Afterwards you can confirm a full fsck has been done by using 'tune2fs -l' it will tell you the date of last check.

Then I run an alternative smartctl test, either '-t short' or '-t long' and record the results and compare to previous.
This has been a pretty good strategy for about four years now, but I'm always thinking about drive problems.
resigned by AI ChatGPT

Post Reply