Custom Query (1494 matches)

Transcend TS120GMTS420 is a M.2 2242 SATA SSD not yet supported. 'Smartctl -x' output made on a SATA controller here ​https://pastebin.com/hxkTJxcp (first task, not even mounted the drive at this point -- bash history: ​http://sprunge.us/WbOK) and hours later behind a JMS578 there ​https://pastebin.com/LHUhv5UG

https://www.smartmontools.org/attachment/ticket/761/Transcend.pdf seems to *not* properly describe the attributes since 148-151 are missing for example.

Observations wrt known attributes: 9 interpreted as Power_On_Hours seems to be wrong (still 0 after 2 hours operation) 194 interpreted as Temperature_Celsius matches thumb test

Observations wrt unknown attributes between the two smartctl executions: 148 increased from 9 to 315 149 increased from 1 to 14 150 remained 0 151 increased from 0 to 9 160 remained 0 161 remained 69 163 remained 5 164 increased from 0 to 1012 165 increased from 0 to 5 166 remained 0 167 increased from 0 to 2 169 remained 100 245 increased from 0 to 8096

Some newer HPSA devices reply to basic SAT commands and provide inquiry that contains "ATA ".

It causes that sat variable in sat_device::autodetect_open() becomes true, and even if cciss is explicitly specified by smartctl -d cciss,0 -H /dev/sda it switches to sat dev/sda [cciss_disk_00] [SAT]: Device open changed type from 'sat,auto' to 'sat'

As a result, it causes failure: SMART STATUS RETURN: incomplete response, ATA output registers missing REPORT-IOCTL: Device=/dev/sda Command=SMART STATUS CHECK returned -1 errno=38 [Function not implemented]

Attached patch disables the auto-switch to "better" driver for cciss.

Note that I do not have a test report from the customer for that patch yet, but setting sat = 0 was already confirmed to prevent this bug.

Note that smart_interface::autodetect_sat_device() contains a similar code, but I am not sure whether it needs a fix as well.