On Sat, 28 Sep 2019 at 15:57, David <bouncingc...@gmail.com> wrote:
> On Sat, 28 Sep 2019 at 15:05, David <bouncingc...@gmail.com> wrote:
>
> > I had another thought: if you care curious about where the problem
> > is, maybe you could run some read-only command that reads
> > every part of your disk, and see if it gets stuck anywhere.
> > For example:
> > # find / -xdev -type f -exec md5sum '{}' \;
>
> On second thoughts, I think my suggested command likely won't
> "get stuck" when it hits the error, so it won't be very useful.
>
> Maybe better to hide the stdout from md5sum:
> # find junk -xdev -type f -exec md5sum '{}' >/dev/null \;To be more precise, that hides the stdout from both md5sum and find, but I don't think that matters to the goal.
