Custom Query (1405 matches)

Please recognize this drive automatically.

root@galaxy:~# lsusb -d 0bc2:3332 Bus 001 Device 003: ID 0bc2:3332 Seagate RSS LLC root@galaxy:~# smartctl -i /dev/sdc smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.0.0-17-generic] (local build) Copyright (C) 2002-11 by Bruce Allen, ​http://smartmontools.sourceforge.net

/dev/sdc: Unknown USB bridge [0x0bc2:0x3332 (0x012)] Smartctl: please specify device type with the -d option.

Use smartctl -h to get a usage summary

root@galaxy:~# smartctl -i -d sat /dev/sdc smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.0.0-17-generic] (local build) Copyright (C) 2002-11 by Bruce Allen, ​http://smartmontools.sourceforge.net

START OF INFORMATION SECTION

Model Family: Seagate Barracuda (SATA 3Gb/s, 4K Sectors) Device Model: ST2000DM001-9YN164 Serial Number: W2400P5S LU WWN Device Id: 5 000c50 03d8f2948 Firmware Version: CC98 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sat Mar 31 20:16:39 2012 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled

root@galaxy:~#

In os_linux.cpp, function sg_io_cmnd_io, the bitwise OR with SG_INFO_CHECK should be a bitwise AND -- SG_INFO_CHECK is a mask used to check if that particular bit is set.

Patch attached to fix the bug.

When using smartctl with my Intel 330 SSD, two things caught my eye:

• The unknown attribute #249: According to [1], this should be the total number of NAND writes.

• The "Power_On_Hours" attribute: smartctl 5.42 returned some permanently changing number, so I tried the current trunk version. Now the values is returned as 4 numbers; the first one seems to be the number of hours plus a big offset, but what do the three in the brackets mean? The last one is always zero and the first one overflows from 255 to 0 after about a minute. If they are just the values of the "remaining three bytes" mentioned in [1], then the firmware probably returns garbage. Any Hints?

[1] Intel Solid-State Drive 330 Series Specification, ​http://www.intel.com/content/www/us/en/solid-state-drives/ssd-330-specification.html