You are not logged in.

#1 2012-07-14 00:37:45

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,734
Website

Problems with SSD

Ever since flashing the firmware on my Vertex 4 (128 GB SSD) I have been experiencing seemingly random problems where the system becomes unresponsive and my kernel.log as well os stdout is populated with errors like the below.  Can't downgrade firmware revisions so I'd thought I'd ask in here if folks have experience something similar and how they dealt with it.

# cat kernel.log
Jul 13 20:32:22 localhost kernel: [ 7438.265533] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:22 localhost kernel: [ 7438.265534] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:22 localhost kernel: [ 7438.265536] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 01 51 3b f8 00 00 08 00
Jul 13 20:32:22 localhost kernel: [ 7438.265541] end_request: I/O error, dev sda, sector 22100984
Jul 13 20:32:22 localhost kernel: [ 7438.268365] sd 6:0:0:0: [d]Uhnlderrcd
Jul 13 20:32:22 localhost kernel: [ 7438.269416] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:22 localhost kernel: [ 7438.269418] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 4e 80 c0 00 00 08 00
Jul 13 20:32:22 localhost kernel: [ 7438.269425] end_request: I/O error, dev sda, sector 5144768
Jul 13 20:32:26 localhost kernel: [ 7442.342575] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:26 localhost kernel: [ 7442.342578] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:26 localhost kernel: [ 7442.342582] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 01 51 3b f8 00 00 08 00
Jul 13 20:32:26 localhost kernel: [ 7442.342589] end_request: I/O error, dev sda, sector 22100984
Jul 13 20:32:26 localhost kernel: [ 7442.345006] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:26 localhost kernel: [ 7442.345010] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:26 localhost kernel: [ 7442.345013] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 4e 79 38 00 00 08 00
Jul 13 20:32:26 localhost kernel: [ 7442.345020] end_request: I/O error, dev sda, sector 5142840
Jul 13 20:32:26 localhost kernel: [ 7442.345112] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:26 localhost kernel: [ 7442.345114] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:26 localhost kernel: [ 7442.345117] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 4e 89 e0 00 00 08 00
Jul 13 20:32:26 localhost kernel: [ 7442.345123] end_request: I/O error, dev sda, sector 5147104
Jul 13 20:32:26 localhost kernel: [ 7442.345504] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:26 localhost kernel: [ 7442.345507] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:26 localhost kernel: [ 7442.345510] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 4e 86 00 00 00 08 00
Jul 13 20:32:26 localhost kernel: [ 7442.345516] end_request: I/O error, dev sda, sector 5146112
Jul 13 20:32:26 localhost kernel: [ 7442.345601] sd 6:0:0:0: [sda] Unhanlderrcd
Jul 13 20:32:26 localhost kernel: [ 7442.346064] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:26 localhost kernel: [ 7442.346067] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 4e 80 c0 00 00 08 00
Jul 13 20:32:26 localhost kernel: [ 7442.346074] end_request: I/O error, dev sda, sector 5144768
Jul 13 20:32:26 localhost kernel: [ 7442.346147] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:26 localhost kernel: [ 7442.346150] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:26 localhost kernel: [ 7442.346154] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 4e 92 50 00 00 08 00
Jul 13 20:32:26 localhost kernel: [ 7442.346167] end_request: I/O error, dev sda, sector 5149264
Jul 13 20:32:27 localhost kernel: [ 7443.161852] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:27 localhost kernel: [ 7443.161855] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:27 localhost kernel: [ 7443.161858] d6000 sa D:cb0=x8 80 05 26 00 00
Jul 13 20:32:32 localhost kernel: [ 7448.665625] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:32 localhost kernel: [ 7448.665628] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:32 localhost kernel: [ 7448.665632] s ::::[d]CB d[]02:2 00 b9 00 02 0<> 48654]edrqet / ro,dvsa etr2720
Jul 13 20:32:34 localhost kernel: [ 7450.345455] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:34 localhost kernel: [ 7450.345458] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 01 4b 9b d0 00 00 08 00
Jul 13 20:32:34 localhost kernel: [ 7450.345465] end_request: I/O error, dev sda, sector 21732304
Jul 13 20:32:35 localhost kernel: [ 7451.374709] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:35 localhost kernel: [ 7451.374712] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:35 localhost kernel: [ 7451.374715] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 01 51 3b f8 00 00 08 00
Jul 13 20:32:44 localhost kernel: [ 745.771 n_eus:IOerr e d,sco 2094_eus:IOerr e d,sco 692
Jul 13 20:32:45 localhost kernel: [ 7461.486444] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:45 localhost kernel: [ 7461.486448] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:45 localhost kernel: [ 7461.486451] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 53 73 40 00 00 08 00
Jul 13 20:32:45 localhost kernel: [ 7461.486458] end_request: I/O error, dev sda, sector 5468992
Jul 13 20:32:45 localhost kernel: [ 7461.486476] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:45 localhost kernel: [ 7461.486478] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:45 localhost kernel: [ 7461.486481] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 53 73 40 00 00 08 00
Jul 13 20:32:45 localhost kernel: [ 7461.486488] end_request: I/O error, dev sda, sector 5468992
Jul 13 20:32:45 localhost kernel: [ 7461.486655] sd 6:0:0:0: [sda] Unhandled error code
Jul 13 20:32:45 localhost kernel: [ 7461.486658] sd 6:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
Jul 13 20:32:45 localhost kernel: [ 7461.486660] sd 6:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 55 52 d8 00 00 08 00
Jul 13 20:32:45 localhost kernel: [ 7461.486668] end_request: I/O error, dev sda, sector 5591768

Offline

#2 2012-07-14 14:06:15

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: Problems with SSD

Nothing in the readme that came with the update stating that you should do some kind of reset? Looked in the OCZ forums for similar reports?


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#3 2012-07-14 14:08:37

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,734
Website

Re: Problems with SSD

@R - Nothing.

Offline

#4 2012-07-14 16:56:44

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: Problems with SSD

Maybe the interface mode (ahci/ide) and/or speed (1.5G/3G/...) has some influence. Maybe a BIOS incompatibility problem with the new firmware. I'm not saying that is the case but maybe a borked fw update, maybe the drive is malfunctioning [1] .... just shooting randomly in every direction, might eventually hit something tongue

[1] http://www.linuxquestions.org/questions … 2-a-692954


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#5 2012-07-14 18:28:50

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,734
Website

Re: Problems with SSD

Another freeze just occurred, but this was a temp freeze/unfreeze.  More info from dmesg:

[15660.318461] ata7.00: exception Emask 0x0 SAct 0x1f SErr 0x0 action 0x6 frozen
[15660.318467] ata7.00: failed command: READ FPDMA QUEUED
[15660.318471] ata7.00: cmd 60/00:00:e0:70:fe/01:00:01:00:00/40 tag 0 ncq 131072 in
[15660.318473]          res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[15660.318475] ata7.00: status: { DRDY }
[15660.318477] ata7.00: failed command: READ FPDMA QUEUED
[15660.318481] ata7.00: cmd 60/00:08:e0:71:fe/01:00:01:00:00/40 tag 1 ncq 131072 in
[15660.318482]          res 40/00:01:02:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[15660.318485] ata7.00: status: { DRDY }
[15660.318487] ata7.00: failed command: WRITE FPDMA QUEUED
[15660.318491] ata7.00: cmd 61/08:10:20:58:2a/00:00:0c:00:00/40 tag 2 ncq 4096 out
[15660.318492]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[15660.318494] ata7.00: status: { DRDY }
[15660.318496] ata7.00: failed command: WRITE FPDMA QUEUED
[15660.318500] ata7.00: cmd 61/08:18:58:58:2a/00:00:0c:00:00/40 tag 3 ncq 4096 out
[15660.318501]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[15660.318504] ata7.00: status: { DRDY }
[15660.318505] ata7.00: failed command: WRITE FPDMA QUEUED
[15660.318510] ata7.00: cmd 61/50:20:00:25:6b/00:00:08:00:00/40 tag 4 ncq 40960 out
[15660.318511]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[15660.318513] ata7.00: status: { DRDY }
[15660.318517] ata7: hard resetting link
[15660.645120] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[15660.646363] ata7.00: configured for UDMA/133
[15660.646369] ata7.00: device reported invalid CHS sector 0
[15660.646373] ata7.00: device reported invalid CHS sector 0
[15660.646375] ata7.00: device reported invalid CHS sector 0
[15660.646378] ata7.00: device reported invalid CHS sector 0
[15660.646384] ata7: EH complete

I wonder if this is a problem with my $24 controller card (Rocket 620)?

Last edited by graysky (2012-07-14 18:31:40)

Offline

#6 2012-07-14 18:52:46

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,491

Re: Problems with SSD

That looks bad yes. Maybe try passing the kernel "libata.force=noncq"? 
(Not from my own experience luckily, see this old thread here.)

Offline

#7 2012-07-14 18:59:48

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,734
Website

Re: Problems with SSD

OK... so I can get these errors in dmesg by doing a simple dd benchmark (which is outlined on the SSD_Benchmarking wiki page.

$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc
# echo 3 > /proc/sys/vm/drop_caches
# dd if=tempfile of=/dev/null bs=1M count=1024

Experiment 1
1) Replaced cable
2) Repeated benchmark
3) Checked dmesg for errors

Result: Errors still there
Conclusion: Not a bad cable

Experiment 2
4) Moved position from Device 0 to Device 1 on the controller card
Repeated 2 and 3

Result: Errors still there
Conclusion: Not a bad port on the controller

Experiment 3
5) Plugged into MB's ICHR10 controller (only SATA2)
Repeated 2 and 3 several times

Result: NO errors
Conclusion: Something is wrong with the controller

Last edited by graysky (2012-07-14 19:01:33)

Offline

Board footer

Powered by FluxBB