Photorec says this hard drive will take 339h28m56s to scan๐
=> More informations about this toot | More toots from jackemled@furry.engineer
Just accidentally pirated all of the Microsoft Windows card games from Windows 7 because those were all on there.
=> More informations about this toot | More toots from jackemled@furry.engineer
It says 759h53m28s now๐
=> More informations about this toot | More toots from jackemled@furry.engineer
That's an entire month๐
=> More informations about this toot | More toots from jackemled@furry.engineer
It finished overnight. I'm doing another hard drive now. On both of them it kept freezing for multiple minutes & I have no idea why. btop says it's waiting.
=> More informations about this toot | More toots from jackemled@furry.engineer
@jackemled Guessing, but damaged area that's taxing the drive's retry logic? Check kernel logs for command timeouts coinciding with the freezing.
If so, and if it eventually continues, it's probably doing about as good a job as it can under the circumstances.
=> More informations about this toot | More toots from mkj@social.mkj.earth
@mkj The SMART status is fine on both of them. I don't know how to check kernel logs or what to look for. It does eventually continue.
=> More informations about this toot | More toots from jackemled@furry.engineer
@jackemled A good starting point for kernel logs on a Linux system at least is sudo dmesg | tail -f which you can run in a separate terminal.
Still, as long as it eventually continues, seeing the kernel logs go past probably won't make much difference. It certainly won't make it finish faster. ๐
=> More informations about this toot | More toots from mkj@social.mkj.earth This content has been proxied by September (3851b).Proxy Information
text/gemini