Re: smartctl output for Crucial 512Gb SSD

Hello again

I've put the drive back into the system it was used in, and used the
one other SATA port available.  Running smartctl returns some strange
output, I've also included the kernel message in case it helps.

root@voyage:~/smartmontools-6.3# ./smartctl -T permissive -x /dev/sda
smartctl 6.3 2014-07-26 r3976 [i686-linux-3.4.4-voyage] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               /3:0:0:0
Product:
Compliance:           SPC-5
User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
>> Terminate command early due to bad response to IEC mode page
Read Cache is:        Unavailable
Writeback Cache is:   Unavailable

=== START OF READ SMART DATA SECTION ===
Log Sense failed, IE page [scsi response fails sanity test]
Error Counter logging not supported

scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
Device does not support Self Test logging
Device does not support Background scan results logging


[    3.899820] ata1: SATA max UDMA/133 abar m1024@0xffe40000 port
0xffe40100 irq 45
[    3.899954] ata2: DUMMY
[    3.900067] ata3: SATA max UDMA/133 abar m1024@0xffe40000 port
0xffe40200 irq 45
[    3.900193] ata4: DUMMY
[    4.205145] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    4.205279] ata1: SATA link down (SStatus 0 SControl 300)
[    4.205686] ata3.00: failed to enable AA (error_mask=0x1)
[    4.205772] ata3.00: ATA-9: M4-CT512M4SSD1, 070H, max UDMA/100
[    4.205853] ata3.00: 1000215216 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    4.206476] ata3.00: failed to enable AA (error_mask=0x1)
[    4.206568] ata3.00: configured for UDMA/100 (device error ignored)
[    4.207143] scsi 3:0:0:0: Direct-Access     ATA      M4-CT512M4SSD1
  070H PQ: 0 ANSI: 5
[    4.207977] sd 3:0:0:0: [sda] 1000215216 512-byte logical blocks:
(512 GB/476 GiB)
[    4.208722] sd 3:0:0:0: [sda] Write Protect is off
[    4.208822] sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    4.208998] sd 3:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[    4.569257] scsi 0:0:0:0: Direct-Access     TS       TS2GUFM-H
  1100 PQ: 0 ANSI: 0 CCS
[    4.571000] sd 0:0:0:0: [sdb] 4014080 512-byte logical blocks:
(2.05 GB/1.91 GiB)
[    4.572153] sd 0:0:0:0: [sdb] Write Protect is off
[    4.572260] sd 0:0:0:0: [sdb] Mode Sense: 43 00 00 00
[    4.573219] sd 0:0:0:0: [sdb] No Caching mode page present
[    4.573323] sd 0:0:0:0: [sdb] Assuming drive cache: write through
[    4.577728] sd 0:0:0:0: [sdb] No Caching mode page present
[    4.577837] sd 0:0:0:0: [sdb] Assuming drive cache: write through
[    4.579449]  sdb: sdb1
[    4.583344] sd 0:0:0:0: [sdb] No Caching mode page present
[    4.583454] sd 0:0:0:0: [sdb] Assuming drive cache: write through
[    4.583561] sd 0:0:0:0: [sdb] Attached SCSI disk
[    4.587875] sd 3:0:0:0: Attached scsi generic sg0 type 0
[    4.588303] sd 0:0:0:0: Attached scsi generic sg1 type 0
[   34.720249] ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[   34.720368] ata3.00: failed command: READ FPDMA QUEUED
[   34.720482] ata3.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0
ncq 4096 in
[   34.720489]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[   34.720684] ata3.00: status: { DRDY }
[   34.720769] ata3: hard resetting link
[   40.074131] ata3: link is slow to respond, please be patient (ready=0)
[   44.766167] ata3: COMRESET failed (errno=-16)
[   44.766267] ata3: hard resetting link
[   50.120136] ata3: link is slow to respond, please be patient (ready=0)
[   54.812132] ata3: COMRESET failed (errno=-16)
[   54.812216] ata3: hard resetting link
[   60.166135] ata3: link is slow to respond, please be patient (ready=0)
[   89.848141] ata3: COMRESET failed (errno=-16)
[   89.848226] ata3: limiting SATA link speed to 1.5 Gbps
[   89.848305] ata3: hard resetting link
[   94.896060] ata3: COMRESET failed (errno=-16)
[   94.896149] ata3: reset failed, giving up
[   94.896225] ata3.00: disabled
[   94.896300] ata3.00: device reported invalid CHS sector 0
[   94.896402] ata3: EH complete
[   94.896535] sd 3:0:0:0: [sda] Unhandled error code
[   94.896613] sd 3:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
[   94.896726] sd 3:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00
[   94.897243] end_request: I/O error, dev sda, sector 0
[   94.897323] Buffer I/O error on device sda, logical block 0
[   94.897517] sd 3:0:0:0: [sda] Unhandled error code
[   94.897599] sd 3:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
[   94.897712] sd 3:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00
[   94.898216] end_request: I/O error, dev sda, sector 0
[   94.898293] Buffer I/O error on device sda, logical block 0
[   94.898490] sd 3:0:0:0: [sda] Unhandled error code
[   94.898568] sd 3:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
[   94.898681] sd 3:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00
[   94.899194] end_request: I/O error, dev sda, sector 0
[   94.899271] Buffer I/O error on device sda, logical block 0
[   94.899383] ldm_validate_partition_table(): Disk read failed.
[   94.899542] sd 3:0:0:0: [sda] Unhandled error code
[   94.899620] sd 3:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
[   94.899732] sd 3:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00
[   94.900237] end_request: I/O error, dev sda, sector 0
[   94.900313] Buffer I/O error on device sda, logical block 0
[   94.900506] sd 3:0:0:0: [sda] Unhandled error code
[   94.900584] sd 3:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
[   94.900697] sd 3:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00
[   94.901210] end_request: I/O error, dev sda, sector 0
[   94.901287] Buffer I/O error on device sda, logical block 0
[   94.901399]  sda: unable to read partition table
[   94.902193] sd 3:0:0:0: [sda] READ CAPACITY(16) failed
[   94.902281] sd 3:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
[   94.902398] sd 3:0:0:0: [sda] Sense not available.
[   94.902682] sd 3:0:0:0: [sda] READ CAPACITY failed
[   94.902762] sd 3:0:0:0: [sda]  Result: hostbyte=0x04 driverbyte=0x00
[   94.902877] sd 3:0:0:0: [sda] Sense not available.
[   94.903338] sd 3:0:0:0: [sda] Got wrong page
[   94.903419] sd 3:0:0:0: [sda] Assuming drive cache: write through
[   94.903501] sd 3:0:0:0: [sda] Attached SCSI disk

On 13 August 2014 22:27, Volker Kuhlmann <[email protected]> wrote:
> On Wed 13 Aug 2014 03:36:23 NZST +1200, Mike wrote:
>
>> My m4 512Gb CT512M4SSD1 suddenly failed to read. Below is the smartctl
>> output that returns eventually, taking at least a couple of minutes.  I've
>> tried 2 different USB caddys and also SATA connection to laptop running
>> livecd.  The drive has exclusively been mounted read-only on a Linux system
>> with an ext4 filesystem, and has had unexpected power loss routinely
>> throughout its life.  The values in the attribute table look OK to me I
>> think, but the serious errors at the bottom look bad.  Any ideas greatly
>> appreciated:
>
>> Read SMART Log Directory failed.
>>
>> Error SMART Error Log Read failed: scsi error medium or hardware error
>> (serious)
>> Smartctl: SMART Error Log Read Failed
>> Error SMART Error Self-Test Log Read failed: scsi error medium or hardware
>> error (serious)
>> Smartctl: SMART Self Test Log Read Failed
>> Error SMART Read Selective Self-Test Log failed: scsi error medium or
>> hardware error (serious)
>> Smartctl: SMART Selective Self Test Log Read Failed
>
> This looks like smartctl may not be able to communicate with the drive
> properly, which is what you expect if the drive/computer interface
> circuitry is damaged. However, these errors don't seem to exclude the
> possibility of a serious platter failure - or rather the equivalent in
> solid state.
>
> Moving the disk around between enclosures etc can easily damage the
> drive electronics if sufficient ESD protection procedures have not been
> followed (those procedures must be sufficient regardless of your opinion
> of them ;-) ). If the problem first occurred without having moved any
> hardware around then the problem is with the drive. If you can reliably
> exclude the problem being located at the computer, enclosure or
> connections/cables then it's also the drive.
>
> If the problem is with the drive then the drive is most certainly
> finished. Copy off all the data you can asap and use your backups for
> the rest.
>
> It might be a good idea to treat SSDs the same as spinning versions. The
> differences are in speed and behaviour after being dropped, not
> necessarily in long-term reliability of data.
>
> HTH,
>
> Volker
>
> --
> Volker Kuhlmann
> http://volker.top.geek.nz/      Please do not CC list postings to me.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Smartmontools-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/smartmontools-support

------------------------------------------------------------------------------