Custom Query (1434 matches)

We normally monitor SMART attribute 5 Reallocated_Sector_Ct to predict drive failure. Recently we received a shipment of replacement drives (Seagate Constellation ES.3) that don't appear to have SMART attributes in any version of smartctl, up to and including SVN from 12/18/14.

Is it just that support for these drives hasn't yet been added to smartmontools, or is there something new/peculiar about these drives?

Info:

# ./smartctl -i /dev/sdae
smartctl 6.4 2014-12-13 r4030 [x86_64-linux-3.13.0-43-generic] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SEAGATE
Product:              ST4000NM0023
Revision:             0004
Compliance:           SPC-4
User Capacity:        4,000,787,030,016 bytes [4.00 TB]
Logical block size:   512 bytes
LB provisioning type: unreported, LBPME=0, LBPRZ=0
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000c500626b0313
Serial number:        Z1Z5PQ6Z0000C509C0UY
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Thu Dec 18 16:04:45 2014 CST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

# ./smartctl --attributes /dev/sdae
smartctl 6.4 2014-12-13 r4030 [x86_64-linux-3.13.0-43-generic] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
Current Drive Temperature:     33 C
Drive Trip Temperature:        60 C

Manufactured in week 37 of year 2014
Specified cycle count over device lifetime:  10000
Accumulated start-stop cycles:  96
Specified load-unload count over device lifetime:  300000
Accumulated load-unload cycles:  127
Elements in grown defect list: 0

Vendor (Seagate) cache information
  Blocks sent to initiator = 2968316052
  Blocks received from initiator = 3752175265
  Blocks read from cache and sent to initiator = 2227814356
  Number of read and write commands whose size <= segment size = 13010546
  Number of read and write commands whose size > segment size = 759449

Vendor (Seagate/Hitachi) factory information
  number of hours powered up = 887.18
  number of minutes until next internal SMART test = 0

Similar to Ticket #338 my StarTech S358BU33ERM 8-bay enclosure has a JMicron JMB575M + JMS567 chips but works with -d sat

a drive in above enclosure:

# smartctl -a /dev/sdd
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.18.0-gentoo] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sdd: Unknown USB bridge [0x152d:0x3562 (0x310)]
Please specify device type with the -d option.

same drive with -d sat

# smartctl -a -d sat /dev/sdd
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.18.0-gentoo] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD30EFRX-68AX9N0
[...several screens...]

lsusb excerpt:

# lsusb -s 008:004 -v

Bus 008 Device 004: ID 152d:3562 JMicron Technology Corp. / JMicron USA Technology Corp. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         9
  idVendor           0x152d JMicron Technology Corp. / JMicron USA Technology Corp.
  idProduct          0x3562 
  bcdDevice            3.10
  iManufacturer           1 CFI
  iProduct                2 USB to ATA/ATAPI Bridge
  iSerial                 3 891407280112A
  bNumConfigurations      1
[...again several screens trimmed...]

I tried to infer the info you'll need from issue #338 . If you need full outputs let me know.

Mfg product page: ​http://www.startech.com/HDD/Enclosures/8-bay-removable-hard-drive-enclosure~S358BU33ERM

I use HDD Guardian on Windows as a GUI and I've reported ​this issue since back in 2013. I know now that there is nothing to be done on HDD Guardian's side unless the underlying software provides support for JMicron 322/363.

Just wondering if anybody has contacted JMicron customer support department (fae@…) regarding this matter and if so, what was their reply.