Custom Query (1365 matches)
Results (151 - 153 of 1365)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #466 | invalid | FreeBSD 9.3: extended self-test log lifetime timestamp does not match reality | ||
| Description |
At some point in time (I'm not sure when), it looks like either smartmontools or FreeBSD (I'm not sure which) appears to have begun using the wrong time when doing self-tests. More precisely: when a self-test is run (ex. smartctl -t short /dev/ada0), the completion time as shown in the SMART self-test log is extremely distant/far off compared to attribute 9 Power_On_Hours. This problem is reproducible across multiple drive models (Samsung SSD 840 EVO, WD3003FZEX, WD1003FZEX). I cannot reproduce this problem on Windows XP Pro SP3 (32-bit) using smartmontools 6.3. I'll provide some hard data, including -r ataioctl,2 output, from multiple drives on a system, and show actual proof of this problem. I keep going back and forth trying to figure out if this is a smartmontools bug or a FreeBSD CAM/kernel bug (and if it's the latter, it manifests itself in an extremely bizarre way). Rolling back to smartmontools 6.2 does not fix the problem. |
|||
| #468 | fixed | Add support for TS64GSSD370 | ||
| Description |
It's not in smartctl database and many values are not detected properly. |
|||
| #482 | fixed | Support for Prolific PL2773 | ||
| Description |
The ICY BOX IB-120StU3 uses a Prolific PL2773 chip, which is currently not supported by smartmontools. By reverse engineering the Windows tool iSmart.exe i have made the included patch. It seems to work well and supports all of smartctl -a. Please review and consider including in your next release. |
|||
