Couple of days ago I spotted the following issue in journalctl
smartd[319]: Device: /dev/sdb [SAT], 2 Currently unreadable (pending) sectors
sudo smartctl -a /dev/sdb
said
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Elements / My Passport (USB, AF)
Device Model: WDC WD50NDZW-11A8JS0
Serial Number: WD-WX52D8163UPC
LU WWN Device Id: 5 0014ee 2bf4619ea
Firmware Version: 01.01A01
User Capacity: 5,000,947,523,584 bytes [5.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
TRIM Command: Available, deterministic
Device is: In smartctl database 7.3/5319
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sat Mar 11 18:29:46 2023 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 2
3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 4658
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 947
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 10459
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 218
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 211
193 Load_Cycle_Count 0x0032 116 116 000 Old_age Always - 253807
194 Temperature_Celsius 0x0022 105 101 000 Old_age Always - 47
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 90% 10424 733750280
# 2 Extended offline Completed: read failure 90% 10401 73375028
So I had to learn about this issue, because I encountered first time bad sectors on my HDD. After some reading I ended up with fsck -vcck
from wiki.archlinux.org/title/Badblocks#During_filesystem_check
$ sudo fsck -vcck /dev/sdb1
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Checking for bad blocks (non-destructive read-write test)
Testing with random pattern: 99.74% done, 34:36:43 elapsed. (0/0/0 errors)
Hope the above fsck
will solve that smartd error
UPDATE
After bunch of optimizes
Inode 69271555 extent tree (at level 1) could be narrower. Optimize<y>? yes
Inode 69271558 extent tree (at level 2) could be narrower. Optimize<y>? yes
Inode 69271562 extent tree (at level 1) could be narrower. Optimize<y>? yes
Inode 69271563 extent tree (at level 2) could be narrower. Optimize<y>? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
75042 inodes used (0.05%, out of 152616960)
796 non-contiguous files (1.1%)
50 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 70463/682/30
293501388 blocks used (24.04%, out of 1220933888)
0 bad blocks
159 large files
61214 regular files
8493 directories
0 character device files
0 block device files
0 fifos
0 links
5322 symbolic links (3855 fast symbolic links)
4 sockets
------------
75033 files
And finally SMART says Completed without error
after extended self-test
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% 10490 -
# 2 Extended offline Completed: read failure 90% 10424 733750280
# 3 Extended offline Completed: read failure 90% 10401 733750280
2 of 2 failed self-tests are outdated by newer successful extended offline self-test # 1