t0mi

okay after investigation i found out i pointed the mariadb config and data folders to /mnt/nvme and not /mnt/nvmepool so files were written in RAM, yeah i never rebootet... after update all gone... this was a stupid mistake because the backup script only backup'd the normal /mnt/user/appdata and /mnt/nvmepool/appdata

Hi all, I ran into a critical issue right after updating Unraid to 7.1.4: - I had a dedicated second encrypted ZFS pool (`nvmepool`) that I used exclusively for sepperate appdata. - This pool hosted 2x MariaDB databases for both Nextcloud and WordPress. - After the update, the entire pool is basically empty – only a few MB used, all previous appdata (including the DB directories) is gone. - No ZFS snapshots were enabled. - I do have CA Appdata Backup archives, but unfortunately they don’t include the MariaDB data itself, only the container templates. What I’ve checked so far: - `zpool status` → pool is ONLINE, mirror healthy, no errors. - `zfs list` → only tiny, freshly created datasets, none of the old ones remain. - `zdb -l` on the devices returns only “failed to unpack label”. - Searching the pool for `ibdata1` or `.ibd` files yields nothing. So it really looks like the Unraid update either reinitialized or completely wiped the ZFS pool contents, and all databases are gone. **Questions:** - Has anyone experienced something similar – a separate ZFS pool used for appdata being wiped after an Unraid update? - Are there any realistic recovery options, like `zpool import -T` (older TXG) or using tools like `zfs_recover`? - Has anyone successfully recovered MariaDB data (ibdata1/ibd files) from a ZFS pool without snapshots? Any insights, experiences, or even confirmation that I’m out of luck would be really appreciated. These databases contained a lot of work (WordPress + Nextcloud). Thanks 🙏

oh you are completly right

Hello, i searched for the exact same (im running a gameserver docker for my friends and sometimes the server have to be restarted) Im also hosting nextcloud so i created a user for them where if they need to restart they just create the file restart.txt the script: #!/bin/bash # Name of the Docker container CONTAINER_NAME="CoreKeeper" # Path to the watch file RESTART_FILE="/mnt/nvmepool/appdata/nextcloud/data/corekeeper/files/restart.txt" # Infinite loop to check for the file while true; do if [ -f "$RESTART_FILE" ]; then echo "File $RESTART_FILE found. Restarting the Docker container..." # Restart the Docker container docker restart $CONTAINER_NAME # Delete the file to reset the process rm -f "$RESTART_FILE" echo "Docker container has been restarted and the file has been deleted." fi # Wait for 60 seconds before checking again sleep 60 done UPDATE: do it as userscript in settings and forget that below In Unraid you open the console and create the restartdockercontainer.sh Create new file and paste the code inside nano restartdockercontainer.sh CTRL+X and save it with Y use following command so the script can be executed chmod +x restartdockercontainer.sh you then can run it with nohup ./restartdockercontainer.sh & if you restart your unraid maschine u would need to start it again, you can check if it is running with command ps and kill it with kill <id>

hello may you can fix the monero-gui? ---Something went wrong, can't download Monero-GUI, putting container in sleep mode---

i have the same problem now, and nice my server is down! great ... im very angry even because the usb key which is recommended in guides FAILED. the first key was a sandisk but it had a GUID problem... and now i cant replace license... such a bullshit