Buffer I/O errors when trying to recover journal for fsck
by Tohveli from LinuxQuestions.org on (#4W46W)
Hello, after few months away from linux I'm trying to get back on my debian machine (4.19.28-2). First thing I booted into was "fsck error on boot: /dev/sdca1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY", so I ran fsck /dev/sdc1 and was returned with myriads of walls of errors which ended with:
Code:Free inodes count wrong (6939155, counted=6830081)
debian: ***** FILE SYSTEM WAS MODIFIED *****
debian: 501759/files (0.9% non-contiguous), 9487363/29296875 blocksI rebooted with "reboot -f" and after systemd had loaded i got a wall of buffer I/O errors that ended with an "Ext4 Error (device sdc1) disk remounted read-only". After having logged into root i ran fsck again and got: "-bash: fcsk: command not found". I went to /sbin to run fsck and was again greeted with the same wall of buffer I/O error on dev sdc1, logical block xxxxxxxx, lost async page write errors. Eventually i got:
Code:fsck.ext4: Input/Output error while recovering journal of debian
debian contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structures
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: - (164879--165105) -(203624--204198)
fix<y>?I quit fsck here before fixing anything with ctrl + z and ran fsck again - this time the buffer I/O errors that occurred last time didn't come up and it went straight to the same the "fsck.ext4: input/out error while recovering journal of debian". It only found two errors which i both fixed:
Code:Block bitmap differences: - (164879--165105) -(203624--204198)
Free blocks count wrong (19809512, counted=19807396)But then i got a bunch of buffer I/O errors again, which eventually ended with:
Code:Error writing file system info: Input/Output error
debian: ***** FILE SYSTEM WAS MODIFIED *****Now every time when i try to run fsck I keep getting the same persistent "Free blocks count wrong (19809512, counted=19807396)" error. and after that ten rows of "buffer I/O error on dev sdc1, logical block 1, lost async page write" for all logical blocks 1 through 10 and there's always a "print_req_error: I/O error, dev sdc, sector 2056" before the buffer i/o errors.
Now I have no idea what to do anymore, how do i troubleshoot this? Should I check for back blocks on my SSD - can i do that safely without harming my windows 7 partition? I want to be able to login to my linux desktop again, but after reading all the replies from relevant posts on the internet it's starting look more and more bleak.
Code:Free inodes count wrong (6939155, counted=6830081)
debian: ***** FILE SYSTEM WAS MODIFIED *****
debian: 501759/files (0.9% non-contiguous), 9487363/29296875 blocksI rebooted with "reboot -f" and after systemd had loaded i got a wall of buffer I/O errors that ended with an "Ext4 Error (device sdc1) disk remounted read-only". After having logged into root i ran fsck again and got: "-bash: fcsk: command not found". I went to /sbin to run fsck and was again greeted with the same wall of buffer I/O error on dev sdc1, logical block xxxxxxxx, lost async page write errors. Eventually i got:
Code:fsck.ext4: Input/Output error while recovering journal of debian
debian contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structures
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: - (164879--165105) -(203624--204198)
fix<y>?I quit fsck here before fixing anything with ctrl + z and ran fsck again - this time the buffer I/O errors that occurred last time didn't come up and it went straight to the same the "fsck.ext4: input/out error while recovering journal of debian". It only found two errors which i both fixed:
Code:Block bitmap differences: - (164879--165105) -(203624--204198)
Free blocks count wrong (19809512, counted=19807396)But then i got a bunch of buffer I/O errors again, which eventually ended with:
Code:Error writing file system info: Input/Output error
debian: ***** FILE SYSTEM WAS MODIFIED *****Now every time when i try to run fsck I keep getting the same persistent "Free blocks count wrong (19809512, counted=19807396)" error. and after that ten rows of "buffer I/O error on dev sdc1, logical block 1, lost async page write" for all logical blocks 1 through 10 and there's always a "print_req_error: I/O error, dev sdc, sector 2056" before the buffer i/o errors.
Now I have no idea what to do anymore, how do i troubleshoot this? Should I check for back blocks on my SSD - can i do that safely without harming my windows 7 partition? I want to be able to login to my linux desktop again, but after reading all the replies from relevant posts on the internet it's starting look more and more bleak.