Wednesday, July 10, 2019, 7:47:55 PM, you wrote: > On Wed, Jul 10, 2019 at 10:46 AM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: >> >> # smartctl -l scterc,900,100 >> # echo 180 > /sys/block/sda/device/timeout > smartctl command above does need a drive specified... Indeed! :) With the commands above, you are increasing the timeout and then fsck will try to re-read the sectors, right? As for the SMART status, the number of pending sectors was 0 before. It started to grow after the PSU incident yesterday. Now, since I'm doing a ddrescue, all the sectors will be read (or attempted to be read). So the pending sectors counter may increase further. As I understand, when a drive cannot READ a sector, the sector is reported as pending. And it will stay like that until either the sector is finally read or until it is overwritten. When either of these happens, the Pending Sector Counter should decrease. In theory, it can go back to 0 (although I didn't follow this closely enough, so I never saw a drive like that). If a drive can't WRITE to a sector, it tries to reallocate it. If it succeeds, Reallocated Sectors Counter is increased. If it fails to reallocate - I guess there should be another kind of error or a counter, but I'm not sure which one. When reallocated sectors appear - it's clearly a bad sign. If the number of reallocated sectors grow - the drive should not be used. But it's not that obvious for the pending sectors... Anyway, as you noted, the drive isn't new already: > 9 Power_On_Hours -O--CK 022 022 000 - 56941 > > 56941÷8760 = 6.5 years ? > > Doubtful it's under warranty. Mmm... yeah... I guess it was one of the early WD30EFRX drives... This model was launched about 7 years ago, if I'm not mistaken... :) --- Best regards, Andrey
