You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
On 14.0 host and 14.0 ramdisk, I get the following error(s) when running
mount_filesystems
: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).The text was updated successfully, but these errors were encountered: