You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2019-11-17 09:37:03
- kokoko3k
- Member
- Registered: 2008-11-14
- Posts: 2,394
Is this SSD failing or not?
Hi, today my PC did not boot because of an error on /home that needed manual intervention.
After fsck it, it went online, but i noticed the following messages in the journal:
nov 16 17:34:57 slimer kernel: ata2.00: READ LOG DMA EXT failed, trying PIO
nov 16 17:34:57 slimer kernel: ata2.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0
nov 16 17:34:57 slimer kernel: ata2.00: irq_stat 0x40000008
nov 16 17:34:57 slimer kernel: ata2.00: failed command: READ FPDMA QUEUED
nov 16 17:34:57 slimer kernel: ata2.00: cmd 60/08:b0:38:ac:90/00:00:2e:00:00/40 tag 22 ncq dma 4096 in
res 41/40:00:38:ac:90/00:00:2e:00:00/00 Emask 0x409 (media error) <F>
nov 16 17:34:57 slimer kernel: ata2.00: status: { DRDY ERR }
nov 16 17:34:57 slimer kernel: ata2.00: error: { UNC }
nov 16 17:34:57 slimer kernel: ata2.00: configured for UDMA/133
nov 16 17:34:57 slimer kernel: sd 1:0:0:0: [sdb] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
nov 16 17:34:57 slimer kernel: sd 1:0:0:0: [sdb] tag#22 Sense Key : Medium Error [current]
nov 16 17:34:57 slimer kernel: sd 1:0:0:0: [sdb] tag#22 Add. Sense: Unrecovered read error - auto reallocate failed
nov 16 17:34:57 slimer kernel: sd 1:0:0:0: [sdb] tag#22 CDB: Read(10) 28 00 2e 90 ac 38 00 00 08 00
nov 16 17:34:57 slimer kernel: blk_update_request: I/O error, dev sdb, sector 781233208 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
nov 16 17:34:57 slimer kernel: ata2: EH complete
nov 16 17:34:57 slimer kernel: EXT4-fs error (device sdb4): __ext4_find_entry:1530: inode #20972716: comm unison: reading directory lblock 0
[..]
(The following errors were logged while i was doing the fsck)
[..]
nov 17 09:53:21 slimer kernel: ata2.00: READ LOG DMA EXT failed, trying PIO
nov 17 09:53:21 slimer kernel: ata2.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0
nov 17 09:53:21 slimer kernel: ata2.00: irq_stat 0x40000008
nov 17 09:53:21 slimer kernel: ata2.00: failed command: READ FPDMA QUEUED
nov 17 09:53:21 slimer kernel: ata2.00: cmd 60/08:88:00:43:91/00:00:2e:00:00/40 tag 17 ncq dma 4096 in
res 41/40:00:00:43:91/00:00:2e:00:00/00 Emask 0x409 (media error) <F>
nov 17 09:53:21 slimer kernel: ata2.00: status: { DRDY ERR }
nov 17 09:53:21 slimer kernel: ata2.00: error: { UNC }
nov 17 09:53:21 slimer kernel: ata2.00: configured for UDMA/133
nov 17 09:53:21 slimer kernel: sd 1:0:0:0: [sdb] tag#17 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
nov 17 09:53:21 slimer kernel: sd 1:0:0:0: [sdb] tag#17 Sense Key : Medium Error [current]
nov 17 09:53:21 slimer kernel: sd 1:0:0:0: [sdb] tag#17 Add. Sense: Unrecovered read error - auto reallocate failed
nov 17 09:53:21 slimer kernel: sd 1:0:0:0: [sdb] tag#17 CDB: Read(10) 28 00 2e 91 43 00 00 00 08 00
nov 17 09:53:21 slimer kernel: blk_update_request: I/O error, dev sdb, sector 781271808 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
nov 17 09:53:21 slimer kernel: ata2: EH complete
nov 17 09:53:21 slimer kernel: EXT4-fs warning (device sdb4): htree_dirblock_to_tree:997: inode #20972677: lblock 0: comm ncdu: error -5 reading directory block
nov 17 09:53:31 slimer kernel: ata2.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x0
nov 17 09:53:31 slimer kernel: ata2.00: irq_stat 0x40000008
nov 17 09:53:31 slimer kernel: ata2.00: failed command: READ FPDMA QUEUED
nov 17 09:53:31 slimer kernel: ata2.00: cmd 60/08:40:60:2d:52/00:00:21:00:00/40 tag 8 ncq dma 4096 in
res 41/40:00:60:2d:52/00:00:21:00:00/00 Emask 0x409 (media error) <F>
nov 17 09:53:31 slimer kernel: ata2.00: status: { DRDY ERR }
nov 17 09:53:31 slimer kernel: ata2.00: error: { UNC }
nov 17 09:53:31 slimer kernel: ata2.00: configured for UDMA/133
nov 17 09:53:31 slimer kernel: sd 1:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
nov 17 09:53:31 slimer kernel: sd 1:0:0:0: [sdb] tag#8 Sense Key : Medium Error [current]
nov 17 09:53:31 slimer kernel: sd 1:0:0:0: [sdb] tag#8 Add. Sense: Unrecovered read error - auto reallocate failed
nov 17 09:53:31 slimer kernel: sd 1:0:0:0: [sdb] tag#8 CDB: Read(10) 28 00 21 52 2d 60 00 00 08 00
nov 17 09:53:31 slimer kernel: blk_update_request: I/O error, dev sdb, sector 559033696 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
nov 17 09:53:31 slimer kernel: ata2: EH complete
nov 17 09:53:31 slimer kernel: EXT4-fs warning (device sdb4): htree_dirblock_to_tree:997: inode #14028375: lblock 0: comm ncdu: error -5 reading directory block
nov 17 09:53:37 slimer kernel: ata2.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0
nov 17 09:53:37 slimer kernel: ata2.00: irq_stat 0x40000008
nov 17 09:53:37 slimer kernel: ata2.00: failed command: READ FPDMA QUEUED
nov 17 09:53:37 slimer kernel: ata2.00: cmd 60/08:30:a8:af:50/00:00:25:00:00/40 tag 6 ncq dma 4096 in
res 41/40:00:a8:af:50/00:00:25:00:00/00 Emask 0x409 (media error) <F>
nov 17 09:53:37 slimer kernel: ata2.00: status: { DRDY ERR }
nov 17 09:53:37 slimer kernel: ata2.00: error: { UNC }
nov 17 09:53:37 slimer kernel: ata2.00: configured for UDMA/133
nov 17 09:53:37 slimer kernel: sd 1:0:0:0: [sdb] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
nov 17 09:53:37 slimer kernel: sd 1:0:0:0: [sdb] tag#6 Sense Key : Medium Error [current]
nov 17 09:53:37 slimer kernel: sd 1:0:0:0: [sdb] tag#6 Add. Sense: Unrecovered read error - auto reallocate failed
nov 17 09:53:37 slimer kernel: sd 1:0:0:0: [sdb] tag#6 CDB: Read(10) 28 00 25 50 af a8 00 00 08 00
nov 17 09:53:37 slimer kernel: blk_update_request: I/O error, dev sdb, sector 626044840 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
nov 17 09:53:37 slimer kernel: ata2: EH complete
nov 17 09:53:37 slimer kernel: EXT4-fs warning (device sdb4): dx_probe:761: inode #16123953: lblock 0: comm ncdu: error -5 reading directory block
nov 17 09:53:46 slimer kernel: ata2.00: exception Emask 0x0 SAct 0x4000000 SErr 0x0 action 0x0
nov 17 09:53:46 slimer kernel: ata2.00: irq_stat 0x40000008
nov 17 09:53:46 slimer kernel: ata2.00: failed command: READ FPDMA QUEUED
nov 17 09:53:46 slimer kernel: ata2.00: cmd 60/08:d0:58:ac:50/00:00:1d:00:00/40 tag 26 ncq dma 4096 in
res 41/40:00:58:ac:50/00:00:1d:00:00/00 Emask 0x409 (media error) <F>
nov 17 09:53:46 slimer kernel: ata2.00: status: { DRDY ERR }
nov 17 09:53:46 slimer kernel: ata2.00: error: { UNC }
nov 17 09:53:46 slimer kernel: ata2.00: configured for UDMA/133
nov 17 09:53:46 slimer kernel: sd 1:0:0:0: [sdb] tag#26 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
nov 17 09:53:46 slimer kernel: sd 1:0:0:0: [sdb] tag#26 Sense Key : Medium Error [current]
nov 17 09:53:46 slimer kernel: sd 1:0:0:0: [sdb] tag#26 Add. Sense: Unrecovered read error - auto reallocate failed
nov 17 09:53:46 slimer kernel: sd 1:0:0:0: [sdb] tag#26 CDB: Read(10) 28 00 1d 50 ac 58 00 00 08 00
nov 17 09:53:46 slimer kernel: blk_update_request: I/O error, dev sdb, sector 491826264 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
nov 17 09:53:46 slimer kernel: ata2: EH complete
nov 17 09:53:46 slimer kernel: EXT4-fs warning (device sdb4): htree_dirblock_to_tree:997: inode #11927660: lblock 0: comm ncdu: error -5 reading directory blocksmartctl:
koko@slimer# sudo smartctl -a /dev/sdb
smartctl 7.0 2018-12-30 r4883 [x86_64-linux-5.3.8-arch1-1] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: SanDisk SSD PLUS 480 GB
Serial Number: 174771460706
LU WWN Device Id: 5 001b44 4a9ea3ad5
Firmware Version: UG3000RL
User Capacity: 480.113.590.272 bytes [480 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Nov 17 10:35:54 2019 CET
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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 249) Self-test routine in progress...
90% of test remaining.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x15) SMART execute Offline immediate.
No Auto Offline data collection support.
Abort Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No 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: ( 85) minutes.
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0032 100 100 000 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 1371
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1549
165 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 391
166 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 3
167 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 0
168 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 10
169 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 377
170 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 0
171 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
172 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
173 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 3
174 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 66
184 End-to-End_Error 0x0032 100 100 --- Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 91
188 Command_Timeout 0x0032 100 100 --- Old_age Always - 0
194 Temperature_Celsius 0x0022 063 056 000 Old_age Always - 37 (Min/Max 0/56)
199 UDMA_CRC_Error_Count 0x0032 100 100 --- Old_age Always - 0
230 Unknown_SSD_Attribute 0x0032 100 100 000 Old_age Always - 1146760200459
232 Available_Reservd_Space 0x0033 100 100 005 Pre-fail Always - 100
233 Media_Wearout_Indicator 0x0032 100 100 --- Old_age Always - 1550
234 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 4403
241 Total_LBAs_Written 0x0030 100 100 000 Old_age Offline - 1983
242 Total_LBAs_Read 0x0030 100 100 000 Old_age Offline - 3756
244 Unknown_Attribute 0x0032 000 100 --- Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
Selective Self-tests/Logging not supportedfull journal here
http://sprunge.us/B3HWCa
Now it is performing the long self test.
Is it the drive failing on me?
Thanks...
-EDIT-
(After fsck, the pc went up and i'm using it right now as usual)
Last edited by kokoko3k (2019-11-18 09:09:08)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
#2 2019-11-17 10:03:21
- kokoko3k
- Member
- Registered: 2008-11-14
- Posts: 2,394
Re: Is this SSD failing or not?
...and now that i think of it, i think that the first error occurred when the pc went up from hibernation, and i remember that putting into hibernation just before that event took a longer time that usual.
Last month, smart attribute 187 (Reported Uncorrectable Errors) was at value: 1, now it shows 91 (!).
according to kingston docs: https://www.kingston.com/en/ssd/data-protection
In rare cases, data errors in a block that is being read cannot be corrected; the SSD Controller recognises this occurrence as an Uncorrectable ECC Error (UECC) and reports the error to the host computer. SSDs are designed to be extremely reliable. For Client SSDs, UECCs are typically rated as one in 10
But i just did a full read of the SSD via "dd if=/dev/sdb of=/dev/null", and it completed without errors, nor anything has been logged by the kernel and nothing in journal:
koko@slimer# sudo dd if=/dev/sdb of=/dev/null status=progress bs=4M
479970983936 bytes (480 GB, 447 GiB) copied, 1004 s, 478 MB/s
114468+0 record dentro
114468+0 record fuori
480113590272 bytes (480 GB, 447 GiB) copied, 1004,28 s, 478 MB/s
After the full read, attribute 187 was still at 91.
What could that means?
-edit-
Smart self test,the long one, completed without errors too.
I don't know what to do with this ssd 
Last edited by kokoko3k (2019-11-17 15:33:17)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
#3 2019-11-18 08:32:51
- kokoko3k
- Member
- Registered: 2008-11-14
- Posts: 2,394
Re: Is this SSD failing or not?
Here they come again; the following happened while i was doing an rsync to make a backup
[ 899.752946] ata2.00: READ LOG DMA EXT failed, trying PIO
[ 899.753735] ata2.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x0
[ 899.753738] ata2.00: irq_stat 0x40000008
[ 899.753741] ata2.00: failed command: READ FPDMA QUEUED
[ 899.753748] ata2.00: cmd 60/08:80:40:24:d7/00:00:23:00:00/40 tag 16 ncq dma 4096 in
res 41/40:00:40:24:d7/00:00:23:00:00/00 Emask 0x409 (media error) <F>
[ 899.753750] ata2.00: status: { DRDY ERR }
[ 899.753752] ata2.00: error: { UNC }
[ 899.759925] ata2.00: configured for UDMA/133
[ 899.759954] sd 1:0:0:0: [sdb] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 899.759959] sd 1:0:0:0: [sdb] tag#16 Sense Key : Medium Error [current]
[ 899.759963] sd 1:0:0:0: [sdb] tag#16 Add. Sense: Unrecovered read error - auto reallocate failed
[ 899.759968] sd 1:0:0:0: [sdb] tag#16 CDB: Read(10) 28 00 23 d7 24 40 00 00 08 00
[ 899.759973] blk_update_request: I/O error, dev sdb, sector 601302080 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 899.760020] ata2: EH complete
[ 1016.960175] ata2.00: exception Emask 0x0 SAct 0x80000 SErr 0x0 action 0x0
[ 1016.960179] ata2.00: irq_stat 0x40000008
[ 1016.960183] ata2.00: failed command: READ FPDMA QUEUED
[ 1016.960191] ata2.00: cmd 60/08:98:70:bb:d5/00:00:25:00:00/40 tag 19 ncq dma 4096 in
res 41/40:00:70:bb:d5/00:00:25:00:00/00 Emask 0x409 (media error) <F>
[ 1016.960194] ata2.00: status: { DRDY ERR }
[ 1016.960196] ata2.00: error: { UNC }
[ 1016.966289] ata2.00: configured for UDMA/133
[ 1016.966309] sd 1:0:0:0: [sdb] tag#19 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1016.966315] sd 1:0:0:0: [sdb] tag#19 Sense Key : Medium Error [current]
[ 1016.966319] sd 1:0:0:0: [sdb] tag#19 Add. Sense: Unrecovered read error - auto reallocate failed
[ 1016.966323] sd 1:0:0:0: [sdb] tag#19 CDB: Read(10) 28 00 25 d5 bb 70 00 00 08 00
[ 1016.966328] blk_update_request: I/O error, dev sdb, sector 634764144 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 1016.966374] ata2: EH complete
[ 1021.834494] ata2.00: exception Emask 0x0 SAct 0x4000000 SErr 0x0 action 0x0
[ 1021.834496] ata2.00: irq_stat 0x40000008
[ 1021.834498] ata2.00: failed command: READ FPDMA QUEUED
[ 1021.834511] ata2.00: cmd 60/08:d0:40:42:d7/00:00:25:00:00/40 tag 26 ncq dma 4096 in
res 41/40:00:40:42:d7/00:00:25:00:00/00 Emask 0x409 (media error) <F>
[ 1021.834512] ata2.00: status: { DRDY ERR }
[ 1021.834512] ata2.00: error: { UNC }
[ 1021.840451] ata2.00: configured for UDMA/133
[ 1021.840468] sd 1:0:0:0: [sdb] tag#26 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1021.840470] sd 1:0:0:0: [sdb] tag#26 Sense Key : Medium Error [current]
[ 1021.840472] sd 1:0:0:0: [sdb] tag#26 Add. Sense: Unrecovered read error - auto reallocate failed
[ 1021.840484] sd 1:0:0:0: [sdb] tag#26 CDB: Read(10) 28 00 25 d7 42 40 00 00 08 00
[ 1021.840486] blk_update_request: I/O error, dev sdb, sector 634864192 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 1021.840497] ata2: EH completesmartctl now reports :
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 94(was 91 yesterday)
But i did a
root@slimer# badblocks -v /dev/sdb4 >/tmp/badsectors.txtAnd guess what? /tmp/badsectors.txt is just empty.
Pass completed, 0 bad blocks found. (0/0/0) errI'm beginning to think that this is could be a software error or an error triggered by software (kernel); could it be?
-EDIT-
Don't know how much sense it makes on an SSD, but since smart table indicates that there has been no relocations, i did this:
root@slimer# journalctl|grep "dev sdb, sector"
nov 16 17:34:57 slimer kernel: blk_update_request: I/O error, dev sdb, sector 781233208 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
nov 17 09:53:21 slimer kernel: blk_update_request: I/O error, dev sdb, sector 781271808 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
nov 17 09:53:31 slimer kernel: blk_update_request: I/O error, dev sdb, sector 559033696 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
nov 17 09:53:37 slimer kernel: blk_update_request: I/O error, dev sdb, sector 626044840 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
nov 17 09:53:46 slimer kernel: blk_update_request: I/O error, dev sdb, sector 491826264 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
nov 18 08:52:23 slimer kernel: blk_update_request: I/O error, dev sdb, sector 601302080 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
nov 18 08:54:20 slimer kernel: blk_update_request: I/O error, dev sdb, sector 634764144 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
nov 18 08:54:25 slimer kernel: blk_update_request: I/O error, dev sdb, sector 634864192 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
root@slimer# journalctl|grep "dev sdb, sector"|cut -d " " -f 12
781233208
781271808
559033696
626044840
491826264
601302080
634764144
634864192
for s in $(journalctl|grep "dev sdb, sector"|cut -d " " -f 12) ; do echo reading sector $s with hdparm ; hdparm --read-sector $s ; done
root@slimer# for s in $(journalctl|grep "dev sdb, sector"|cut -d " " -f 12) ; do echo reading sector $s with hdparm ; hdparm --read-sector $s /dev/sdb ; done |grep succeeded
reading sector 781233208: succeeded
reading sector 781271808: succeeded
reading sector 559033696: succeeded
reading sector 626044840: succeeded
reading sector 491826264: succeeded
reading sector 601302080: succeeded
reading sector 634764144: succeeded
reading sector 634864192: succeededNothing, i'm unable to reproduce the error.
(later)
now doing wild reads on files to test the filesystem subsystem...
root@slimer# sync ; echo 3 > /proc/sys/vm/drop_caches ; find /home -type f -exec timeout 1 grep a {} \;and finally, two sectors:
nov 18 10:28:41 slimer kernel: blk_update_request: I/O error, dev sdb, sector 634778608 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
nov 18 10:28:45 slimer kernel: blk_update_request: I/O error, dev sdb, sector 634764152 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0...but as you can see the number differs;
rebooted and tried the very same command:
nov 18 11:05:41 slimer kernel: blk_update_request: I/O error, dev sdb, sector 634708472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
nov 18 11:05:47 slimer kernel: blk_update_request: I/O error, dev sdb, sector 634954528 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
nov 18 11:06:05 slimer kernel: blk_update_request: I/O error, dev sdb, sector 634679384 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
nov 18 11:06:19 slimer kernel: blk_update_request: I/O error, dev sdb, sector 634764152 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0Again, different numbers.
Tried again, and another 4 different sectors popped up.
It seems there is a pattern:
1) It seems there are exactly 4 errors per scan
2) The 4 errors comes just after (just one message) this: "READ LOG DMA EXT failed, trying PIO"
Last edited by kokoko3k (2019-11-18 12:56:34)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
#4 2019-11-19 19:39:05
- kokoko3k
- Member
- Registered: 2008-11-14
- Posts: 2,394
Re: Is this SSD failing or not?
changed ssd with another one, same model 1:1 copy via dd, problem gone.
Then filled the first one with a miriad of 100k files feeded from /dev/urandom via dd.
Guess what? No more errors reading them.
Go figure...
Last edited by kokoko3k (2019-11-19 20:07:41)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
#5 2019-11-19 19:54:13
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 21,740
Re: Is this SSD failing or not?
I'd not trust it anymore either way, uncorrectable errors are only likely to increase rather than decrease.
Offline
#6 2019-11-19 20:09:33
- kokoko3k
- Member
- Registered: 2008-11-14
- Posts: 2,394
Re: Is this SSD failing or not?
Yeah, me too.
It is not the ssd per se (well, a little bit... it was just little more than a year old and just 1.5TB of data written), but the desire to understand what t# f# is going on.
Probably i'll never know.
Last edited by kokoko3k (2019-11-19 20:14:43)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
Pages: 1