Custom Query (1564 matches)
Results (409 - 411 of 1564)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1232 | fixed | For database: SanDisk SD8SBAT128G1002 | ||
| Description |
SanDisk SD8SBAT128G1002 in an ASUS R417NA/E402N/E402NA laptop. Not found in drivedb.h, revision 4949 of 2019-08-20. It seems to be the same as ticket #799, except for the form factor (M.2 2280 for SD8SBAT, 2.5”/7mm cased for SD8SNAT). To keep the discussion in one place, I will post additional info in ticket #799. Just creating this separate ticket as instructed by the FAQ. |
|||
| #831 | fixed | FoxLine flssd240x4se is not in database | ||
| Description |
Drive is FoxLine SSD, model flssd240x4se |
|||
| #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. |
|||
