You are not logged in.
Recently, I have experienced the failure to boot, due to the mounting problem. The following is the journalctl log
Apr 06 08:10:04 mylaptop systemd[1]: Starting File System Check on /dev/disk/by-uuid/a09a7384-545b-4230-a550-1b25362bd8ed...
Apr 06 08:10:12 mylaptop systemd[1]: Finished Flush Journal to Persistent Storage.
Apr 06 08:10:17 mylaptop systemd-fsck[608]: home: Inode 12976177 seems to contain garbage.
Apr 06 08:10:17 mylaptop systemd-fsck[608]: home: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Apr 06 08:10:17 mylaptop systemd-fsck[608]: (i.e., without -a or -p options)
Apr 06 08:10:17 mylaptop systemd-fsck[606]: fsck failed with exit status 4.
Apr 06 08:10:17 mylaptop systemd[1]: systemd-fsck@dev-disk-by\x2duuid-a09a7384\x2d545b\x2d4230\x2da550\x2d1b25362bd8ed.service: Main process exited, code=exited, status=1/FAILURE
Apr 06 08:10:17 mylaptop systemd[1]: systemd-fsck@dev-disk-by\x2duuid-a09a7384\x2d545b\x2d4230\x2da550\x2d1b25362bd8ed.service: Failed with result 'exit-code'.
Apr 06 08:10:17 mylaptop systemd[1]: Failed to start File System Check on /dev/disk/by-uuid/a09a7384-545b-4230-a550-1b25362bd8ed.
Apr 06 08:10:17 mylaptop systemd[1]: Dependency failed for /home.
Apr 06 08:10:17 mylaptop systemd[1]: Dependency failed for Local File Systems.
Apr 06 08:10:17 mylaptop systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Apr 06 08:10:17 mylaptop systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
After login as root and run "fsck /dev/sda3", and fixes all prompts. Then the reboot is success. But it happens twice within a week.
I always shutdown the computer using "systemctl poweroff" through oblogout.
Does anyone know whether this issue is caused by OS level? Any related bug reports (I searched, but didn't find related issue).
Or it is a symptom of harddisk failure?
Last edited by allencch (2022-04-08 02:17:14)
Offline
Possible explantions include
- a parallel OS (windows?)
- bad trimming (cron job or discard option)
- FS bug (ext4 or sth. more exotic?) or
- the drive is falling apart (smartctl -a)
Online
Sounds like disk failure to me. Run a long SMART test and then post the output of
smartctl -a
Offline
This is the `smartctl -a` result,
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.17.1-arch1-1] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda Pro Compute
Device Model: ST1000LM049-2GH172
Serial Number: WGS2H311
LU WWN Device Id: 5 000c50 0be002540
Firmware Version: SDM1
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 2.5 inches
TRIM Command: Available
Device is: In smartctl database 7.3/5319
ATA Version is: ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Apr 7 13:36:58 2022 +08
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x71) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 124) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
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 060 058 006 Pre-fail Always - 227677564
3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2718
5 Reallocated_Sector_Ct 0x0033 098 098 036 Pre-fail Always - 728
7 Seek_Error_Rate 0x000f 090 060 045 Pre-fail Always - 974548030
9 Power_On_Hours 0x0032 090 090 000 Old_age Always - 9562 (198 176 0)
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 098 098 020 Old_age Always - 2718
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 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 058 049 040 Old_age Always - 42 (Min/Max 26/48)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 10
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 20
193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 7095
194 Temperature_Celsius 0x0022 042 051 000 Old_age Always - 42 (0 22 0 0 0)
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 - 9548 (49 19 0)
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 23901578322
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 20271548416
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 9561 -
# 2 Short offline Completed without error 00% 9557 -
# 3 Extended offline Aborted by host 70% 9557 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Offline
Despite
# 1 Extended offline Completed without error 00% 9561 -
5 Reallocated_Sector_Ct 0x0033 098 098 036 Pre-fail Always - 728
looks scary.
I'd not trust the drive nor its self-testing capacity, boot grml from a usb key, secure all valuable data immediately and run a (non-destructive) badblocks test.
(The destructive test is much faster, but the drive is blank afterwards, so if the reallocated sectors are a red herring - what is unlikely, but not impossible - you saved some time on badblocks to waste some time on re-installation.
If you can, you could also dd_rescue clone the entire drive onto a new one and if the drive turns out to be still good, but empty after a destructive test, you can just swap them.
Online
@seth @V1del, thanks for the help and advice.
Offline