Womabre
Members
-
Joined
-
Last visited
-
I created a bug report here:
-
Summary: After updating to Unraid 7.2, containers such as Nextcloud intermittently lose write access — uploads via web UI or sync clients fail. The issue appears to affect other containers as well and seems related to ZFS mounts becoming unavailable. Workaround: Execute zfs mount -a manually or via a scheduled user script (e.g. hourly cron) to restore write functionality. The issue is currently being discussed here:
-
Thanks! I just updated to 7.2.0 and my Nextcloud AIO container was down after a backup this night. And this was the fix! Before running the zfs mount -a command I got an error when running touch /mnt/user/nextcloud/test.txt
-
This has been fixed in 6.12.10 Version 6.12.10 2024-04-03 - Release notes
-
Thanks! Will keep an eye on that thread.
-
Just downgraded to 6.12.8. All drives immediately show up again.
-
When I switch the missing drives to a slot where the drive shows up the drive is available but the switched drive is now missing. Seems to be an issue with the config, driver, cable or hardware. Both slots are connected to my HBA but the other drives connected to it show up without an issue. I reseated all cable, without effect. Can someone maybe see something weird in my diagnostics? Attached are my diagnostics. breedveld-diagnostics-20240328-1426.zip
-
For me it was the IPMI plugin. Took around 30s on every page load to get the temp, fan speed etc. Remove it, everything is lightning fast again.
-
I've also been having this issue for year now. Running 6.12.5 (upgrading to 6.12.6 after writing this, the update triggered me to search for a solution again). Attached are my diagnostics. breedveld-diagnostics-20231202-1236.zip
-
Also got this issue for years now. The custom threshold is just ignored... I get notifications at 80% which is ridiculous for 10TB drives. The settings in dynamix.cfg are: warning="96" critical="97" unraid v6.12.4
-
Are you using the Unassigned Devices plugin to mount the NAS to your unraid system?
-
Yes, no problem. Just create two, or more, instances of the docker. One for each account.
-
I have everything running smoothly again. Thanks everyone for all the help, it was very useful! 🙂 Thanks! Set up that script to run hourly.
-
Just restarted the server again. Everything was looking OK. So I started recreating my docker.img After a few minutes the log was getting spammed with errors. And the btrfs file system switched to read only. breedveld-diagnostics-20210708-1540.zip
-
Just checked all the BIOS settings. No overclocking is enabled anywhere. I think the frequency you see in memtest is the CPU. Has been running quite a while now, no errors. I'm thinking maybe my SSD is dying...
