Ok, I tried running a SMART test via gnome-disk-utility with the
mainline kernel, and still get these errors. It took about 4 hard resets
to get my SSD to show in BIOS this morning.
Excerpt:
Mar 27 21:15:36 jupiter kernel: [ 68.832057] ata4.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 27 21:15:36 jupiter kernel: [ 68.832067] ata4.00: failed command: SMART
Mar 27 21:15:36 jupiter kernel: [ 68.832079] ata4.00: cmd
b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
Mar 27 21:15:36 jupiter kernel: [ 68.832082] res
40/00:00:01:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 27 21:15:36 jupiter kernel: [ 68.832089] ata4.00: status: { DRDY }
Mar 27 21:15:36 jupiter kernel: [ 68.832096] ata4: hard resetting link
Mar 27 21:15:46 jupiter kernel: [ 78.844142] ata4: softreset failed (device
not ready)
Mar 27 21:15:46 jupiter kernel: [ 78.844150] ata4: hard resetting link
Mar 27 21:16:31 jupiter kernel: [ 123.900139] ata4: softreset failed (device
not ready)
Mar 27 21:16:31 jupiter kernel: [ 123.900148] ata4: limiting SATA link speed
to 3.0 Gbps
Mar 27 21:16:36 jupiter kernel: [ 129.088127] ata4: softreset failed (device
not ready)
Mar 27 21:16:36 jupiter kernel: [ 129.088136] ata4: reset failed, giving up
Mar 27 21:16:36 jupiter kernel: [ 129.088142] ata4.00: disabled
Mar 27 21:16:36 jupiter kernel: [ 129.088188] ata4: EH complete
Mar 27 21:16:36 jupiter kernel: [ 129.088233] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 27 21:16:36 jupiter kernel: [ 129.088238] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 27 21:16:36 jupiter kernel: [ 129.088246] sd 3:0:0:0: [sdb] CDB: Read(10):
28 00 06 44 1c 40 00 00 20 00
Mar 27 21:16:36 jupiter kernel: [ 129.088262] end_request: I/O error, dev sdb,
sector 105126976
Mar 27 21:16:36 jupiter kernel: [ 129.088282] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 27 21:16:36 jupiter kernel: [ 129.088287] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 27 21:16:36 jupiter kernel: [ 129.088293] sd 3:0:0:0: [sdb] CDB: Read(10):
28 00 00 95 27 00 00 00 20 00
Mar 27 21:16:36 jupiter kernel: [ 129.088308] end_request: I/O error, dev sdb,
sector 9774848
Mar 27 21:16:36 jupiter kernel: [ 129.088324] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 27 21:16:36 jupiter kernel: [ 129.088331] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 27 21:16:36 jupiter kernel: [ 129.088336] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 27 21:16:36 jupiter kernel: [ 129.088344] sd 3:0:0:0: [sdb] CDB: Read(10):
28 00 04 84 c5 b0 00 00 20
Mar 27 21:16:36 jupiter kernel: [ 129.088370] sd 3:0:0:0: [sdb] Unhandled
error code
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/958188/+attachment/2955631/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/958188
Title:
SMART causes SSD to die with unhandled error code
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/958188/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
