Re: [SOLVED, kind of] Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate
On Sun, 29 Sep 2019 01:24:00 +1000
David <bouncingcats@gmail.com> wrote:
> Having read that, I don't see any admission that fsck makes any
> changes if run without any options as it seems you did. So I
> wonder what caused the change in the debugfs message.
I'll offer a guess. Modern disk drives have a full up controller on
board. That controller has enough smarts that when it detects an error
it can correct, it will transparently correct the error and re-write
the sector.
Sometimes it takes more than one such read and re-write to make the
correction permanent.
In GSmartControl, under the Statistics tab, keep an eye on the number
of reallocated sectors. If you see a non-zero value, your drive is in
trouble. At the prices of modern hard drives, it makes sense to replace
early rather than endure the hassle of restoring from backups, no
matter how well done they are.
Also,if you haven't already done so, set up smartd, which is part of
the smartmontools package.
And think about having a spare drive on hand for the day when that
drive goes south.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Reply to: