Maybe a failing drive. Check hard disk for errors (i.e. smartctl).
If disk is ok, then check if filesystem needs repair. If using default filesystem (XFS) it needs to be done with unmounted partitions (for instance booting from a live environment to use xfs_repair).
Hi
I generally use SystemRescueCD for this. It includes xfs_repair and runs smoothly on NethServer, no matter if virtual or realā¦
My 2 cents
Andy
2 Likes
It seems to be a failing drive, right?
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 00% 2828 0
# 2 Short offline Completed without error 00% 2825 -
# 3 Extended offline Completed: read failure 00% 2824 0
# 4 Short offline Completed without error 00% 2822 -
# 5 Short offline Completed without error 00% 2821 -
# 6 Short offline Aborted by host 90% 13468 -
Note, that Power_On_Hours is 68367 > 65536 and therefore the values for LifeTime started at zero again.
Yes. The extended offline test show some read error (at least at sector 0).
SMART Attributes (like current pending sectors, reallocated event/sectors count, uncorrectableā¦ etc.) can give you a better picture of driveās health
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 - 1075
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 5505
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 5
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 001 001 000 Old_age Always - 68367
10 Spin_Retry_Count 0x0033 210 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4326
192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 646
193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 5123920
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 35 (Min/Max 13/54)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 5
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 38
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 51
222 Loaded_Hours 0x0032 001 001 000 Old_age Always - 42287
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 - 334
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
At first sight 5 reallocated sectors and one pending sector doesnāt look so bad (subject to interpretation). At this stage data is salvageable (well, most of the times, as i.e. a bad sector affecting the superblock of an encrypted drive can ruin your day, IIRC).
But often when thereās one bad there are more to follow. A full disk scan (badblocksā¦) can reveal them. Over time the hard disk (I guess that one is a hard disk) can develop more bad sectors and cause data loss. The pace at what the health of the hard disk is declining and the importance of data can determine the urge to replace it, but the sooner the better.
Even āit doesnāt look so badā I would rather replace it than play the odds.