Audiobookshelf giving me a endless error and then NAS crashes

Hello,

I’m running TrueNAS Scale with the HexOS install (can’t verify the version of truenas at this moment). I’m looking at different app solutions for things I can do with the NAS, and I thought Audiobookshelf would be interesting. I went through the TrueNAS app browser to get it, and when I tried installing it, it would be stuck attempting to deploy for a few minutes. I then looked at the active logs going on and it gave me this set of lines repeatedly:

2025-04-17 16:42:23.172725+00:00promise: Promise {
2025-04-17 16:42:23.172727+00:00<rejected> [Error: EACCES: permission denied, mkdir '/metadata/logs'] {
2025-04-17 16:42:23.172729+00:00errno: -13,
2025-04-17 16:42:23.172731+00:00code: 'EACCES',
2025-04-17 16:42:23.172732+00:00syscall: 'mkdir',
2025-04-17 16:42:23.172734+00:00path: '/metadata/logs'
2025-04-17 16:42:23.172736+00:00}
2025-04-17 16:42:23.172738+00:00}
2025-04-17 16:42:23.172741+00:00[2025-04-18 01:42:23.169] FATAL: [Server] Unhandled rejection: [Error: EACCES: permission denied, mkdir '/metadata/logs'] {
2025-04-17 16:42:23.172744+00:00errno: -13,
2025-04-17 16:42:23.172746+00:00code: 'EACCES',
2025-04-17 16:42:23.172748+00:00syscall: 'mkdir',
2025-04-17 16:42:23.172750+00:00path: '/metadata/logs'
2025-04-17 16:42:23.172752+00:00} 

I’m not sure why it is freaking out as none of the other apps are presently complaining about permissions and I setup the datasets the same as everything else. But the weirdest part is that after I snagged the cut of the log I needed (since it was zooming by fast with the repeated error), I tried going to the apps tab, but nothing was working and my NAS became unresponsive. I even tried plugging it into a monitor and looking at the terminal there, but I couldn’t type anything directly into the device. So I hit the power button and it gives the error that it failed at unmounting various things before finally turning off after awhile. Once she rebooted, somehow secure boot was enabled (took me a few tries to figure out why it was failing to boot), so I had to disable that to get it to work. Now it is just a rinse and repeat after retrying it a few times.

So anyone have thoughts? XD