this post was submitted on 19 Jun 2026
1 points (100.0% liked)

Technology

42758 readers
341 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.

Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.

Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 7 years ago
MODERATORS
MinutePhrase@lemmy.ml
1
is my hdd dying? (lemmy.ml)
submitted 5 hours ago by gary_host_laptop@lemmy.ml to c/technology@lemmy.ml
9 comments fedilink hide all child comments
 
❯ mount | grep phaedra
/dev/sdb1 on /mnt/phaedra type ext4 (rw,nosuid,nodev,relatime,seclabel,emergency_ro,x-systemd.device-timeout=30,x-gvfs-show)

❯ dmesg | tail -100
dmesg: read kernel buffer failed: Operation not permitted

❯ journalctl -k -n 100
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: cmd 60/80:18:b8:33:76/>
                                               res 40/00:01:00:4f:c2/>
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: status: { DRDY }
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: failed command: READ F>
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: cmd 60/20:c8:b8:14:a4/>
                                               res 40/00:01:00:4f:c2/>
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: status: { DRDY }
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: failed command: READ F>
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: cmd 60/08:f8:48:c5:10/>
                                               res 40/00:01:00:4f:c2/>
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: status: { DRDY }
Jun 19 09:52:59 ghost-desktop kernel: ata2: hard resetting link
Jun 19 09:53:02 ghost-desktop kernel: ata2: SATA link up 1.5 Gbps (SS>
Jun 19 09:53:03 ghost-desktop kernel: ata2.00: configured for UDMA/33
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#3 FAILED >
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#3 Sense K>
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#3 Add. Se>
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#3 CDB: Re>
Jun 19 09:53:03 ghost-desktop kernel: I/O error, dev sdb, sector 7423>
lines 1-19
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: cmd 60/80:18:b8:33:76/00:00:ba:01:00/40 tag 3 ncq dma 65536 in
                                               res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: status: { DRDY }
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: failed command: READ FPDMA QUEUED
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: cmd 60/20:c8:b8:14:a4/00:00:80:00:00/40 tag 25 ncq dma 16384 in
                                               res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: status: { DRDY }
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: failed command: READ FPDMA QUEUED
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: cmd 60/08:f8:48:c5:10/00:00:01:00:00/40 tag 31 ncq dma 4096 in
                                               res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Jun 19 09:52:59 ghost-desktop kernel: ata2.00: status: { DRDY }
Jun 19 09:52:59 ghost-desktop kernel: ata2: hard resetting link
Jun 19 09:53:02 ghost-desktop kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jun 19 09:53:03 ghost-desktop kernel: ata2.00: configured for UDMA/33
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=4s
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#3 Sense Key : Aborted Command [current] 
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#3 Add. Sense: No additional sense information
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#3 CDB: Read(16) 88 00 00 00 00 01 ba 76 33 b8 00 00 00 80 00 00
Jun 19 09:53:03 ghost-desktop kernel: I/O error, dev sdb, sector 7423275960 op 0x0:(READ) flags 0x80700 phys_seg 16 prio class 2
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#25 Sense Key : Aborted Command [current] 
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#25 Add. Sense: No additional sense information
Jun 19 09:53:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#25 CDB: Read(16) 88 00 00 00 00 00 80 a4 14 b8 00 00 00 20 00 00
Jun 19 09:53:03 ghost-desktop kernel: I/O error, dev sdb, sector 2158236856 op 0x0:(READ) flags 0x880700 phys_seg 4 prio class 2
Jun 19 09:53:03 ghost-desktop kernel: ata2: EH complete
Jun 19 10:47:51 ghost-desktop kernel: EXT4-fs error (device sdb1): ext4_validate_block_bitmap:423: comm pool-475: bg 8231: bad block bitmap checksum
Jun 19 10:49:03 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#29 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=33s
Jun 19 10:49:04 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#29 CDB: Write(16) 8a 00 00 00 00 00 6d f6 48 00 00 00 20 00 00 00
Jun 19 10:49:04 ghost-desktop kernel: I/O error, dev sdb, sector 1844856832 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 2
Jun 19 10:49:04 ghost-desktop kernel: EXT4-fs warning (device sdb1): ext4_end_bio:369: I/O error 10 writing to inode 67371715 starting block 230607104)
Jun 19 10:49:04 ghost-desktop kernel: EXT4-fs (sdb1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 67371715, error -5)
Jun 19 10:49:04 ghost-desktop kernel: buffer_io_error: 7158 callbacks suppressed
Jun 19 10:49:04 ghost-desktop kernel: Buffer I/O error on device sdb1, logical block 230606848
Jun 19 10:49:04 ghost-desktop kernel: Buffer I/O error on device sdb1, logical block 230606849
Jun 19 10:49:04 ghost-desktop kernel: Buffer I/O error on device sdb1, logical block 230606850
Jun 19 10:49:04 ghost-desktop kernel: Buffer I/O error on device sdb1, logical block 230606851
Jun 19 10:49:04 ghost-desktop kernel: Buffer I/O error on device sdb1, logical block 230606852
Jun 19 10:49:04 ghost-desktop kernel: Buffer I/O error on device sdb1, logical block 230606853
Jun 19 10:49:04 ghost-desktop kernel: Buffer I/O error on device sdb1, logical block 230606854
Jun 19 10:49:04 ghost-desktop kernel: Buffer I/O error on device sdb1, logical block 230606855
Jun 19 10:49:04 ghost-desktop kernel: Buffer I/O error on device sdb1, logical block 230606856
Jun 19 10:49:04 ghost-desktop kernel: Buffer I/O error on device sdb1, logical block 230606857
Jun 19 10:49:51 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=42s
Jun 19 10:49:51 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#4 CDB: Write(16) 8a 00 00 00 00 00 6e 0a a8 00 00 00 20 00 00 00
Jun 19 10:49:51 ghost-desktop kernel: I/O error, dev sdb, sector 1846192128 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 2
Jun 19 10:49:51 ghost-desktop kernel: EXT4-fs warning (device sdb1): ext4_end_bio:369: I/O error 10 writing to inode 67371714 starting block 230774016)
Jun 19 10:49:51 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#5 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=42s
Jun 19 10:49:51 ghost-desktop kernel: sd 1:0:0:0: [sdb] tag#5 CDB: Write(16) 8a 00 00 00 00 00 6e 98 48 00 00 00 20 00 00 00
Jun 19 10:49:51 ghost-desktop kernel: I/O error, dev sdb, sector 1855473664 op 0x1:(WRITE) flags 0x4000 phys_seg 64 prio class 2


❯ sudo smartctl -a /dev/sdb
[sudo] password for ghost_user: 
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-7.0.12-100.fc43.x86_64] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba X300
Device Model:     TOSHIBA HDWE140
Serial Number:    41IUK67JFBRG
LU WWN Device Id: 5 000039 abc58066c
Firmware Version: FP1R
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.5/5852
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Fri Jun 19 11:08:11 2026 -03
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:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
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: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 481) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

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       -       524
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       18344
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       120
  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   036   036   000    Old_age   Always       -       25792
 10 Spin_Retry_Count        0x0033   253   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       18340
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       13
192 Power-Off_Retract_Count 0x0032   071   071   000    Old_age   Always       -       14999
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       18774
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       40 (Min/Max 11/61)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       15
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       0
222 Loaded_Hours            0x0032   037   037   000    Old_age   Always       -       25500
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       -       545
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       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  Short offline       Completed without error       00%     15477         -

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.

The above only provides legacy SMART information - try 'smartctl -x' for more
top 9 comments
sorted by: hot top controversial new old
[–] sgh@lemmy.ml 3 points 4 hours ago (1 children)

Reallocated sectors, yup, it's dying...

[–] gary_host_laptop@lemmy.ml 0 points 4 hours ago (2 children)

SATA Version is: SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)

while my other drives are:

sda: current 6.0 Gb/s sdc: current 6.0 Gb/s

Also, the kernel reported a hard link reset before the drive ended up at 1.5 Gb/s.

Could a bad SATA cable, SATA port, or power connection explain the link resets, fallback to 1.5 Gb/s, and subsequent filesystem errors, even though SMART doesn't show CRC errors? Or do you think it's dying anyway?

[–] cmnybo@discuss.tchncs.de 0 points 1 hour ago (1 children)

A bad SATA cable can cause the link errors, but it wouldn't cause sectors to be reallocated.

[–] gary_host_laptop@lemmy.ml 1 points 41 minutes ago

do you think maybe a bad sata cable damage the disk and that is the link between the two?

[–] KssioAug@lemmy.dbzer0.com 2 points 3 hours ago (1 children)

What gives it in is the ID 5, Reallocated_Sector_Ct. In your log, there were found 120 reallocated sectors, which indicates pretty much literally a physical damage in the hard drive. The drive detects this damaged sectors and move the data to a different one.

[–] gary_host_laptop@lemmy.ml 1 points 3 hours ago (1 children)

could i keep using it in read only mode until i manage to buy a backup? its my biggest drive 4tb and i dont have anywhere else to back it up :(

[–] KssioAug@lemmy.dbzer0.com 3 points 3 hours ago

Not recommended. Even if you're not writing data to the drive, when you read it the physical components keep working, which can lead to more damage until you lose everything. I would recommend you to back up, right now, your most important data to any other drive you have, then unplug this damaged one, buy a new drive, and then backup your stuff on it following a 'emergency' order (the most important and non replaceable files first, and then the less important stuff).

[–] Shadow@lemmy.ca 3 points 5 hours ago (1 children)

Most likely. You could try in another machine to rule out cable or controller issues.

[–] gary_host_laptop@lemmy.ml 1 points 4 hours ago

SATA Version is: SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)

while my other drives are:

sda: current 6.0 Gb/s sdc: current 6.0 Gb/s

Also, the kernel reported a hard link reset before the drive ended up at 1.5 Gb/s.

Could a bad SATA cable, SATA port, or power connection explain the link resets, fallback to 1.5 Gb/s, and subsequent filesystem errors, even though SMART doesn't show CRC errors? Or do you think it's dying anyway?