YsarKain

So, at least in my case, it looks like Unraid Connect was the culprit - I renamed the plugin file to .bak and rebooted and the array came up normally. Nerdtools is still installed and omz and rar etc. all work and my aliases are set 🙂 Before I updated Unraid from 6.10 to 7.01 a number of plugins weren't updating, (nvidia, unassigned devices) they all just updated properly.

I'm still up in safe mode so can't modify plugins unless it's through the shell, waiting until tonight to reboot array a few more times. I'm hoping it's unraid connect causing the issue, cause I have my omz set up with all my aliases and I don't really understand what I'm doing in Slack, used to Centos/RHEL/Ubuntu 😛 If it still doesn't work after nixing the plugins I guess the next step would be a reinstall from a new usb.

Both 😛 I'll start with those and see what happens. Is there any way to see the configuration for NerdTools when in safe mode? I know I had python with it and I don't need that now, but I also had omz and rar and now the little scripts and aliases I used frequently don't work. Update: Found the config file, I have mediainfo, mktorrent, rar, rar2fs, unrar, vim, and zsh installed. I really only think I need zsh, rar/unrar, and maybe vim. Any way to install those without nerdtools?

So it seems to work fine in safe mode (except of course for all the plugins being disabled). But every reboot into normal mode results in the system saying the array is starting, but it just sits there. There doesn't seem to be any way to cancel or stop the array starting up, and every time I've set auto-start array to off it goes back on after a reboot. I removed some plugins I don't use anymore but it hasn't seemed to help any. I'm going to reboot one last time into safe mode so I can at least get the array up and then get some sleep, hopefully there is something in the diags that can help. I guess the next step would be to remove all the plugins and then add them back in if the array starts up fine in non-safe mode? thor-diagnostics-20250301-0342.zip

It came up in safe mode with the array down like it should, I put the cache config back and rebooted again in safe mode so I can try to bring up the array and see what happens.

OK giving that a shot. The auto-start array option went back to yes, so I think maybe it's not saving that, I turned it off again so we'll see what happens. I am getting an error from the unraid connect plugin saying the api isn't available, but that's the only error I see anywhere. Looking at the syslogs it doesn't even look like it's trying to start the array.

The array still says it's starting as soon as it boots, cache drives now show as unassigned devices, no other changes.

Tried turning off auto-start array and rebooting, when it came up it immediately says "Starting..." for the array.

Hello all, I just upgraded to 7.0.1, rebooted, and now the array won't start. There is no error message, and nothing shows up that seems concerning in the log, but on the main page it says "starting..." and it's been like that for 30 minutes. All the drives show up in the main list: I've attached the diagnostics as well. Should I try rolling back? thor-diagnostics-20250228-2300.zip

OK in the middle of parity check now but I planned on updating once it finished.

Feb 10 08:49:27 Thor root: plugin: checking: /boot/config/plugins/nvidia-driver/nvidia-driver-2025.02.10.txz - MD5 Feb 10 08:49:27 Thor root: plugin: skipping: /boot/config/plugins/nvidia-driver/nvidia-driver-2025.02.10.txz already exists Feb 10 08:49:27 Thor root: plugin: running: upgradepkg --install-new /boot/config/plugins/nvidia-driver/nvidia-driver-2025.02.10.txz That's all that shows up in syslog, the previous output was from the upgrade window. thor-diagnostics-20250210-0851.zip

Here is what I am getting when I try to update the plugin: plugin: updating: nvidia-driver.plg Executing hook script: pre_plugin_checks plugin: run failed: 'upgradepkg --install-new' returned 127 Executing hook script: post_plugin_checks

I sent them when I posted the above, in a support ticket

Sorry for not getting back to you on this earlier, I haven't been working on this issue since everything else is working ok. I looked in /var/log/unraid-api/stderr.log and I get: [2023-06-15T06:00:01.841] [21605] [ERROR] [emhttp] Failed loading state file from "/usr/local/emhttp/state/var.ini" with "Value "" is not false/true or no/yes." very similar to what the other guy was getting. But there are a bunch of variables set to "" in /usr/local/emhttp/state/var.ini: localMaster="" WSD_OPT="" WSD2_OPT="" shareUserInclude="" shareUserExclude="" regCheck="" fsProgress="" fsUnmountableMask=""

Updated to the new version of the plugin, no change.