gerard / ext4fuse

EXT4 implementation for FUSE

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Unable to open ext4 mounted partition on El Captain

igauravsehrawat opened this issue · comments

Hi there,
Great project but I am struggling to get it working.
Is El Captain supported?

I have mounted my ext4 partition but i can't proceed to get into partition!
Below is the output of mount

    mount                                                      
    /dev/disk1 on / (hfs, local, journaled)
    devfs on /dev (devfs, local, nobrowse)
    map -hosts on /net (autofs, nosuid, automounted, nobrowse)
    map auto_home on /home (autofs, automounted, nobrowse)
    /dev/disk2s2 on /Volumes/Untitled (ntfs, local, nodev, nosuid, read-only, noowners)
    /dev/disk2s5 on /Volumes/Back up (ntfs, local, nodev, nosuid, read-only, noowners)
    /dev/disk2s1 on /Volumes/RECOVERY (ntfs, local, nodev, nosuid, read-only, noowners)
    ext4fuse@osxfuse0 on /Users/root3d/Documents/linux-mount-point (osxfusefs, synchronous)
    ext4fuse@osxfuse1 on /Users/root3d/Documents/linux-mount-point-2 (osxfusefs, synchronous)

Seems like there is something, can you point out how to proceed further?

Thanks

I have the same problem

mount
/dev/disk1 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
/dev/disk3s1 on /Volumes/Mrixs pqi (exfat, local, nodev, nosuid, noowners)
ext4fuse@osxfuse0 on /Volumes/first (osxfusefs, synchronous)

OS X El Capitan 10.11.1 (15B42)

I also have the same issue. I have disabled System Integrity Protection, so the problem goes beyond that feature of 10.11 interfering somehow.

Note that when I try to list a directory in which the filesystem in mounted, I get the following odd behavior:

$ ls -la
ls: linux: No such file or directory
total 0
drwxr-xr-x   3 username  staff   102 Dec 23 15:49 .
drwxr-xr-x+ 62 username  staff  2108 Dec 23 15:49 ..

In this case, I had my linux filesystem mounted at ./linux

I recieved a response similar to the one @briankendall recieved.
Logging in as root with user environment via sudo -s resolved this.

If you need to run a program that you shouldn't run as root and copying them isn't an option, adding user to operator group allowed access to all files that had other or group read.

Accessing files without other read required creating a group with the same name as the file's group and adding user to it. I removed user from operator group after trying this as I would like for the files of operator group, which include atleast raw disk access, to be behind a password check.

Best of luck.

Same result as @patsomaru, but adding the user to the operator group did not help.

@patsomaru Thanks for dropping by.

Accessing files without other read required creating a group with the same name as the file's group and adding user to it.

This confuses me a bit, since i am unable to access file so how can i get to know about file's group?
Can you give an example regarding your instructions?

Cheers

Can confirm that I can mount ext4 partitions as root. But then of course only root can access the files.

Any plans to fix things so that normal user accounts can mount partitions that they can read and write to?

Same here. I can mount and access as root, but can't as user. Although I added the user
to the wheel group and the operator group.

More precisely, my user account seems to mount the partition, but then it can't acces-it. The partition is only available to the group and user 1000.

Any progress ?

I've added my user to the operator group and can mount partitions no problem at all and can access some files / folders no problem at all. However I cannot read files / folders in my users home directory. Is this because of the permissions on the home directory? Do I need to chmod the directory to add read access to all users?

Same problem but I solved adding -o allow_other as mount option, es:
$ sudo ext4fuse /dev/my_device /mnt/my_mount_point -o allow_other

Added a PR (referenced above) to add a line in the README mentioning this. Thanks, @aborigeno, for adding that comment!

The allow_other trick does not work for me on Mac OS X Catalina (10.15.2). Still only browsable by sudo.

Same goes for Mojave

The allow_other trick does not work for me on Mac OS X Catalina (10.15.2). Still only browsable by sudo.

allow_other worked for me with macOS Monterey (12.5.1).