[SOLVED, kind of] Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

[local10 <local10@tutanota.com>]

Sep 28, 2019, 02:06 by local10@tutanota.com:

> Good advice, thanks. I have a backup drive which is almost a mirror copy of the failing one, so that's why I am not very worried about it. I'm going to try to fix it in a couple of days, so let's see how it goes.
>

So I forced fsck to run at reboot, it refused to run in the auto mode, dropped me into BusyBox and from there I could run fsck manually, pressing <yes> a couple of times telling fsck to ignore errors (that was the only option available to me in fsck other than quitting it). After that fsck reported the filesystem clean.

The end result:
fsck reports the repaired fs as clean
The system boots from the repaired root fs and functions normally, no disk related errors in the syslog
SMART self tests (both short and long) complete successfully, no errors
badblocks reports no bad blocks:

# badblocks -sv -o /root/bad.blocks /dev/sda
Checking blocks 0 to 976762583
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)

debugfs still looks a bit weird:

# debugfs
debugfs 1.44.5 (15-Dec-2018)
debugfs:  open /dev/sda2
debugfs:  testb 950
Block 950 marked in use
debugfs:  icheck 950
Block   Inode number
950     7
debugfs:  ncheck 7
Inode   Pathname
debugfs:  testb 1430
Block 1430 marked in use
debugfs:  icheck 1430
Block   Inode number
1430    <block not found>
debugfs:  quit

So the issue appears to be resolved, the system works, my remaining concern at this point is the debugfs output above.

Thanks to everyone who responded.