August 11, 20223 yr I must have missed a few memos because my OS are way out of date so I'm catching up on updates. One of my servers is stalled during update from 6.9.2 to 6.10.3. Before I kill the process, reboot or do anything else, would appreciate some guidance on next steps. As of now it's been sitting for about 20 minutes: Aug 11 10:13:08 Farhills1 emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update unRAIDServer.plg Aug 11 10:13:08 Farhills1 root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Aug 11 10:13:08 Farhills1 root: plugin: running: /tmp/unRAIDServer.sh Aug 11 10:13:08 Farhills1 root: plugin: creating: /tmp/unRAIDServer.zip - downloading from URL https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.10.3-x86_64.zip Aug 11 10:13:11 Farhills1 root: plugin: creating: /tmp/unRAIDServer.md5 - downloading from URL https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.10.3-x86_64.md5 Aug 11 10:13:11 Farhills1 root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Aug 11 10:13:11 Farhills1 root: plugin: running: /tmp/unRAIDServer.sh farhills1-diagnostics-20220811-1032.zip Edited August 11, 20223 yr by Sardine8207
August 11, 20223 yr Author Since posting I rebooted the server and tried to update again. It's hanging on this step every time: plugin: updating: unRAIDServer.plg plugin: downloading: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.10.3-x86_64.zip ... done plugin: downloading: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.10.3-x86_64.md5 ... done writing flash device - please wait... Archive: /tmp/unRAIDServer.zip Would I be better trying to upgrade to 6.11-RC3 then down to 6.10.3? or downgrade to 6.9.1 then try going up to 6.10.3? Edited August 11, 20223 yr by Sardine8207
August 11, 20223 yr Author Tried the downgrade to 6.9.1. It's still getting stuck on the same step writing the archive to flash. The server began a parity check after the last reboot, sure enough there's an entry in the log for unclean shutdown detected. Not sure why this got flagged since all restarts have been cleanly initiated from the web GUI. Maybe this is causing the update script to fail silently? In any case I've started a parity check now and will let it run, then reboot and see where things stand. Is there anything else I can check/try while the parity check grinds along?
August 11, 20223 yr Community Expert Solution Do you have a current flash backup? You can get the zipped download of whichever version at the download link in upper right of the forum, then copy the bz* files from the download to the top level of your flash drive
August 12, 20223 yr Author Yeah, lots of versioned backups, but I'll make one manually for good measure before overwriting anything. Will give it a shot this evening!
August 12, 20223 yr Author Had some time with nobody on plex this afternoon to update and reboot. Worked just as described! Thanks Every reboot is still showing unclean shutdown, but I'll make another post for that issue if needed. Looks like another cable has gone bad (read errors on a disk causing it to disable during parity check), so will fix that first. Edited August 12, 20223 yr by Sardine8207
August 12, 20223 yr Community Expert 27 minutes ago, Sardine8207 said: Every reboot is still showing unclean shutdown, but I'll make another post for that issue if needed. It might be worth reading this section of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI.
August 12, 20223 yr Author Awesome info - 99% it's a VM I set up not so long ago that's running out of time on shutdown. I've only given it 2-cores and 4G ram because its only purpose is to be an always-available destination for scans from a crappy printer. It's VEERRRRYYYY slow to do anything related to starting and stopping. Edit: Bingo! Found this in syslog: Aug 12 14:35:56 Farhills1 root: The following VMs are still running, forcing shutdown: Windows 10 - Scans Thanks again for all the help. 2 for one in this post! Edited August 12, 20223 yr by Sardine8207
September 22, 20232 yr @Sardine8207 Is it safe to say that all the previous comments above are null and void, and all you did was shut down the VM, and you could have proceeded from 6.9.2 to 6.10 or 6.11 without error?? Forgive me for my ignorance, I'm new to Unraid, and we inherited a huge network with an Unraid server which has 10 pihole DHCP servers and 5 vm's. Edited September 22, 20232 yr by skytouch-usa
September 22, 20232 yr Author Not sure if the VM was preventing the upgrade. Maybe the unraid update process reverts to the original version if the update reboot is unclean? That or it was 2 separate issues and something else glitched preventing me from upgrading. Manually extracting the update files in the boot drive allows the update to happen anyhow, so I suspect 2 issues.
September 22, 20232 yr 14 minutes ago, Sardine8207 said: Not sure if the VM was preventing the upgrade. Maybe the unraid update process reverts to the original version if the update reboot is unclean? That or it was 2 separate issues and something else glitched preventing me from upgrading. Manually extracting the update files in the boot drive allows the update to happen anyhow, so I suspect 2 issues. Understood. Thank you for the quick reply!!
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.