I currently have a machine running 7.2.0 that I can't seem to get upgraded. I've tried targeting both 7.2.3 and 7.2.1, but I always fail in the exact same manner.

Plugins have all been updated, the host has been rebooted (multiple times), etc. I don't see anything obvious in the system logs and really don't know where to start looking at to determine what post_plugin_checks seems to have an issue with. Any ideas of where to look/start?

plugin: installing: unRAIDServer.plg

Executing hook script: CA_preHook

Clearing Community Applications plugin cache

Executing hook script: pre_plugin_checks

plugin: downloading: unRAIDServer.plg ... done

Executing hook script: CA_preHook

Clearing Community Applications plugin cache

plugin: downloading: unRAIDServer-7.2.3-x86_64.zip ... done

plugin: downloading: unRAIDServer-7.2.3-x86_64.md5 ... done

writing flash device - please wait...

Archive: /tmp/unRAIDServer.zip

extracting: /boot/unRAIDServer/bzfirmware

extracting: /boot/unRAIDServer/bzfirmware.sha256

extracting: /boot/unRAIDServer/bzimage

extracting: /boot/unRAIDServer/bzimage.sha256

extracting: /boot/unRAIDServer/bzmodules

extracting: /boot/unRAIDServer/bzmodules.sha256

extracting: /boot/unRAIDServer/bzroot

extracting: /boot/unRAIDServer/bzroot-gui

extracting: /boot/unRAIDServer/bzroot-gui.sha256

extracting: /boot/unRAIDServer/bzroot.sha256

extracting: /boot/unRAIDServer/changes.txt

extracting: /boot/unRAIDServer/license.txt

extracting: /boot/unRAIDServer/make_bootable.bat

extracting: /boot/unRAIDServer/make_bootable_linux

extracting: /boot/unRAIDServer/make_bootable_mac

extracting: /boot/unRAIDServer/memtest

extracting: /boot/unRAIDServer/memtest.sha256

extracting: /boot/unRAIDServer/syslinux/syslinux.cfg-

checking sha256 on /boot/unRAIDServer/bzfirmware

checking sha256 on /boot/unRAIDServer/bzimage

checking sha256 on /boot/unRAIDServer/bzmodules

checking sha256 on /boot/unRAIDServer/bzroot-gui

checking sha256 on /boot/unRAIDServer/bzroot

checking sha256 on /boot/unRAIDServer/memtest

Archive: /tmp/unRAIDServer.zip

plugin: run failed: '/bin/bash' returned 1

Executing hook script: CA_postHook

Clearing Community Applications plugin cache

Executing hook script: post_plugin_checks

Thank you!

unraid-diagnostics-20260127-1637.zip

35 minutes ago, joseph.hobbs said:

the host has been rebooted

Do you mean you are running Unraid as a VM?

13 minutes ago, trurl said:

Do you mean you are running Unraid as a VM?

Sorry, no. Running bare metal. Was just trying to indicate that I've rebooted prior to reattemtping the upgrade.

Your flash drive is 120GB? How did you prepare it originally?

It's been a few years honestly. I would have followed the guide at the time for 6.x. It has given me no trouble (that I am aware of) up to this point.

Looking at the host after I attempt an install (and before I cancel it), it looks like it sets things up as expected...

So if I'm reading these plugin files right, it looks like it runs each FILE block in sequence. Based on the output I'm getting during the upgrade process, I feel like it's failing on the 2nd block, specifically commented as 'If Unraid Connect is installed, ensure it is current'. I just uninstalled that and am in the process of rebooting. Curious if that might be the culprit.

Welp, so much for that idea...

plugin: installing: unRAIDServer.plg
Executing hook script: pre_plugin_checks
plugin: downloading: unRAIDServer.plg ... done

plugin: downloading: unRAIDServer-7.2.3-x86_64.zip ... done
plugin: downloading: unRAIDServer-7.2.3-x86_64.md5 ... done

Plugin-Update-Helper for 3rd party driver plugins found, updating...

writing flash device - please wait...
Archive:  /tmp/unRAIDServer.zip
 extracting: /boot/unRAIDServer/bzfirmware  
 extracting: /boot/unRAIDServer/bzfirmware.sha256  
 extracting: /boot/unRAIDServer/bzimage  
 extracting: /boot/unRAIDServer/bzimage.sha256  
 extracting: /boot/unRAIDServer/bzmodules  
 extracting: /boot/unRAIDServer/bzmodules.sha256  
 extracting: /boot/unRAIDServer/bzroot  
 extracting: /boot/unRAIDServer/bzroot-gui  
 extracting: /boot/unRAIDServer/bzroot-gui.sha256  
 extracting: /boot/unRAIDServer/bzroot.sha256  
 extracting: /boot/unRAIDServer/changes.txt  
 extracting: /boot/unRAIDServer/license.txt  
 extracting: /boot/unRAIDServer/make_bootable.bat  
 extracting: /boot/unRAIDServer/make_bootable_linux  
 extracting: /boot/unRAIDServer/make_bootable_mac  
 extracting: /boot/unRAIDServer/memtest  
 extracting: /boot/unRAIDServer/memtest.sha256  
 extracting: /boot/unRAIDServer/syslinux/syslinux.cfg-  
checking sha256 on /boot/unRAIDServer/bzfirmware
checking sha256 on /boot/unRAIDServer/bzimage
checking sha256 on /boot/unRAIDServer/bzmodules
checking sha256 on /boot/unRAIDServer/bzroot-gui
checking sha256 on /boot/unRAIDServer/bzroot
checking sha256 on /boot/unRAIDServer/memtest
Archive:  /tmp/unRAIDServer.zip
plugin: run failed: '/bin/bash' returned 1
Executing hook script: post_plugin_checks

Do you have a current flash backup?

I took a flash backup before I attempted an upgrade, yes.

The config folder from your flash backup is all you need to get all of your configuration on a new install.

See if you can make a new install on a different flash drive and get it to boot, just as a test.

I'll need to source a drive and dig the server out of the rack, so it will take some time. I'll give it a shot and report back.

I really appreciate your help here!

I kept digging a bit before I gave up and came up with this... In reviewing the update package, I followed each command to see if it had been completed so I could track it down where exactly things went awry. I traced it to this block in unRAIDServer.plg (lines 280-284).

# if EFI or EFI- directory does not exist
if [[ ! -e /boot/EFI && ! -e /boot/EFI- ]]; then
  unzip -d /boot /tmp/&name;.zip EFI-/* || exit 1
  sed -i 's|default /syslinux/menu.c32|default menu.c32|g' /boot/syslinux/syslinux.cfg &> /dev/null
fi

When I look at my /boot partition, I have neither an EFT nor an EFT- directory present. The unzip command expects to find files in the ZIP at EFI-/*, but the files are at EFI/*. Due to this, it exits 1. Given I'm running in legacy mode, I definitely don't want a /boot/EFI with these files (based on my understanding of UEFI.

To work around this, initially, I just created a /boot/EFI- directory, and the patch ran fine. For consistency, I will copy the EFI files over to EFI-, as this is what I understand SHOULD be happening.

I'm not sure if something caused the EFI to get deleted or if it was removed entirely in the past. Definitely weird...

Note that having an EFI folder won't prevent you from booting legacy; it just allows you to also boot UEFI. The option used will just depend on how the BIOS is set/supports.

On 1/28/2026 at 2:47 AM, JorgeB said:

Note that having an EFI folder won't prevent you from booting legacy; it just allows you to also boot UEFI. The option used will just depend on how the BIOS is set/supports.

Interesting note, thanks!