andyd

I ended up disabling Docker to delete the datasets - not an obvious thing to know but I'll know going forward

That did address it ... thanks! Can't communicate with the server but I think this has to do with Opnsense where the nut server lives. I'll have to check on that

Hi I'm trying to set this up for the first time - setting this up as slave... 1. There is a small red hand near the monitoring password - why is that the case? 2. If I try to enable the service I see the below. Not sure what to make of any of the lines Apr 19 12:26:24 HomeServer rc.nut: Writing NUT configuration... Apr 19 12:26:27 HomeServer rc.nut: Updating permissions for NUT... Apr 19 12:26:27 HomeServer rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... Apr 19 12:26:27 HomeServer rc.nut: Disabling the NUT Runtime Statistics Module... Apr 19 12:26:28 HomeServer rc.nut: fopen /var/run/nut/upsmon.pid: No such file or directory Apr 19 12:26:28 HomeServer rc.nut: Could not find PID file to see if previous upsmon instance is already running! Apr 19 12:26:28 HomeServer rc.nut: Unable to use old-style MONITOR line without a username Apr 19 12:26:28 HomeServer rc.nut: Convert it and add a username to upsd.users - see the documentation Apr 19 12:26:28 HomeServer rc.nut: Fatal error: unusable configuration

Hi, I am trying to delete datasets for Apps that no longer exist. I get the following error... "cache/appdata/mariadb-official: Operation not permitted" Is there a way to get around this error?

Not sure if I would consider this an unclean shutdown but can someone correct me if I'm wrong. Do I have to turn off the array first before shutting down in Gui? Also would a running VM not shut down before shutting down Server via Gui cause this?

I haven't had any issues since I posted this which is the longest it's gone. I didn't swap out anything. What I did do is disable app backup which I had forgotten about. Not 100% sure if that was the issue but after disabling that so it's not running at the same time as the zfs backup - seems ok now 🤷‍♂️

I ended up pausing the rebuild (knowing it would restart) and shutdown. After that, it started up successfully

Ah dockers did start up but VM refuses to. homeserver-diagnostics-20231229-1432.zip

Sure see attached ... thanks!

Or maybe I should ask why would these services fail to start? Since it's in the middle of data rebuilding I can't turn off server and back on.

I went through this process... https://docs.unraid.net/legacy/FAQ/parity-swap-procedure/ 1. Did not realize it said `legacy` 2. Seems overkill With that said, after copying over parity it's now building on the demoted parity. I've done data rebuilds before and the array was still usable along with docker / vms. Why would it not be in this case?

I ran the extended test and it completed without error. Attached is the smart report homeserver-smart-20231211-1820.zip

homeserver-diagnostics-20231211-1306.zip

As far as I can tell there are 0 issues with this drive. No smart errors before and after converting it to zfs for the sole purpose of backing up app data. since zfs formatting, drive has been disabled two times with successful rebuilds. Now on third disabling before zfs formatting this drive has been running as a data drive for several years with no issues. any reason why it would be an issue now? The drive as it stands only handles zfs backup. No data is being written to it otherwise

Ok thanks - I did the steps without going into maintenance mode and drive is fine again