Custom Query (1546 matches)
Results (217 - 219 of 1546)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1343 | invalid | Please add : Smartbuy PS5013-2280T | ||
| Description |
Please add : Smartbuy PS5013-2280T |
|||
| #298 | fixed | [patch] Fix for Seagate drives in drivedb.h | ||
| Description |
I've a Seagate ST2000DM001-1CH164 and it generates the following warning from smartd and smartctl: ep 29 11:46:00 freyr smartd[1093]: Device: /dev/ada5, WARNING: A firmware update for this drive may be available, Sep 29 11:46:00 freyr smartd[1093]: see the following Seagate web pages: Sep 29 11:46:00 freyr smartd[1093]: http://knowledge.seagate.com/articles/en_US/FAQ/207931en Sep 29 11:46:00 freyr smartd[1093]: http://knowledge.seagate.com/articles/en_US/FAQ/223651en Having a look at the second link, the firmware update only applies to a specific part number (9YN166 and friends). My drive is a ST2000DM001-1CH164 (part 1CH164) and is up-to-date according to Seagate. Currently using smartmontools 6.2. I've modified drivedb.h in order to accommodate, see attached patch. |
|||
| #1677 | worksforme | Unable to Ignore 'unreadable (pending) sectors' Error | ||
| Description |
I have many, many machines running SSDs and they periodicaly generate errors like this: Device: /dev/sdc [SAT], 1 Currently unreadable (pending) sectors The SSDs tend to reman these failures because they will go away over time. But how to I stop smartd from e-mailing these alerts. Because of the number of machines we have, we can get up to 100 e-mails a day. It makes it difficult to weed out more serious errors. I have tried the following: DEVICESCAN -I 197 -m gcn-alerts@… -M exec /usr/libexec/smartmontools/smartdnotify -n standby,10,q and DEVICESCAN -m gcn-alerts@… -M exec /usr/libexec/smartmontools/smartdnotify -n standby,10,q -t -I 197 But the e-mails keep coming. Any idea how to get rid of errors for type 197 failures? |
|||
