You are not logged in.
Hello,
I encountered an issue with my SSD today that I need some help with. Here's a step-by-step breakdown of what happened:
I was playing a game when it suddenly crashed. When I tried to launch the game again through Steam, it couldn’t locate the game on the partition where it was installed.
I checked lsblk, but I couldn’t see the disk listed, so I decided to reboot my PC.
During reboot, the system failed to mount the disk. I thought there might be something wrong with the SATA cables, so I switched the SATA port on the motherboard. After doing that, I was able to boot up, and the SSD was detected, but the folders on it were empty.
I then tried checking the disk using smartctl, but the disk became unmounted again, and lsblk no longer showed it.
I attempted to copy data from the SSD to my NVMe, and I managed to copy some files, but then the disk crashed again.
Here are the relevant logs from dmesg:
dmesg | grep -i "sda"
[ 3.563823] sd 7:0:0:0: [sda] 1875385008 512-byte logical blocks: (960 GB/894 GiB)
[ 3.563843] sd 7:0:0:0: [sda] Write Protect is off
[ 3.563848] sd 7:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 3.563868] sd 7:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.563905] sd 7:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[ 3.589946] sda: sda1 sda2
[ 3.590306] sd 7:0:0:0: [sda] Attached SCSI disk
[ 12.194669] EXT4-fs (sda2): mounted filesystem e3a239c6-ae86-43e5-bb5b-e8dc101ff092 r/w with ordered data mode. Quota mode: none.
[ 12.195270] EXT4-fs (sda1): mounted filesystem 732c4903-492a-41c9-af52-3be312ded7c9 r/w with ordered data mode. Quota mode: none.
[ 1179.592707] sd 7:0:0:0: [sda] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 1179.592715] sd 7:0:0:0: [sda] tag#31 Sense Key : Illegal Request [current]
[ 1179.592719] sd 7:0:0:0: [sda] tag#31 Add. Sense: Unaligned write command
[ 1179.592724] sd 7:0:0:0: [sda] tag#31 CDB: Read(10) 28 00 19 ba 0b d8 00 00 68 00
[ 1179.592727] I/O error, dev sda, sector 431623128 op 0x0:(READ) flags 0x80700 phys_seg 7 prio class 0
[ 1181.788628] sd 7:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 1181.788642] sd 7:0:0:0: [sda] tag#21 Sense Key : Illegal Request [current]
[ 1181.788647] sd 7:0:0:0: [sda] tag#21 Add. Sense: Unaligned write command
[ 1181.788652] sd 7:0:0:0: [sda] tag#21 CDB: Read(10) 28 00 16 f0 7a c8 00 00 68 00
[ 1181.788655] I/O error, dev sda, sector 384858824 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[ 1194.178328] sd 7:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=12s
[ 1194.178337] sd 7:0:0:0: [sda] tag#8 Sense Key : Illegal Request [current]
[ 1194.178341] sd 7:0:0:0: [sda] tag#8 Add. Sense: Unaligned write command
[ 1194.178346] sd 7:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 19 b8 73 30 00 00 68 00
[ 1194.178349] I/O error, dev sda, sector 431518512 op 0x0:(READ) flags 0x80700 phys_seg 13 prio class 0
[ 1277.448401] sd 7:0:0:0: [sda] tag#28 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=83s
[ 1277.448410] sd 7:0:0:0: [sda] tag#28 Sense Key : Illegal Request [current]
[ 1277.448415] sd 7:0:0:0: [sda] tag#28 Add. Sense: Unaligned write command
[ 1277.448419] sd 7:0:0:0: [sda] tag#28 CDB: Read(10) 28 00 19 ba fa c8 00 00 18 00
[ 1277.448422] I/O error, dev sda, sector 431684296 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[ 1277.448503] I/O error, dev sda, sector 431684296 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1277.448756] device offline error, dev sda, sector 431684320 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[ 1277.448775] device offline error, dev sda, sector 431684320 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1277.448854] device offline error, dev sda, sector 431684336 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[ 1277.448863] device offline error, dev sda, sector 431684336 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1277.448929] device offline error, dev sda, sector 431684400 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[ 1277.448938] device offline error, dev sda, sector 431684400 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1277.448996] device offline error, dev sda, sector 431684416 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[ 1277.449001] device offline error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[ 1279.792538] EXT4-fs (sda1): shut down requested (2)
[ 1279.792545] Aborting journal on device sda1-8.
[ 1279.792555] Buffer I/O error on dev sda1, logical block 58228736, lost sync page write
[ 1279.792558] JBD2: I/O error when updating journal superblock for sda1-8.
[ 1279.897358] EXT4-fs (sda2): shut down requested (2)
[ 1279.897367] Aborting journal on device sda2-8.
[ 1279.897381] Buffer I/O error on dev sda2, logical block 58228736, lost sync page write
[ 1279.897386] JBD2: I/O error when updating journal superblock for sda2-8.
[ 1279.900665] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1083: inode #20097513: lblock 0: comm rsync: error -5 reading directory block
[ 1279.900699] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1083: inode #20097518: lblock 0: comm rsync: error -5 reading directory block
[ 1279.900708] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1083: inode #20097528: lblock 0: comm rsync: error -5 reading directory block
[ 1279.900718] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1083: inode #20097551: lblock 0: comm rsync: error -5 reading directory block
[ 1279.900730] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1083: inode #20097571: lblock 0: comm rsync: error -5 reading directory block
[ 1279.900753] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1083: inode #20097626: lblock 0: comm rsync: error -5 reading directory block
[ 1279.900766] EXT4-fs warning (device sda1): dx_probe:823: inode #19971310: lblock 0: comm rsync: error -5 reading directory block
[ 1279.900775] EXT4-fs warning (device sda1): dx_probe:823: inode #19971310: lblock 0: comm rsync: error -5 reading directory block
[ 1279.900783] EXT4-fs warning (device sda1): dx_probe:823: inode #19971310: lblock 0: comm rsync: error -5 reading directory block
[ 1279.900791] EXT4-fs warning (device sda1): dx_probe:823: inode #19971310: lblock 0: comm rsync: error -5 reading directory block
[ 1279.941075] EXT4-fs (sda2): unmounting filesystem e3a239c6-ae86-43e5-bb5b-e8dc101ff092.
[ 1279.941397] Buffer I/O error on dev sda2, logical block 0, lost sync page write
[ 1279.941403] EXT4-fs (sda2): I/O error while writing superblock
[ 1279.968159] sd 7:0:0:0: [sda] Synchronizing SCSI cache
[ 1279.968190] sd 7:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OKI am not quite sure whether ssd is dead or not or even what happened to it, so any help is appreciated
Last edited by eingrid (2025-02-16 11:58:40)
Offline
I got another SSD so for a while I will check whether it works, just to know if the issue is with some cable and I missed it, or in system (probably not), or in ssd itself.
Based on my searches it seems to be hardware failure, and there is nothing to do about it, but I would like someone to confirm it
sources :
https://www.linux.org/threads/locked-ssd.48899/
https://bbs.archlinux.org/viewtopic.php?id=284019
Last edited by eingrid (2025-02-16 12:17:57)
Offline
Found some links about it - it might be related with power saving:
https://wiki.archlinux.org/title/Power_ … Management
https://www.reddit.com/r/truenas/commen … e_command/
https://access.redhat.com/solutions/1256863
https://access.redhat.com/solutions/21677
https://docs.oracle.com/cd/E19105-01/st … 918-10.pdf
https://github.com/openzfs/zfs/issues/10094
What is this SSD and how long do you have it? What kernel do you use?
Can you post output of command 'smartctl -x /dev/sda' ? Disk don't have to be mounted.
Last edited by xerxes_ (2025-02-16 12:24:47)
Offline
My current kernel is 6.12.10-arch1-1.
SSD : SSD 960GB Prologix S320 2.5" SATAIII TLC
I've used it for about 8 months.
When I previously run:
smartctl -x /dev/sda
it was just stuck, and currenly I detached that SSD from PC, I will try it today later on and post the output here.
Another interesting thing is that this is the first time this issue occurs and I didn't change anything in a while. Also new SSD is working just fine.
Last edited by eingrid (2025-02-16 13:16:47)
Offline