Custom Query (1566 matches)
Results (475 - 477 of 1566)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1697 | invalid | Question on decoding temperature values from csv file | ||
| Description |
I started looking at the csv files smartd generates and would like some help understanding it. On some websites ATA drives were said to show a 150 offset to the raw value in Celsius. A number 187 would translate to 187-150 as a value for degrees celsius. On some SCSI Enterprise drives the temperature is listed exactly in degrees celsius in the CSV file which is very convenient. I found a few CSV files with strange output and would like to know how to find the correct decoding. Below is some data of ATA drives CSV output searching for then key 194 aka. Temperature_Celsius, showing the column number in which key=194 is found and the min and max value found in the next column that I think is the temperature. For some drives the range can not be linear: minimal value 4, max value 253 would not translate by any linear offset assuming this is a digit and not hex. Also, min=55 max=79 is likely an offset of possibly 100? Pulling with smartctl shows 194 Temperature_Celsius 0x0022 073 046 --- Old_age Always - 27 (Min/Max 20/46) key=194 in column=35 min=94 max=145 in /tmp/Temperature_Celsius.WD-WMC1T0306391.raw.csv (Model: WDC WD30EZRX-00DC0B0) key=194 in column=41 min=4 max=253 in /tmp/Temperature_Celsius.7SGEWP6C.raw.csv (Model: WDC WD80EFAX-68LHPN0) key=194 in column=53 min=5 max=43 in /tmp/Temperature_Celsius.Z840RT48.raw.csv (Model: ST8000AS0002-1NA17Z) key=194 in column=41 min=4 max=253 in /tmp/Temperature_Celsius.1SG60K6Z.raw.csv (Model: WDC WD80EMAZ-00WJTA0) key=194 in column=53 min=5 max=42 in /tmp/Temperature_Celsius.ZCT0EYFR.raw.csv (Model: ST8000DM004-2CX188) key=194 in column=41 min=104 max=250 in /tmp/Temperature_Celsius.JEGRVHKN.raw.csv (Model: WDC WD100EMAZ-00WJTA0) key=194 in column=53 min=6 max=42 in /tmp/Temperature_Celsius.ZCT0EQG7.raw.csv (Model: ST8000DM004-2CX188) key=194 in column=41 min=181 max=253 in /tmp/Temperature_Celsius.2YHZD7WD.raw.csv (Model: HGST HUH721010ALE601) key=194 in column=50 min=55 max=79 in /tmp/Temperature_Celsius.183584805068.raw.csv (Model: WDC WDS500G2B0A-00SM50) Is there a magic table for each manufacturer to decode the smart output or syntax to log the raw value only? Btw: Google has not been my friend yet in finding an answer. |
|||
| #268 | fixed | smartd should avoid port multiplier devices on FreeBSD | ||
| Description |
When scanning for devices, smartd uses the FreeBSD cam subsystem to iterate through all of the devices on the system. When it encounters a SATA port multipler (e.g., /dev/pmp0) it sends commands to that device that eventually timeout. This delays boot by several minutes on a large system. Running "smartd -q onechceck" produces errors like this for each port multiplier encountered, Device: /dev/pmp8, opened (pass53:mvsch10:0:15:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 00 (pass53:mvsch10:0:15:0): CAM status: ATA Status Error (pass53:mvsch10:0:15:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (pass53:mvsch10:0:15:0): RES: 51 04 00 00 00 00 00 00 00 00 00 (pass53:mvsch10:0:15:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 01 00 (pass53:mvsch10:0:15:0): CAM status: Command timeout Device: /dev/pmp8, not ATA, no IDENTIFY DEVICE Structure Unable to register ATA device /dev/pmp8 These devices should be avoided on FreeBSD. The attached patch avoids them when running "smartd -d onecheck" but it is not clear if that is sufficient or even the right place to make such a change. |
|||
| #95 | fixed | JMicron 4 device support (0x152d:0x0551) | ||
| Description |
I've recently acquired a 4 bay USB3+eSATA enclosure, specifically this one: http://mediasonicinc.com/store/product_info.php?cPath=26_51&products_id=234 (Mediasonic Pro Box 4 Bay Enclosure USB 3.0 & eSATA [HF2-SU3S2] in case the link becomes dead). NB: I'm not actually using USB3 (yet), it's connected to a USB2 host. The enclosure uses a JMicron chip that smartmontools does not support. I'm hoping that JMicron implemented this one similarly to the two device chips, and that smartmontools can support this without huge effort. What smartctl says when I try to query it: "... Unknown USB bridge [0x152d:0x0551 (0x100)]" ... <please use -d> On a lark, I tried the usbjmicron,0, and that appeared to successfully give the info for the first disk. So I tried usbjmicron,1 for the second device, and that I think made the enclosure "reboot": I got a usb disconnect, and then it came back to life. |
|||
