11 Aug
2019
11 Aug
'19
6:10 a.m.
On 2019-08-08 1:08 a.m., D. Hugh Redelmeier via talk wrote:
smartctl --test=long is the right way. Not surprisingly this can take quite some time on a large HDD. Probably not on an ordinary SSD.
smartctl returns instantly with no output when tried on any reasonable permutation of the device name. I know the main files that was affected, and it's a VirtualBox dynamic disk image. Unfortunately, VBox (or possible Win 10 running as the VM) doesn't seem to be very clever with underlying media errors on this type of disk and it locks up. Stewart