Jorgen Lundman

Hmm could we change the import script to run `dtruss zpool import ....` and see which actual syscall returns the error...

You might need to disable SIP for dtrace - for it to be able to run

Ah yes, that is awkward. Hmm what can we do without SIP changes hmmmmm

5 is just EIO, but that might be translated to a different error elsewhere. If we are lucky maybe there is some messages in vnop_debug, which you can set to...

Ok sorry, had a zoom meeting, so didn't have time to finish. Make the import script have ``` sysctl kstat.zfs.darwin.tunable.vnop_debug=1 zpool import ........ ``` Then take note of the time...

Although, isn't you log pretty much saying it's failed? ``` "target":"/Volumes/zDisk/Users/sterna-marine", "pid":396, "errno":1, "deny(1) file-mount /Volumes/zDisk/Users/sterna-marine", "process":"zpool", "flags":69, "uid":0, "action":"deny","normalized_target":["Volumes","zDisk","Users","sterna-marine"]} 1 libzfs.2.dylib 0x0000000102c8c5c8 zfs_mount + 828 2 libzfs.2.dylib 0x0000000102c8dbda zpool_enable_datasets...

Certainly sounds like it is denying zpool from mount. It needs to read from disk4 boot, to find the directory to mount ontop of

I don't get why its refused at boot, and works after login. "id" presumably says your login name after all

What is it you are trying to do? The "DiskUtility" features, that has ZFS is not connected to us, but the old ZFS support - we have not got any...

Ah right - great. Make sure to try the new port sometime as well, in case there are regressions to fix before the first release