You are not logged in.
- Topics: Active | Unanswered
#1 2017-08-04 09:56:31
- sokl
- Member
- Registered: 2015-02-02
- Posts: 11
[SOLVED] How to make sure SSD isn't busted?
After power outage system was booting painfully slow - instead of 10s (inc. fsck), it took 30m. (I've got fsck on every boot.)
I plugged ssd into another PC to fsck manually and it fixed a few errors. After that fsck stopped recognizing / as ext4 (lsblk -f still does).
/home is still mountable, but no files are readable, gives this:
blk_update_request: i/o error, dev sda, sector 123456789
I do not care for files recovery. All I need is a method to make sure that power was lost during some i/o operations and there's no damage to the physical disk.
I thought about formatting the disk and filling it with copies of a big file and then hash-check them. Should I try?
Haven't done anything yet, waiting for suggestions.
Last edited by sokl (2017-08-06 06:01:39)
Offline
#2 2017-08-04 10:16:36
- graysky
- Wiki Maintainer
- From: :wq
- Registered: 2008-12-01
- Posts: 10,734
- Website
Re: [SOLVED] How to make sure SSD isn't busted?
Use smartctl to do a long disk check firstly. The IO error is not a good sign. Is the drive under warrantee? If no data is important on it try filling up from /dev/zero then reformat and watch dmesg for errors. You could try the checksum test as well. Beyond the SMART test, I do not know of a way to verify physical damage to a SSD. For spinners, badblocks is how to do it... perhaps it apples here as well. Did you consult google?
Last edited by graysky (2017-08-04 10:18:03)
Offline
#3 2017-08-04 14:52:27
- R00KIE
- Forum Fellow
- From: Between a computer and a chair
- Registered: 2008-09-14
- Posts: 4,734
Re: [SOLVED] How to make sure SSD isn't busted?
To add to what graysky has said, check the smart status, maybe some attribute will be bellow the threshold already, also try all the smart tests your ssd supports, the order I would use is: conveyance, short, long, offline. You should let the drive stay idle for a while, after an unannounced power cut the drive may need to rebuild some internal table and that might take a while and make the drive less reponsive.
You could also try an ata security erase as that _should_ make sure to erase all flash cells, but you can also try giving it a workout with badblocks, if you do decide to use badblocks then I'd say you can skip the step of filling the drive with zeros from /dev/zero as badblocks will do that as a last test. If badblocks does not find anything wrong, it might also be a good idea to either do an ata security erase or a blkdiscard of the whole drive before putting it to use again.
If all of the above fails and the drive is still under warranty then just go ahead and exchange it.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
#4 2017-08-04 16:56:51
- sokl
- Member
- Registered: 2015-02-02
- Posts: 11
Re: [SOLVED] How to make sure SSD isn't busted?
The disk is 6.5y.o.
Smart was giving similar, if not exact stats, since I first checked it when it was 1 y.o.
I don't think Smart ever read the disk correctly.
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 Unknown_JMF_Attribute 0x0007 100 100 050 Pre-fail Always - 0
5 Reallocated_Sector_Ct 0x0013 100 100 050 Pre-fail Always - 0
7 Unknown_JMF_Attribute 0x000b 100 100 050 Pre-fail Always - 0
8 Unknown_JMF_Attribute 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 56218
10 Unknown_JMF_Attribute 0x0013 100 100 050 Pre-fail Always - 0
12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 714
168 SATA_Phy_Error_Count 0x0012 100 100 000 Old_age Always - 0
175 Bad_Cluster_Table_Count 0x0003 100 100 010 Pre-fail Always - 0
192 Unexpect_Power_Loss_Ct 0x0012 100 100 000 Old_age Always - 0
194 Temperature_Celsius 0x0022 038 100 020 Old_age Always - 38 (Min/Max 35/45)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
240 Unknown_JMF_Attribute 0x0013 100 100 050 Pre-fail Always - 0
170 Bad_Block_Count 0x0003 100 100 010 Pre-fail Always - 0 164 0
173 Erase_Count 0x0012 100 100 000 Old_age Always - 5 35157 30700It was used very lightly and had almost no writing done on it.
I filled it with videos and md5 sums checked out. I'll plug it off for the night and compare hashes a few times tomorrow.
------
R00KIE, isn't badblocks for HDDs only?
Offline
#5 2017-08-05 02:40:15
- R00KIE
- Forum Fellow
- From: Between a computer and a chair
- Registered: 2008-09-14
- Posts: 4,734
Re: [SOLVED] How to make sure SSD isn't busted?
Those smart attributes seem ok. Regarding badblocks it doesn't care what the underlying media is, it just tests the whole media. In the case of an ssd it _could_ possibly uncover any firmware bug where bad flash cells are not detected and replaced by spare cells, or at the very least might force reallocation.
That said, make sure you have the latest firmware installed on the ssd, it seems to be common for reliability problems (mostly corner cases I hope/assume) to be solved after the ssd is on sale, sometimes well after it was first on sale.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
#6 2017-08-05 09:10:41
- sokl
- Member
- Registered: 2015-02-02
- Posts: 11
Re: [SOLVED] How to make sure SSD isn't busted?
Updated firmware, although it fixed only inconsequential bugs.
badblocks -wsv found no bad blocks.
Created ext4 and tried rsyncing backuped system to the disk
rsync -aAXv /backup /mnt/1
and in the process:
rsync: write failed on "/mnt/1/home/u/.node-gyp/0.12.5/tools/wrk/deps/luajit/dynasm/dasm_x86.h": Read-only file system (30)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]fdisk didn't see ssd anymore.
dmesg
[ 335.135137] sdb: sdb1
[ 338.556929] sdb: sdb1
[ 391.758711] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 647.599460] perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79800
[ 704.689214] ata2.00: exception Emask 0x50 SAct 0x5fffffff SErr 0x4890800 action 0xe frozen
[ 704.689223] ata2.00: irq_stat 0x08400040, interface fatal error, connection status changed
[ 704.689228] ata2: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
[ 704.689234] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689244] ata2.00: cmd 61/40:00:00:68:48/05:00:00:00:00/40 tag 0 ncq dma 688128 out
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689249] ata2.00: status: { DRDY }
[ 704.689253] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689263] ata2.00: cmd 61/c0:08:40:6d:48/02:00:00:00:00/40 tag 1 ncq dma 360448 out
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689267] ata2.00: status: { DRDY }
[ 704.689271] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689280] ata2.00: cmd 61/00:10:00:70:48/08:00:00:00:00/40 tag 2 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689285] ata2.00: status: { DRDY }
[ 704.689289] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689299] ata2.00: cmd 61/00:18:00:78:48/08:00:00:00:00/40 tag 3 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689303] ata2.00: status: { DRDY }
[ 704.689307] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689318] ata2.00: cmd 61/00:20:00:80:48/08:00:00:00:00/40 tag 4 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689321] ata2.00: status: { DRDY }
[ 704.689324] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689329] ata2.00: cmd 61/00:28:00:88:48/08:00:00:00:00/40 tag 5 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689332] ata2.00: status: { DRDY }
[ 704.689335] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689340] ata2.00: cmd 61/00:30:00:90:48/08:00:00:00:00/40 tag 6 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689343] ata2.00: status: { DRDY }
[ 704.689346] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689351] ata2.00: cmd 61/00:38:00:98:48/08:00:00:00:00/40 tag 7 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689354] ata2.00: status: { DRDY }
[ 704.689356] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689362] ata2.00: cmd 61/00:40:00:a0:48/08:00:00:00:00/40 tag 8 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689365] ata2.00: status: { DRDY }
[ 704.689367] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689373] ata2.00: cmd 61/00:48:00:a8:48/08:00:00:00:00/40 tag 9 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689376] ata2.00: status: { DRDY }
[ 704.689379] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689384] ata2.00: cmd 61/00:50:00:b0:48/08:00:00:00:00/40 tag 10 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689387] ata2.00: status: { DRDY }
[ 704.689389] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689395] ata2.00: cmd 61/00:58:00:b8:48/08:00:00:00:00/40 tag 11 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689398] ata2.00: status: { DRDY }
[ 704.689401] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689406] ata2.00: cmd 61/00:60:00:c0:48/08:00:00:00:00/40 tag 12 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689409] ata2.00: status: { DRDY }
[ 704.689412] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689417] ata2.00: cmd 61/00:68:00:c8:48/08:00:00:00:00/40 tag 13 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689420] ata2.00: status: { DRDY }
[ 704.689423] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689428] ata2.00: cmd 61/00:70:00:d0:48/08:00:00:00:00/40 tag 14 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689431] ata2.00: status: { DRDY }
[ 704.689434] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689440] ata2.00: cmd 61/00:78:00:d8:48/08:00:00:00:00/40 tag 15 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689442] ata2.00: status: { DRDY }
[ 704.689445] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689451] ata2.00: cmd 61/00:80:00:e0:48/08:00:00:00:00/40 tag 16 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689453] ata2.00: status: { DRDY }
[ 704.689456] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689461] ata2.00: cmd 61/00:88:00:e8:48/08:00:00:00:00/40 tag 17 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689464] ata2.00: status: { DRDY }
[ 704.689467] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689521] ata2.00: cmd 61/00:90:00:f0:48/08:00:00:00:00/40 tag 18 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689523] ata2.00: status: { DRDY }
[ 704.689526] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689530] ata2.00: cmd 61/00:98:00:f8:48/08:00:00:00:00/40 tag 19 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689533] ata2.00: status: { DRDY }
[ 704.689535] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689540] ata2.00: cmd 61/00:a0:00:00:49/08:00:00:00:00/40 tag 20 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689542] ata2.00: status: { DRDY }
[ 704.689544] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689549] ata2.00: cmd 61/00:a8:00:08:49/08:00:00:00:00/40 tag 21 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689551] ata2.00: status: { DRDY }
[ 704.689553] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689557] ata2.00: cmd 61/00:b0:00:10:49/08:00:00:00:00/40 tag 22 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689559] ata2.00: status: { DRDY }
[ 704.689561] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689566] ata2.00: cmd 61/00:b8:00:18:49/08:00:00:00:00/40 tag 23 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689568] ata2.00: status: { DRDY }
[ 704.689570] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689575] ata2.00: cmd 61/00:c0:00:20:49/08:00:00:00:00/40 tag 24 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689577] ata2.00: status: { DRDY }
[ 704.689579] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689584] ata2.00: cmd 61/00:c8:00:28:49/08:00:00:00:00/40 tag 25 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689586] ata2.00: status: { DRDY }
[ 704.689588] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689593] ata2.00: cmd 61/08:d0:00:30:49/06:00:00:00:00/40 tag 26 ncq dma 790528 out
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689595] ata2.00: status: { DRDY }
[ 704.689597] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689602] ata2.00: cmd 61/f8:d8:08:36:49/09:00:00:00:00/40 tag 27 ncq dma 1306624 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689605] ata2.00: status: { DRDY }
[ 704.689607] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689611] ata2.00: cmd 61/00:e0:00:40:49/08:00:00:00:00/40 tag 28 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689614] ata2.00: status: { DRDY }
[ 704.689616] ata2.00: failed command: WRITE FPDMA QUEUED
[ 704.689621] ata2.00: cmd 61/00:f0:00:60:48/08:00:00:00:00/40 tag 30 ncq dma 1048576 ou
res 40/00:00:08:36:49/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 704.689623] ata2.00: status: { DRDY }
[ 704.689628] ata2: hard resetting link
[ 705.409065] ata2: SATA link down (SStatus 0 SControl 300)
[ 710.565266] ata2: hard resetting link
[ 710.878626] ata2: SATA link down (SStatus 0 SControl 300)
[ 710.878635] ata2: limiting SATA link speed to 1.5 Gbps
[ 715.898089] ata2: hard resetting link
[ 716.211320] ata2: SATA link down (SStatus 0 SControl 310)
[ 716.211338] ata2.00: disabled
[ 716.211438] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 716.211443] sd 1:0:0:0: [sdb] tag#0 Sense Key : 0x5 [current]
[ 716.211446] sd 1:0:0:0: [sdb] tag#0 ASC=0x21 ASCQ=0x4
[ 716.211450] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 00 48 68 00 00 05 40 00
[ 716.211453] blk_update_request: I/O error, dev sdb, sector 4745216
[ 716.211474] sd 1:0:0:0: rejecting I/O to offline device
[ 716.211480] sd 1:0:0:0: [sdb] killing request
[ 716.211490] sd 1:0:0:0: rejecting I/O to offline device
[ 716.211501] EXT4-fs warning (device sdb1): ext4_end_bio:322: I/O error -5 writing to inode 398418 (offset 931135488 size 8388608 starting block 600832)
[ 716.211504] Buffer I/O error on device sdb1, logical block 600320
[ 716.211512] Buffer I/O error on device sdb1, logical block 600321
[ 716.211515] Buffer I/O error on device sdb1, logical block 600322
[ 716.211518] Buffer I/O error on device sdb1, logical block 600323
[ 716.211521] Buffer I/O error on device sdb1, logical block 600324
[ 716.211524] Buffer I/O error on device sdb1, logical block 600325
[ 716.211527] Buffer I/O error on device sdb1, logical block 600326
[ 716.211530] Buffer I/O error on device sdb1, logical block 600327
[ 716.211533] Buffer I/O error on device sdb1, logical block 600328
[ 716.211535] Buffer I/O error on device sdb1, logical block 600329
[ 716.211690] sd 1:0:0:0: rejecting I/O to offline device
[ 716.211698] EXT4-fs warning (device sdb1): ext4_end_bio:322: I/O error -5 writing to inode 398418 (offset 931135488 size 8388608 starting block 601088)
[ 716.211852] sd 1:0:0:0: rejecting I/O to offline device
[ 716.211860] EXT4-fs warning (device sdb1): ext4_end_bio:322: I/O error -5 writing to inode 398418 (offset 931135488 size 8388608 starting block 601344)
[ 716.212022] sd 1:0:0:0: rejecting I/O to offline device
[ 716.212030] EXT4-fs warning (device sdb1): ext4_end_bio:322: I/O error -5 writing to inode 398418 (offset 931135488 size 8388608 starting block 601600)
[ 716.212192] sd 1:0:0:0: rejecting I/O to offline device
[ 716.212199] EXT4-fs warning (device sdb1): ext4_end_bio:322: I/O error -5 writing to inode 398418 (offset 931135488 size 8388608 starting block 601856)
[ 716.212355] sd 1:0:0:0: rejecting I/O to offline device
[ 716.212362] EXT4-fs warning (device sdb1): ext4_end_bio:322: I/O error -5 writing to inode 398418 (offset 931135488 size 8388608 starting block 602112)
[ 716.212516] sd 1:0:0:0: rejecting I/O to offline device
[ 716.212523] EXT4-fs warning (device sdb1): ext4_end_bio:322: I/O error -5 writing to inode 398418 (offset 931135488 size 8388608 starting block 602368)
[ 716.212680] sd 1:0:0:0: rejecting I/O to offline device
[ 716.212687] EXT4-fs warning (device sdb1): ext4_end_bio:322: I/O error -5 writing to inode 398418 (offset 939524096 size 8388608 starting block 602624)
[ 716.212850] sd 1:0:0:0: rejecting I/O to offline device
[ 716.212857] EXT4-fs warning (device sdb1): ext4_end_bio:322: I/O error -5 writing to inode 398418 (offset 939524096 size 8388608 starting block 602880)
[ 716.213021] sd 1:0:0:0: rejecting I/O to offline device
[ 716.213028] EXT4-fs warning (device sdb1): ext4_end_bio:322: I/O error -5 writing to inode 398418 (offset 939524096 size 8388608 starting block 603136)
[ 716.213186] sd 1:0:0:0: rejecting I/O to offline device
[ 716.213348] sd 1:0:0:0: rejecting I/O to offline device
[ 716.213511] sd 1:0:0:0: rejecting I/O to offline device
[ 716.213519] sd 1:0:0:0: rejecting I/O to offline device
[ 716.213696] sd 1:0:0:0: rejecting I/O to offline device
[ 716.213877] sd 1:0:0:0: rejecting I/O to offline device
[ 716.214058] sd 1:0:0:0: rejecting I/O to offline device
[ 716.214223] sd 1:0:0:0: rejecting I/O to offline device
[ 716.214388] sd 1:0:0:0: rejecting I/O to offline device
[ 716.214548] sd 1:0:0:0: rejecting I/O to offline device
[ 716.214734] sd 1:0:0:0: rejecting I/O to offline device
[ 716.214745] sd 1:0:0:0: rejecting I/O to offline device
[ 716.215070] sd 1:0:0:0: rejecting I/O to offline device
[ 716.215230] sd 1:0:0:0: rejecting I/O to offline device
[ 716.215394] sd 1:0:0:0: rejecting I/O to offline device
[ 716.215402] sd 1:0:0:0: rejecting I/O to offline device
[ 716.215735] sd 1:0:0:0: rejecting I/O to offline device
[ 716.215895] sd 1:0:0:0: rejecting I/O to offline device
[ 716.216054] sd 1:0:0:0: rejecting I/O to offline device
[ 716.216223] sd 1:0:0:0: rejecting I/O to offline device
[ 716.216386] sd 1:0:0:0: rejecting I/O to offline device
[ 716.216546] sd 1:0:0:0: rejecting I/O to offline device
[ 716.216703] sd 1:0:0:0: rejecting I/O to offline device
[ 716.216865] sd 1:0:0:0: rejecting I/O to offline device
[ 716.217032] sd 1:0:0:0: rejecting I/O to offline device
[ 716.217191] sd 1:0:0:0: rejecting I/O to offline device
[ 716.217348] sd 1:0:0:0: rejecting I/O to offline device
[ 716.217510] sd 1:0:0:0: rejecting I/O to offline device
[ 716.217519] sd 1:0:0:0: rejecting I/O to offline device
[ 716.217693] sd 1:0:0:0: rejecting I/O to offline device
[ 716.217856] sd 1:0:0:0: rejecting I/O to offline device
[ 716.218021] sd 1:0:0:0: rejecting I/O to offline device
[ 716.218182] sd 1:0:0:0: rejecting I/O to offline device
[ 716.218191] sd 1:0:0:0: rejecting I/O to offline device
[ 716.218520] sd 1:0:0:0: rejecting I/O to offline device
[ 716.218681] sd 1:0:0:0: rejecting I/O to offline device
[ 716.218840] sd 1:0:0:0: rejecting I/O to offline device
[ 716.219003] sd 1:0:0:0: rejecting I/O to offline device
[ 716.219177] sd 1:0:0:0: rejecting I/O to offline device
[ 716.219338] sd 1:0:0:0: rejecting I/O to offline device
[ 716.219498] sd 1:0:0:0: rejecting I/O to offline device
[ 716.219507] sd 1:0:0:0: rejecting I/O to offline device
[ 716.219840] sd 1:0:0:0: rejecting I/O to offline device
[ 716.220006] sd 1:0:0:0: rejecting I/O to offline device
[ 716.220165] sd 1:0:0:0: rejecting I/O to offline device
[ 716.220326] sd 1:0:0:0: rejecting I/O to offline device
[ 716.220494] sd 1:0:0:0: rejecting I/O to offline device
[ 716.220656] sd 1:0:0:0: rejecting I/O to offline device
[ 716.220815] sd 1:0:0:0: rejecting I/O to offline device
[ 716.220974] sd 1:0:0:0: rejecting I/O to offline device
[ 716.221133] sd 1:0:0:0: rejecting I/O to offline device
[ 716.221295] sd 1:0:0:0: rejecting I/O to offline device
[ 716.221465] sd 1:0:0:0: rejecting I/O to offline device
[ 716.221626] sd 1:0:0:0: rejecting I/O to offline device
[ 716.221782] sd 1:0:0:0: rejecting I/O to offline device
[ 716.221790] sd 1:0:0:0: rejecting I/O to offline device
[ 716.221971] sd 1:0:0:0: rejecting I/O to offline device
[ 716.222135] sd 1:0:0:0: rejecting I/O to offline device
[ 716.222293] sd 1:0:0:0: rejecting I/O to offline device
[ 716.222452] sd 1:0:0:0: rejecting I/O to offline device
[ 716.222619] sd 1:0:0:0: rejecting I/O to offline device
[ 716.222780] sd 1:0:0:0: rejecting I/O to offline device
[ 716.222938] sd 1:0:0:0: rejecting I/O to offline device
[ 716.223096] sd 1:0:0:0: rejecting I/O to offline device
[ 716.223258] sd 1:0:0:0: rejecting I/O to offline device
[ 716.223424] sd 1:0:0:0: rejecting I/O to offline device
[ 716.223583] sd 1:0:0:0: rejecting I/O to offline device
[ 716.223744] sd 1:0:0:0: rejecting I/O to offline device
[ 716.223904] sd 1:0:0:0: rejecting I/O to offline device
[ 716.224069] sd 1:0:0:0: rejecting I/O to offline device
[ 716.224236] sd 1:0:0:0: rejecting I/O to offline device
[ 716.224402] sd 1:0:0:0: rejecting I/O to offline device
[ 716.224560] sd 1:0:0:0: rejecting I/O to offline device
[ 716.224742] sd 1:0:0:0: rejecting I/O to offline device
[ 716.224905] sd 1:0:0:0: rejecting I/O to offline device
[ 716.225064] sd 1:0:0:0: rejecting I/O to offline device
[ 716.225226] sd 1:0:0:0: rejecting I/O to offline device
[ 716.225388] sd 1:0:0:0: rejecting I/O to offline device
[ 716.225547] sd 1:0:0:0: rejecting I/O to offline device
[ 716.225707] sd 1:0:0:0: rejecting I/O to offline device
[ 716.225867] sd 1:0:0:0: rejecting I/O to offline device
[ 716.226033] sd 1:0:0:0: rejecting I/O to offline device
[ 716.226195] sd 1:0:0:0: rejecting I/O to offline device
[ 716.226356] sd 1:0:0:0: rejecting I/O to offline device
[ 716.226516] sd 1:0:0:0: rejecting I/O to offline device
[ 716.226673] sd 1:0:0:0: rejecting I/O to offline device
[ 716.226682] sd 1:0:0:0: rejecting I/O to offline device
[ 716.227012] sd 1:0:0:0: rejecting I/O to offline device
[ 716.227173] sd 1:0:0:0: rejecting I/O to offline device
[ 716.227333] sd 1:0:0:0: rejecting I/O to offline device
[ 716.227342] sd 1:0:0:0: rejecting I/O to offline device
[ 716.227674] sd 1:0:0:0: rejecting I/O to offline device
[ 716.227842] sd 1:0:0:0: rejecting I/O to offline device
[ 716.228012] sd 1:0:0:0: rejecting I/O to offline device
[ 716.228178] sd 1:0:0:0: rejecting I/O to offline device
[ 716.228339] sd 1:0:0:0: rejecting I/O to offline device
[ 716.228500] sd 1:0:0:0: rejecting I/O to offline device
[ 716.228660] sd 1:0:0:0: rejecting I/O to offline device
[ 716.228820] sd 1:0:0:0: rejecting I/O to offline device
[ 716.228982] sd 1:0:0:0: rejecting I/O to offline device
[ 716.229141] sd 1:0:0:0: rejecting I/O to offline device
[ 716.229300] sd 1:0:0:0: rejecting I/O to offline device
[ 716.229527] sd 1:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[ 716.229533] sd 1:0:0:0: [sdb] CDB: opcode=0x2a 2a 00 00 49 48 00 00 08 00 00
[ 716.229536] blk_update_request: I/O error, dev sdb, sector 4802560
[ 716.229763] sd 1:0:0:0: rejecting I/O to offline device
[ 716.229914] sd 1:0:0:0: [sdb] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 716.229916] sd 1:0:0:0: [sdb] tag#1 Sense Key : 0x5 [current]
[ 716.229917] sd 1:0:0:0: [sdb] tag#1 ASC=0x21 ASCQ=0x4
[ 716.229919] sd 1:0:0:0: [sdb] tag#1 CDB: opcode=0x2a 2a 00 00 48 6d 40 00 02 c0 00
[ 716.229920] blk_update_request: I/O error, dev sdb, sector 4746560
[ 716.230045] sd 1:0:0:0: [sdb] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 716.230046] sd 1:0:0:0: [sdb] tag#2 Sense Key : 0x5 [current]
[ 716.230047] sd 1:0:0:0: [sdb] tag#2 ASC=0x21 ASCQ=0x4
[ 716.230049] sd 1:0:0:0: [sdb] tag#2 CDB: opcode=0x2a 2a 00 00 48 70 00 00 08 00 00
[ 716.230050] blk_update_request: I/O error, dev sdb, sector 4747264
[ 716.230153] sd 1:0:0:0: [sdb] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 716.230154] sd 1:0:0:0: [sdb] tag#3 Sense Key : 0x5 [current]
[ 716.230156] sd 1:0:0:0: [sdb] tag#3 ASC=0x21 ASCQ=0x4
[ 716.230157] sd 1:0:0:0: [sdb] tag#3 CDB: opcode=0x2a 2a 00 00 48 78 00 00 08 00 00
[ 716.230158] blk_update_request: I/O error, dev sdb, sector 4749312
[ 716.230267] sd 1:0:0:0: [sdb] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 716.230270] sd 1:0:0:0: [sdb] tag#4 Sense Key : 0x5 [current]
[ 716.230271] sd 1:0:0:0: [sdb] tag#4 ASC=0x21 ASCQ=0x4
[ 716.230273] sd 1:0:0:0: [sdb] tag#4 CDB: opcode=0x2a 2a 00 00 48 80 00 00 08 00 00
[ 716.230274] blk_update_request: I/O error, dev sdb, sector 4751360
[ 716.230391] sd 1:0:0:0: [sdb] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 716.230392] sd 1:0:0:0: [sdb] tag#5 Sense Key : 0x5 [current]
[ 716.230394] sd 1:0:0:0: [sdb] tag#5 ASC=0x21 ASCQ=0x4
[ 716.230395] sd 1:0:0:0: [sdb] tag#5 CDB: opcode=0x2a 2a 00 00 48 88 00 00 08 00 00
[ 716.230396] blk_update_request: I/O error, dev sdb, sector 4753408
[ 716.230527] sd 1:0:0:0: [sdb] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 716.230529] sd 1:0:0:0: [sdb] tag#6 Sense Key : 0x5 [current]
[ 716.230532] sd 1:0:0:0: [sdb] tag#6 ASC=0x21 ASCQ=0x4
[ 716.230534] sd 1:0:0:0: [sdb] tag#6 CDB: opcode=0x2a 2a 00 00 48 90 00 00 08 00 00
[ 716.230536] blk_update_request: I/O error, dev sdb, sector 4755456
[ 716.230746] sd 1:0:0:0: rejecting I/O to offline device
[ 716.230961] sd 1:0:0:0: [sdb] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 716.230964] sd 1:0:0:0: [sdb] tag#7 Sense Key : 0x5 [current]
[ 716.230967] sd 1:0:0:0: [sdb] tag#7 ASC=0x21 ASCQ=0x4
[ 716.230970] sd 1:0:0:0: [sdb] tag#7 CDB: opcode=0x2a 2a 00 00 48 98 00 00 08 00 00
[ 716.230972] blk_update_request: I/O error, dev sdb, sector 4757504
[ 716.231210] sd 1:0:0:0: [sdb] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 716.231213] sd 1:0:0:0: [sdb] tag#8 Sense Key : 0x5 [current]
[ 716.231215] sd 1:0:0:0: [sdb] tag#8 ASC=0x21 ASCQ=0x4
[ 716.231218] sd 1:0:0:0: [sdb] tag#8 CDB: opcode=0x2a 2a 00 00 48 a0 00 00 08 00 00
[ 716.231220] blk_update_request: I/O error, dev sdb, sector 4759552
[ 716.231250] sd 1:0:0:0: rejecting I/O to offline device
[ 716.232424] sd 1:0:0:0: rejecting I/O to offline device
[ 716.232863] sd 1:0:0:0: rejecting I/O to offline device
[ 716.233283] sd 1:0:0:0: rejecting I/O to offline device
[ 716.233710] sd 1:0:0:0: rejecting I/O to offline device
[ 716.234139] sd 1:0:0:0: rejecting I/O to offline device
[ 716.234504] sd 1:0:0:0: rejecting I/O to offline device
[ 716.235069] sd 1:0:0:0: rejecting I/O to offline device
[ 716.235197] sd 1:0:0:0: rejecting I/O to offline device
[ 716.235578] sd 1:0:0:0: rejecting I/O to offline device
[ 716.235832] sd 1:0:0:0: rejecting I/O to offline device
[ 716.236182] ata2: EH
[ 716.236190] ata2.00: detaching (SCSI 1:0:0:0)
[ 716.237338] JBD2: Detected IO errors while flushing file data on sdb1-8
[ 716.237473] Aborting journal on device sdb1-8.
[ 716.237485] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[ 716.237488] EXT4-fs error (device sdb1) in ext4_do_update_inode:5109: Journal has aborted
[ 716.237517] EXT4-fs error (device sdb1): mpage_map_and_submit_extent:2516: comm kworker/u16:3: Failed to mark inode 398418 dirty
[ 716.237524] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 716.238427] EXT4-fs error (device sdb1) in ext4_writepages:2854: IO failure
[ 716.238434] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 716.238762] JBD2: Detected IO errors while flushing file data on sdb1-8
[ 716.242407] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 716.242442] EXT4-fs error (device sdb1): ext4_journal_check_start:60: Detected aborted journal
[ 716.242445] EXT4-fs (sdb1): Remounting filesystem read-only
[ 716.242448] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 716.242512] EXT4-fs (sdb1): ext4_writepages: jbd2_start: 13312 pages, ino 398419; err -30
[ 716.898349] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 716.898379] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00
[ 716.898381] sd 1:0:0:0: [sdb] Stopping disk
[ 716.898385] sd 1:0:0:0: [sdb] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00
[ 867.214938] EXT4-fs error (device sdb1): ext4_find_entry:1433: inode #2: comm dolphin: reading directory lblock 0
[ 867.232370] EXT4-fs warning: 147 callbacks suppressed
[ 867.232377] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:962: inode #2: lblock 0: comm QThread: error -5 reading directory block
[ 869.254530] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:962: inode #2: lblock 0: comm QThread: error -5 reading directory block
[ 869.792039] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:962: inode #2: lblock 0: comm QThread: error -5 reading directory blockSo I guess that means it's dead?
Last edited by sokl (2017-08-05 09:16:56)
Offline
#7 2017-08-05 09:38:54
- R00KIE
- Forum Fellow
- From: Between a computer and a chair
- Registered: 2008-09-14
- Posts: 4,734
Re: [SOLVED] How to make sure SSD isn't busted?
I guess you want to refer to this page https://ata.wiki.kernel.org/index.php/L … r_messages
From there I'd say you should double check the sata cable, see if it's properly seated on both ends and if it is not loose, also make sure power supply to the disk and motherboard are not loose.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
#8 2017-08-06 06:00:54
- sokl
- Member
- Registered: 2015-02-02
- Posts: 11
Re: [SOLVED] How to make sure SSD isn't busted?
R00KIE, thanks.
You were right. SATA cable was to blame.
I restored backup and so far ssd functions well.
Offline