PiShrink: Why is pishrink reports errors that Gpared does not?

Have an Pi OS 11 image file, that works, no issues. When I read the file via Win32DiskImager or in Linux using dd, no issues or errors. When I write the image file via Win32DiskImager or with dd, no issues.

However when I use PiShrink I get the following error… `pishrink.sh -vspzr image.img image-shrink.img

pishrink.sh: Checking filesystem … /dev/loop0 is mounted. e2fsck: Cannot continue, aborting.

pishrink.sh: Filesystem error detected! … pishrink.sh: Trying to recover corrupted filesystem … e2fsck 1.46.2 (28-Feb-2021) /dev/loop0 is mounted. e2fsck: Cannot continue, aborting.

pishrink.sh: Trying to recover corrupted filesystem - Phase 2 … e2fsck 1.46.2 (28-Feb-2021) /dev/loop0 is mounted. e2fsck: Cannot continue, aborting.

pishrink.sh: ERROR occurred in line 64: Filesystem recoveries failed. Giving up…

`

If I use Gparted no such error results. What is the difference? Gparted uses… e2fsck -f -y -v -C 0 '/dev/sdb2

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 22 (8 by maintainers)

Most upvoted comments

I think it’s time for us to join forces and start collaborating more!

I agree with you. But the target repository shouldn’t be this repository. I have no confidence in @Drewsif .

There are 18 outstanding PRs since 2017 … @Drewsif published his hack and now he’s no longer interested in any maintenance of pishrink. Not well done 😦(((((