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

On Sun, Sep 29, 2019 at 03:04:48AM +0200, local10 wrote: > Sep 28, 2019, 11:24 by bouncingc...@gmail.com: > > > 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

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, Sep 28, 2019 at 04:01:27PM +1000, David wrote: > > 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. This is

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

Sep 28, 2019, 11:24 by bouncingc...@gmail.com: > 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. > man wasn't available in BusyBox so I had to limit myself to

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 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

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

On Sat, 28 Sep 2019 at 22:31, local10 wrote: > Sep 28, 2019, 02:06 by loca...@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

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

Sep 28, 2019, 08:31 by loca...@tutanota.com: > The end result: > Starting with the "The end result:" the email provider I use screwed up the email formatting, in the original it was a numbered list which should've looked something like this: The end result: 1. fsck reports the repaired fs as

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

Sep 28, 2019, 02:06 by loca...@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

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Sep 28, 2019, 00:50 by bouncingc...@gmail.com: > In your situation, I would: > 1) backup everything important ASAP. > and (assuming your init is systemd): > 2) read here > https://www.linuxuprising.com/2019/05/how-to-force-fsck-filesystem.html > 3) do something like a one-off use of >

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 15:57, David wrote: > On Sat, 28 Sep 2019 at 15:05, David 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

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 15:05, David 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 '{}' \;

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Buy spinrite from www.grc.com, that will work, but after fixing, I would copy to a new drive. You will need a dos disk but this program works well. On Fri, 27 Sep 2019 22:38:59 -0400, local10 wrote: > > Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > > > Hi, I assume you are attempting to

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 12:39, local10 wrote: > Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > > It's telling you that the filesystem itself is broken/unreadable. > > I assume you know what inodes are, if not then you should > > read about that. > > In such a case, I think that it is not

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 12:39, local10 wrote: > Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > > > > In such a case, I think that it is not possible to repair this filesystem. > > What I find weird about this that the filesystem (it's a root filesystem) > appears to be fully functional, it

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > Hi, I assume you are attempting to follow a procedure similar > to this one: > https://www.smartmontools.org/wiki/BadBlockHowto#Repairsinafilesystem > > Yes, a different

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 09:47, local10 wrote: > > Started to get SMART self test errors and wanted to fix them before things > would get any worse: > > SMART Self-test log structure revision number 1 > Num Test_DescriptionStatus Remaining LifeTime(hours) >

ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Hi, Started to get SMART self test errors and wanted to fix them before things would get any worse: SMART Self-test log structure revision number 1 Num  Test_Description    Status  Remaining  LifeTime(hours)  LBA_of_first_error # 1  Short offline   Completed: read failure