Custom Query (1359 matches)
Results (40 - 42 of 1359)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #40 | fixed | smartctl --test when a test is already running causes it to abort | ||
| Description |
Hi,
smartctl can be used to execute a test on a drive already running another test. In my case, I ran a short test on a drive already running a long test. I was not aware that SMART could only handle 1 test at a time. Apparently, SMART can't resume aborted tests. smartctl's behavior in this case seems to be to execute the newly requested test without caring about the already one. The worst problem with this is loss of time, as in my scenario. I see two options: running the newly requested test after the currently running one is finished, or prompt for what to do. |
|||
| #41 | invalid | smartd: internal error in MailWarning(): cfg.mailwarn->emailfreq=0 | ||
| Description |
Hi,
Smartd logs internal error along with the notification of a failing hard disk.
-8<- Jan 12 13:42:11 hanuri smartd[9147]: Device: /dev/sdc, 5 Currently unreadable (pending) sectors Jan 12 13:42:11 hanuri smartd[9147]: internal error in MailWarning(): cfg.mailwarn->emailfreq=0 -8<- /etc/smartd.conf has: -8<- /dev/sda -d ata -I 194 -I 190 /dev/sdb -d ata -I 194 -I 190 /dev/sdc -d ata -I 194 -I 190 /dev/sdd -d ata -I 194 -I 190 /dev/sde -d ata -I 194 -I 190 /dev/sdf -d ata -I 194 -I 190 -8<- |
|||
| #42 | wontfix | Subzero temperature | ||
| Description |
Smartctl seems to treat temperature as an unsigned integer. That leads to weird values (~65K) when the temperature is below 0. I don't know if it's SMART's official interpretation of temperature, but I think it would be wise to assume no drives run at 65000 and some do run at <0. Usually it's not inended, but accidents happen... |
|||
