Custom Query (1470 matches)
Results (196 - 198 of 1470)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #700 | fixed | Add support for new USB Seagate drive [0x0bc2:0xab34] | ||
| Description |
Works with -d sat. It's called Backup Plus Desktop, I think. I don't know how to get the drive name: dmesg:
lsusb:
|
|||
| #1781 | duplicate | Add swissbitX-78m2 to drivedb | ||
| Description |
Attached you can find the txt output file according to FAQ. Device is produced in 3 sizes as can be seen here: https://www.swissbit.com/files/public/data-symlink/X-78m2/X-78m2_2280_fact_sheet.pdf Vendor provides datasheet upon registration. In that all attributes are documented. Attributes are similar to X-600m without the following which should be added: 16 is Average Erase Count on pSLC blocks 17 is Rated Erase Count on pSLC blocks 231 is Life Remaining |
|||
| #788 | worksforme | Add temperature raw value in syslog, only log if normalized "health" value is below 100% | ||
| Description |
Forwarding from https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1653560 syslog entries like Jan 2 20:22:27 server smartd[876]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 110 to 112 should be less confusing and logging should by default only take place if something is worth to be warned about. That said, a "health" value below 100% (e.g. 98%) should trigger the logging, because then the health status as specified by the vendor is no more perfect. And the output could be more verbose and less confusing. I suggest: Jan 2 20:22:27 server smartd[876]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius: Thermal health changed from 110% (40°C) to 112% (38°C) Given that normalization is specified by vendors, smartmontools could also take into account that e.g. health below 90% is critical (for WD drives that would be 60°C) and also should reported as critical (WARNING, etc.). |
|||
