RAINMAN

Just as an update, I found my tmp directory was using access mode Read/Write - Slave. I changed it to Read/Write and haven't had an issue since. Could be randomly working since then as the time varies but seems positive so far. Honestly, i have no idea what the difference is. I probably saw somewhere it was recommended and set it at some point.

Unfortunately, its locked up again today so this wasn't the issue. Currently running: Linuxserver.io version: 29.0.3-ls330 Build-date: 2024-07-14T17:27:42+00:00 NextCloud docker won't stop.

Thanks! Will give it a try.

Unlikely, its only this container that ever does it and its been posted by more then just me. I tired these solutions but they dont seem to work. This is the newest builds. Older builds used to be fine.

Anyone else having the issue of this docker locking up? It locks up and I cant stop, restart, nothing. It gives Execution Error. I cant even stop the docker service. I have to do a hard reset of the whole server. Its happened a few times now and seems random when it occurs. Can be anywhere from a day to weeks it works before locking up.

I let it sit for about 20 mins and it randomly went up to regular speed. Unsure why it took so long to get up to speed. Just in case anyone else comes across this. I also ran a parity check and it took the same delay to start getting good speed.

Swapping out a new 12TB in place of an existing 3tb, the rebuild process is sitting at a consistent 6mb/s. I stopped all my dockers/VMs. Doesn't make a difference. I changed the cables and the controller its attached to. No change. I ran drive speed tests (from the docker) while the rebuild was stopped and no issues with speed from any drives or controller tests. CPU usage is minimal. I'm unsure what else to check to make this thing speed up. Any help to get this sped up would be appreciated as I don't really want to wait 25 days for a rebuild. fileserver-diagnostics-20240617-0903.zip

This worked. Thank you! Your help today was much appreciated. No syslog spamming on v2.7.4

Thanks. Its odd because I used the old NUT plugin for years and never saw those messages. This new plugin worked briefly no messages then randomly stopped and now its working again but its kind of unusable as my syslog is filling up. I cant seem to find a way to turn off messages. Any way I can totally disable all syslog witting from NUT? The plugin is running fine and its not in any critical environment so as long as it gives time to do a proper shutdown when I lose power thats all I need. This is what is getting truncated: Not sure what all that means as the unit isnt displaying any noticeable alarms and most wouldn't even apply. Maybe those are possible alarms. unsure.

Its a powerware 9120 (oldie but works well) When I did that I get: When I unplugged the USB and put it into another slot then tried to start it, it came up. Excellent! Not sure why its so finicky sometimes but appreciate the help getting it working. Minor issue: By syslog is getting spammed with the following. Unsure if it matters or how to turn that off.

Can anyone help me figure out why this stopped working? At some point I updated it and it hasnt worked since. It seems there is a fatal error then the driver doesnt work: I've tried different USB ports, rebooting, cant seem to get it working again.

If this is aimed at my question. I do use ZFS but the NextCloud data share is not stored on a ZFS pool or drive using ZFS. Its stored on the array, limited to one XFS disk.

How can I fix this error permanently: I can run a script that fixes the permissions but if I make a change to a share or something in unraid it seems to reset it and i have to run the same script again. Is there something I have in my unraid setup that needs to change so this stays or in the docker? Confused why it keeps reverting back.

I logged out and back in. It's maybe working now. its going through a re-sync.

Anyone else seeing Unable to Connect to Destination? Otherwise everything seems to be fine on my end.