On 2017-04-12 15:28, Anton Aylward wrote:
Yes I know about the 'badblock' program. There are a few variants. But that isn't fast. I've used it on a 8G USB and it took a couple of days. OK that's USB not SATA speeds. But how long would it take to scan a 3T drive using the 'badblock' program?
TOO-OO-OO-OO-OO long!
I just run it on a 1.8 TiB (2 TB) disk, and it took 223m5.110s, without umounting it (ie, nominally in use).
I'm reluctant to try forcing a scan/test on my live drive. Is there a SMARTCTL command that does the equivalent of a 'badblocks' scan?
The long test. But it usually stops at the first error. Previous to running the badblocks programs, I had this report on the log: <3.2> 2017-04-13 15:53:23 Telcontar smartd 1509 - - Device: /dev/sdd [SAT], 8 Currently unreadable (pending) sectors <3.2> 2017-04-13 15:53:23 Telcontar smartd 1509 - - Device: /dev/sdd [SAT], 8 Offline uncorrectable sectors Now I have: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 I was trying to find out the location (the partition) with errors and overwrite them, but they have disappeared from view. Not for the first time, I suspect. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)