D
D
Denis Shpuganich2015-12-12 14:52:08
linux
Denis Shpuganich, 2015-12-12 14:52:08

Why doesn't e2fsck fix errors?

In short, the current problem is that fsck finds and fixes errors, but after a reboot they appear again.
Sectors (or blocks - xs, in general numbers) in the correction logs are always the same.
Symptoms:
When loading the system, it constantly checked (although after running from the system itself it reaches 100% without notifications)
After loading, the system works for a while, but when accessing some programs / files, it switches to readonly mode with all the consequences - programs fall, write errors in logs and stuff...
Background. (The chronological order is reverse - from new to old)
0) checked by Victoria for bads - the tin is completely alive, SMART is in order
1) 3 times I checked with error correction using fsck, both from the system itself and from the live CD
2) I used the EXT4 partition on Windows for about half an hour using Paragon ExtFS (it worked slowly, so I immediately took it down and returned to ext2fsd)
3) Executed initramfs because an error popped up when loading that the old uuid was not found
4) Corrected the fstab file. uuid of the partition has changed
5) Restored the GRUB bootloader using the boot-repair64 program
6) Resized/Moved the partition with Ubuntu (what it all started with :()
7) Before manipulating partitions, I used the ext partition for about a year using ext2fsd on Windows - there were no problems
Question
What to do now?
Here are some pictures of the process:
Photo1
Photo2
Photo3

Answer the question

In order to leave comments, you need to log in

1 answer(s)
V
Vladimir, 2015-12-14
@rostel

the screw is just living out its last days,
most likely the "heads" are skipping past the tracks
, I encountered this several times
after the start, everything seems to be fine, but after a couple of tens of minutes the speed of operations with the disk starts to degrade sharply,
you can check as follows
after uptime for about an hour, run badblocks with a log of bad blocks in the file
after several reloads again badblocks with an exhaust to another file
compare the files with a diff
if the second log is missing a part from the first and new ones are added, then these are definitely signs of agony

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question