-
Notifications
You must be signed in to change notification settings - Fork 8
Henryk Paluch edited this page Aug 12, 2024
·
1 revision
I'm now playing with old SATA 1 Seagate 1TB Barracuda. I know that there is one very old and
uncorrectable bad sector as can be seen from smartctl -a
output:
40 51 01 62 14 56 40 Error: UNC at LBA = 0x00561462 = 5641314
However recently when I start playing with Fedora 40 and LibVirt there was very new error in dmesg:
ata2.00: configured for UDMA/133
ata2.00: exception Emask 0x10 SAct 0xffffffff SErr 0x4010000 action 0xe frozen
ata2.00: irq_stat 0x80400040, connection status changed
ata2: SError: { PHYRdyChg DevExch }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:00:18:60:de/00:00:02:00:00/40 tag 0 ncq dma 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:08:28:60:de/00:00:02:00:00/40 tag 1 ncq dma 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
ata2.00: status: { DRDY }
ta2: hard resetting link
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: configured for UDMA/100
sd 1:0:0:0: [sdb] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
sd 1:0:0:0: [sdb] tag#2 Sense Key : Illegal Request [current]
sd 1:0:0:0: [sdb] tag#2 Add. Sense: Unaligned write command
sd 1:0:0:0: [sdb] tag#2 CDB: Read(10) 28 00 00 89 e9 c8 00 01 00 00
I/O error, dev sdb, sector 9038280 op 0x0:(READ) flags 0x80700 phys_seg 31 prio class 2
When I googled for Unaligned write command
I found quite weird reports:
Some suggest that drive is dying while other recommends to disable ALPM (I should try it, because this HDD is very old so it definitely knows nothing about ALPM)
Copyright © Henryk Paluch. All rights reserved.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License