Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected behavior of mount_filesystems on 14.0 (n71map) #276

Open
nick-botticelli opened this issue Nov 28, 2023 · 0 comments
Open

Unexpected behavior of mount_filesystems on 14.0 (n71map) #276

nick-botticelli opened this issue Nov 28, 2023 · 0 comments

Comments

@nick-botticelli
Copy link

nick-botticelli commented Nov 28, 2023

On 14.0 host and 14.0 ramdisk, I get the following error(s) when running mount_filesystems:

seputil: Gigalocker file (/mnt7/83308556-0035-534F-953A-8E596A5BC07E.gl) exists
seputil: Gigalocker initialization completed
seputil: can't open '/mnt1/usr/standalone/firmware/sep-firmware.img4', errno: No such file or directory(2)
seputil: rejecting zero-byte firmware
seputil: failed to load /mnt1/usr/standalone/firmware/sep-firmware.img4 in  mode
mount_apfs: volume could not be mounted: Resource busy

As the error suggests, sep-firmware.img4 is not located in /mnt1

When instead running mount_apfs -R /dev/disk0s1s6 /mnt6, sep-firmware.img4 appears in /mnt6/usr/standalone/firmware/sep-firmware.img4.

After initializing gigalocker, /usr/libexec/seputil --load then panics the device (though this is not my concern).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant