August 15, 2025Aug 15 I tried to upgrade from Version: 6.11.5 , i simply stopped array, overwrote the BZ files in the usb , waited until it told me to reboot, rebooted.Now i have an unmountable array, ive previously tried to upgrade before and this happened that time too, this time i have more time to try to figure out what the problem is, after mounting the xfs encrypted array using the correct key, it looks like this:Trying the stop the array, results in this:Can anyone please help me? What am i doing wrong here? I do not want the latest unraid, i like to stay behind for stability sake.Thanks in advance Edited August 18, 2025Aug 18 by je82
August 15, 2025Aug 15 Author For now i downgraded to Version: 6.11.5 again and my array mounts just fine with xfs encrypted using the correct passkey.I would like to upgrade though so if you have ideas please let me know. Edited August 15, 2025Aug 15 by je82
August 15, 2025Aug 15 Author unraid produced another diagnostic whenever it was unable to shutdown gracefully after the upgrade to 6.12.15, ive attached the syslog and the diag zip file here in case that helps understand what the issue is: Edited August 18, 2025Aug 18 by je82
August 15, 2025Aug 15 Community Expert Are you entering the passphrase manually before array start or do you have some script/automation?Also, 6.12.15 is EOL, try upgrading again to 7.1.4 and post new diags if they still don't decrypt.
August 15, 2025Aug 15 Author 3 hours ago, JorgeB said:Are you entering the passphrase manually before array start or do you have some script/automation?Also, 6.12.15 is EOL, try upgrading again to 7.1.4 and post new diags if they still don't decrypt.I have it setup so i have to enter the passphrase manually each time i start the system, but i also have some scripts running at launch to mount a share for remote logging:this is my go file:#!/bin/bash# Start the Management Utility/usr/local/sbin/emhttp &#Copy FSTAB to the system on boot and mount the logs folder#nvidia presistance mode#nvidia-smi -pm 1cd /homemkdir nasbackuplogscp /boot/fstab /etc/fstabsleep 5mount -a# Copy files back to /root/.ssh folder and set permissions for key files and known_hosts and authorized_keyscd /root/.ssh/#mkdir .ssh#cd .sshcp /boot/config/sshroot/* /root/.ssh/#cd /root/.ssh/chmod 600 NAS-rsync-key.pubchmod 600 NAS-rsync-key# Copy the monitor script to a writable and executable locationcp /boot/config/monitor.sh /tmp/monitor.shchmod +x /tmp/monitor.sh# Wait for Unraid to fully boot before starting monitor scriptsleep 30/tmp/monitor.sh &the fstab:/dev/disk/by-label/UNRAID /boot vfat auto,rw,flush,exec,noatime,nodiratime,umask=0,shortname=mixed 0 1/boot/bzmodules /lib/modules squashfs ro,defaults 0 2/boot/bzfirmware /lib/firmware squashfs ro,defaults 0 2tmpfs /dev/shm tmpfs defaults 0 0//10.1.1.15/Logs/NAS\040Backup\040Logs /home/nasbackuplogs cifs vers=3.0,username=WebSMB,password=xxxxxxxxxx,uid=0,gid=0,rw,dir_mode=0777,file_mode=0777,users 0 0the monitor.sh is just a script that runs after array successful start that starts a bunch of inotifywait watches which i log to the path /home/nasbackuplogs/x so i can see what files are added/deleted after the fact. (i actually removed this before upgrading from the go file temporarily and it seems it was not the culprit)I would prefer to upgrade to 6.12.15 to begin with. what are your suggestions? Thanks for the support Edited August 15, 2025Aug 15 by je82
August 15, 2025Aug 15 Community Expert Solution 6 hours ago, je82 said:what are your suggestions?Recommend retesting with stock go and fstab files.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.