[smartmontools-support] Crucial MX500 issue

[Raoul Bhatia]

Anyone got any idea?

Dirk, I saw you adding the CT500MX500 back in January.  Do you see a 
similar behavior?

Thanks,
Raoul

On 2018-01-29 21:04, Raoul Bhatia wrote:
> Hi!
> 
> I have an issue with two (2!) newly purchased Crucial MX500 1TB
> (device model CT1000MX500SSD1) disks.
> (FYI:
> https://listi.jpberlin.de/pipermail/smartmontools-database/2018-January/000102.html
> was already
> 
> I connected the 2 disks via 2 different USB device bays, one from
> Sharkoon and one from Inateck (USB 3.0).
> 
> 1. Upon initial connect, I used smartctl -a w/o any error
> 2. On the first disk, i mirrored another 1TB disk and then initiated a
> smart test.  On the second disk I issued a "smartctl -t short", only.
> 3. Upon completion of the tests, I saw the below error on both disks.
> 
> * disk2_smartctl.a1.log - smartctl -a after initial power on
> * disk2_smartctl.x1.log - smartctl -x after initial power on
> * disk2_smartctl.a2.log - smartctl -a after short test
> * disk2_smartctl.x2.log - smartctl -x after short test
> 
> I have a few questions:
> A. Is this perhaps a firmware bug similar to
> https://www.smartmontools.org/ticket/214 that needs special treatment
> in smartmontools/drivedb.h?  Perhaps even a kernel bug?
> B. Shall I consider the disks broken?  I used Crucial's Storage
> Executive that gave no error / a healthy status.
> C. Any other thoughts on this?
> 
> Happy to share additional information but as I will need to send the
> first disk back to the seller in the next days.
> 
> Thanks,
> Raoul
> 
> Linux dmesg:
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
> - - - -
> [Mon Jan 29 20:02:54 2018] usb 1-1.3: new high-speed USB device number
> 14 using ehci-pci
> [Mon Jan 29 20:02:54 2018] usb 1-1.3: New USB device found,
> idVendor=174c, idProduct=55aa
> [Mon Jan 29 20:02:54 2018] usb 1-1.3: New USB device strings: Mfr=2,
> Product=3, SerialNumber=1
> [Mon Jan 29 20:02:54 2018] usb 1-1.3: Product: ASMT1153e
> [Mon Jan 29 20:02:54 2018] usb 1-1.3: Manufacturer: asmedia
> [Mon Jan 29 20:02:54 2018] usb 1-1.3: SerialNumber: xxxxxxxxxxxxxxx
> [Mon Jan 29 20:02:54 2018] scsi host8: uas
> [Mon Jan 29 20:02:54 2018] scsi 8:0:0:0: Direct-Access     asmedia
> ASMT1153e        0    PQ: 0 ANSI: 6
> [Mon Jan 29 20:02:54 2018] sd 8:0:0:0: Attached scsi generic sg4 type 0
> [Mon Jan 29 20:02:54 2018] sd 8:0:0:0: [sdd] 1953525168 512-byte
> logical blocks: (1.00 TB/932 GiB)
> [Mon Jan 29 20:02:54 2018] sd 8:0:0:0: [sdd] 4096-byte physical blocks
> [Mon Jan 29 20:02:54 2018] sd 8:0:0:0: [sdd] Write Protect is off
> [Mon Jan 29 20:02:54 2018] sd 8:0:0:0: [sdd] Mode Sense: 43 00 00 00
> [Mon Jan 29 20:02:54 2018] sd 8:0:0:0: [sdd] Write cache: enabled,
> read cache: enabled, doesn't support DPO or FUA
> [Mon Jan 29 20:02:54 2018] sd 8:0:0:0: [sdd] Attached SCSI disk
> 
> 
> SMART Error Log excerpt:
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
> - - - -
> SMART Error Log Version: 1
> Warning: ATA error count 0 inconsistent with error log pointer 2
> 
> ATA Error Count: 0
> 	CR = Command Register [HEX]
> 	FR = Features Register [HEX]
> 	SC = Sector Count Register [HEX]
> 	SN = Sector Number Register [HEX]
> 	CL = Cylinder Low Register [HEX]
> 	CH = Cylinder High Register [HEX]
> 	DH = Device/Head Register [HEX]
> 	DC = Device Command Register [HEX]
> 	ER = Error register [HEX]
> 	ST = Status register [HEX]
> Powered_Up_Time is measured from power on, and printed as
> DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
> SS=sec, and sss=millisec. It "wraps" after 49.710 days.
> 
> Error -1 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
>   When the command that caused the error occurred, the device was in
> an unknown state.
> 
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   00 ec 00 00 00 00 00
> 
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   ec 00 00 00 00 00 00 00      00:00:00.000  IDENTIFY DEVICE
>   ec 00 00 00 00 00 00 00      00:00:00.000  IDENTIFY DEVICE
>   ec 00 00 00 00 00 00 00      00:00:00.000  IDENTIFY DEVICE
>   ec 00 00 00 00 00 00 00      00:00:00.000  IDENTIFY DEVICE
>   c8 00 00 00 00 00 00 00      00:00:00.000  READ DMA
> 
> SMART Self-test log structure revision number 1
> Num  Test_Description    Status                  Remaining
> LifeTime(hours)  LBA_of_first_error
> # 1  Extended offline    Completed without error       00%        10    
>      -
> # 2  Short offline       Completed without error       00%         9    
>      -
> 
> SMART Selective self-test log data structure revision number 1
>  SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
>     1        0        0  Not_testing
>     2        0        0  Not_testing
>     3        0        0  Not_testing
>     4        0        0  Not_testing
>     5        0        0  Not_testing
> Selective self-test flags (0x0):
>   After scanning selected spans, do NOT read-scan remainder of disk.
> If Selective self-test is pending on power-up, resume after 0 minute 
> delay.

-- 
DI (FH) Raoul Bhatia M.Sc.
E-Mail. raoul at bhatia.at
Tel. +43 699 10132530