Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 2
    Yea, the kernel page cache limits block size to the CPU's page size, so for i386/amd64, you can't mount a fs with more than 4k block size. Another alternative is to use e2tools. Commented Apr 25, 2013 at 15:03
  • 1
    Thank you! I was able to access a Seagate Central NAS drive this way. Commented Sep 2, 2015 at 20:45
  • I try this way on 2 machines (kubuntu 14.04 x86 and 15.10 x64), but get freezing and CPU usage 100% by fuseext2 on open mount folder. Can me anybody say, why? Commented Feb 11, 2016 at 13:29
  • I'm getting a similar experience to YShinkarev - hanging when trying to access the fuseext2 mount, also freezes when I try to umount it. Ctrl+c has no effect... Commented Jul 26, 2017 at 17:34
  • 3
    While this does not answer the question per se, you can recover the data using debugfs /dev/sdXX where you can run basic commands such as ls and rdump to copy the files to a safe location. Source: n-dimensional.de/blog/2012/05/01/wd-mybook-live-data-rescue I used this method because the fuseext2 freezes (bugs.debian.org/cgi-bin/bugreport.cgi?bug=776248) Commented Oct 6, 2017 at 15:04