e2fsck stalls at 1.73%
by RandomTroll from LinuxQuestions.org on (#51Q9F)
Code: e2fsck -ccfy /dev/sdc1 returned: Quote:
where it stuck for an hour. Code: e2fsck -cfy /dev/sdc1 doesn't stick there, finishes in 20 minutes.
That the time stalls, not just the progress, indicate that e2fsck has stalled, not just found a sector that puzzles it so that it can't proceed? Or is the updating of time dependent on the progress of the program?


e2fsck 1.45.6 (20-Mar-2020) Checking for bad blocks (non-destructive read-write test) Testing with random pattern: 1.73% done, 5:17 elapsed. (0/0/0 errors) |
That the time stalls, not just the progress, indicate that e2fsck has stalled, not just found a sector that puzzles it so that it can't proceed? Or is the updating of time dependent on the progress of the program?