Unable to install on M1

[nhusby]

I am unable to install this on apple silicon.

I tried installing MacFuse via brew, but that didn't work, so I installed it from the github release and did all of the security stuff. Then I tried installing ext4fuse with this command brew install ext4fuse and I get the following error:

brew install ext4fuse                            
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).

ext4fuse: Linux is required for this software.
libfuse@2: Linux is required for this software.
Error: ext4fuse: Unsatisfied requirements failed this build.

[javierlopezdeancos]

The same error for me in Ventura 13.0.1

[imf]

I am also having this on Ventura 13.0.1...

It has now become quite hard to work with Raspberry Pi SD cards on a Mac.

[sarambasich]

I am also experiencing this on a 2017 Intel MacBook Pro running Ventura 13.0.1 (22A400).

[ramazk]

Same on M1 Monterey 12.3.1. MacFuse updated to last 4.4.1 version but it didn't help.

[damonbreeden]

due to Homebrew/homebrew-core@ab05068#diff-5b5676e31cbcdb12ec4fc584f8f80f834183d0634835e53b2cea9fdc4fe63d8dR14

i'll try and make my own tap that doesn't have this limit

edit: brew took a lot of steps to deprecate fuse, this is considerably more involved than just commenting out the requirements line: https://github.com/Homebrew/homebrew-core/pull/64491/files#diff-5b5676e31cbcdb12ec4fc584f8f80f834183d0634835e53b2cea9fdc4fe63d8d

i'll take a closer look next month when my company does open-source fridays (we work on OS projects instead of work projects one day each month)

[mitchellvanbijleveld]

This is really unfortunate. I hope there will be a fix in the future!

[damonbreeden]

so... brew took a lot of steps to place this package in this situation, and looking closer at it i didn't care to try to reverse engineer all that effort

it's not very hard to build this pkg manually, and if you're in the situation where you're on macOS and trying to mount ext4 volumes, it can pretty reasonably be assumed that you're comfortable with the command line

so with that in mind, these are all the steps required to build the pkg and use it
install mac4fuse from https://osxfuse.github.io/, restart

git clone https://github.com/gerard/ext4fuse.git && cd "$(basename "$_" .git)"
make
mkdir ~/ext4_mount
diskutil list # shows you a list of all disks connected to your system, choose your ext4 disk/partition
sudo ./ext4fuse /dev/disk4 ~/ext4_mount -o allow_other # sudo is required
# approve all the security prompts, reboot
sudo ./ext4fuse /dev/disk4 ~/ext4_mount -o allow_other # run again after reboot

lsa ~/ext4_mount 
total 40
dr-xr-xr-x  4 1000  1000    4.0K Nov 26 10:49 Saturday Night Live
dr-x------  2 root  wheel    16K Dec 16 08:50 lost+found

# when finished
sudo umount ~/ext4_mount

[marciano1]

Buster
My diskutil disk:
/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *64.0 GB disk4
1: Windows_FAT_32 ⁨boot⁩ 268.4 MB disk4s1
2: Linux ⁨⁩ 63.7 GB disk4s2

Mount error: Partition doesn't contain EXT4 filesystem

[swoodford]

@marciano1 I had a similar error:

/dev/disk6 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *31.9 GB    disk6
   1:             Windows_FAT_32 boot                    45.2 MB    disk6s1
   2:                      Linux                         31.9 GB    disk6s2

ext4fuse % sudo ./ext4fuse /dev/disk6 ~/ext4_mount -o allow_other
Partition doesn't contain EXT4 filesystem

[damonbreeden]

You need to mount the partition not the disk, eg disk6s2

…

On Feb 24, 2023 at 5:41 PM -0500, Shawn Woodford ***@***.***>, wrote: @marciano1 I had a similar error: /dev/disk6 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *31.9 GB disk6 1: Windows_FAT_32 boot 45.2 MB disk6s1 2: Linux 31.9 GB disk6s2 ext4fuse % sudo ./ext4fuse /dev/disk6 ~/ext4_mount -o allow_other Partition doesn't contain EXT4 filesystem — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[swoodford]

yes, you are right, I was going to edit my comment but you were too quick! got a bunch of security warnings (on Ventura 13.2.1) which I'll have to work through then try again

[swoodford]

After all these security messages, about 7 reboots, booting into the Recovery environment and changing settings in Startup Security Utility I got it working!

System Extension Blocked

The system extension required for mounting macFUSE volumes could not be loaded.

Please open the Security & Privacy System Preferences pane, go to the General preferences and allow loading system software from developer "Benjamin Fleischer". A restart might be required before the system extension can be loaded.

Then try mounting the volume again.

To enable system extensions, you need to modify your security settings in the Recovery environment.

To do this, shut down your system. Then press and hold the Touch ID or power button to launch Startup Security Utility. In Startup Security Utility, enable kernel extensions from the Security Policy button.

A program tried to load new system extension(s) signed by “Benjamin Fleischer”. You can enable these extensions in Privacy & Security System Settings.

[roxgib]

How do I trigger these 'security prompts'? I'm able to mount a drive using the instructions @damonbreeden provided and list the contents with sudo ls, but I can only access it using sudo and only certain commands work (e.g. rsync can't see inside even with sudo)

[damonbreeden]

Sounds like you forgot to use ‘allow_other’ when you mounted

…

On Feb 28, 2023 at 1:27 AM -0500, Sam Bradshaw ***@***.***>, wrote: How do I trigger these 'security prompts'? I'm able to mount a drive using the instructions @damonbreeden provided and list the contents with sudo ls, but I can only access it using sudo and only certain commands work (e.g. rsync can't see inside even with sudo) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>