Custom Query (1564 matches)
Results (40 - 42 of 1564)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #89 | fixed | Use log directory to check for old error/self-test log support | ||
| Description |
Smartctl and smartd assume that the old SMART error log (log address 0x01) is supported if an error-logging capability bit in IDENTIFY or SMART data is set. Same applies to old SMART self-test log (log address 0x06). These logs were introduced in ATA-5 and are now outdated because 48-bit LBA addresses are not supported. Recent devices may only support the newer 48-bit capable logs (extended comprehensive error-log, extended self-test log) introduced in ATA-6.
Error SMART Error Log Read failed: Input/output error Smartctl: SMART Error Log Read Failed Error SMART Error Self-Test Log Read failed: Input/output error Smartctl: SMART Self Test Log Read Failed Misleading kernel messages may appear during smartd startup: ... kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
... kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
... kernel: ide: failed opcode was: 0xb0
... smartd[...]: Device: /dev/hda, Read SMART Self Test Log Failed
... smartd[...]: Device: /dev/hda, no SMART Self-Test log; remove -l selftest Directive from smartd.conf
(
Smartctl and smartd should read the log directory (log address 0x00) to check whether the old logs are still supported and print an " |
|||
| #94 | fixed | Build fails if source was downloaded via ViewVC | ||
| Description |
ViewVC allows to download the source as a tarball. A build from the tarball fails because the SVN Id strings are not expanded. http://smartmontools.svn.sourceforge.net/viewvc/smartmontools/trunk/smartmontools/ |
|||
| #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. |
|||
