My environment: BananaPI with kernel 3.4.108Whenever I run a file system check for the SDcard it results with an read error on block 134217729. Actually this is not surprising as this 32GB card has only 7167999 blocks for the second big EXT4 FS. I also tried to run fsck.ext4 -f -c ( see below ) This didn't help either. It's not a bad block, I think it must be a bad inode which is broken. To answer with no for the question to ignore error didn't help too. Obviously fsck.ext4 can find issues on a file system but cannot repair. My question are there any other non destructive tools available for repairing broken EXT4 fs's with such a problem ? // Hans# fsck.ext4 -f -c /dev/sda2e2fsck 1.42.5 (29-Jul-2012)Checking for bad blocks (read-only test): doneroot: Updating bad block inode.Pass 1: Checking inodes, blocks, and sizesError reading block 134217729 (Invalid argument).  Ignore error? yesForce rewrite? yesError writing block 134217729 (Invalid argument) while getting next inode from scan.  Ignore error? yesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationroot: ***** FILE SYSTEM WAS MODIFIED *****root: 193003/1794048 files (0.3% non-contiguous), 1988723/7168000 blocks
fsck.ext4 can't repair block far behind end of the file system
debian;filesystems