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

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

Rename /boot/config/pools/cache.cfg to bak, then reboot and see if it starts without the pool, if yes, then create a new pool, assign all the devices, start array to reimport it.

28 minutes ago, JorgeB said:

Rename /boot/config/pools/cache.cfg to bak, then reboot and see if it starts without the pool, if yes, then create a new pool, assign all the devices, start array to reimport it.

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

Post new diags, but I don't see any error son the syslog, unassigning the pool was mostly a shot in the dark, since there are some known issues importing some.

 

Also try booting in safe mode to rule out any plugin issues.

Just now, JorgeB said:

Post new diags, but I don't see any error son the syslog, unassigning the pool was mostly a shot in the dark, since there are some known issues importing some.

 

Also try booting in safe mode to rule out any plugin issues.

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.

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.

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

1 hour ago, YsarKain said:

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?

Yep

I'm facing exactly the same issue after the upgrade... haven't tried anything yes except for normal reboots.

On the "main" page the unassigned devices is taking a fair amount of time to load.

4 hours ago, YsarKain said:

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?

Okay I've got mine running again.
What I did so far:
Remove all 3 Unassigned Devices* plugins (didn't help), removed NerdTools (which isn't supported anymore due to you know ...), Unraid Connect and ZFS Master for Unraid. Rebooted and it worked. Now I reinstallled Unassigned Devices* and ZFS Master for Unraid and it still runs after a reboot. So I assume it's either related to Unraid Connect (and I also do havve had the API message...) or to NerdTools. Otherwise it might have been one of the others which was resolved by uninstalling and reinstalling them, but I doubt it.

 

Let us know if you have either NerdTools and/or Unraid Connect installed and if uninstalling helps...

2 hours ago, IZSkiSurfer said:

Okay I've got mine running again.
What I did so far:
Remove all 3 Unassigned Devices* plugins (didn't help), removed NerdTools (which isn't supported anymore due to you know ...), Unraid Connect and ZFS Master for Unraid. Rebooted and it worked. Now I reinstallled Unassigned Devices* and ZFS Master for Unraid and it still runs after a reboot. So I assume it's either related to Unraid Connect (and I also do havve had the API message...) or to NerdTools. Otherwise it might have been one of the others which was resolved by uninstalling and reinstalling them, but I doubt it.

 

Let us know if you have either NerdTools and/or Unraid Connect installed and if uninstalling helps...

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?

Edited March 1, 20251 yr by YsarKain

2 hours ago, YsarKain said:

Any way to install those without nerdtools?

Have you disabled both at once or were you able to identify if it's caused by nerdtools (or the Unraid Connect)?

 

Regarding omz/zsh I manually added the following plugin via link: https://github.com/donbuehl/oh-my-zsh/blob/main/oh-my-zsh.plg (plugin looks clean and save to me).
It complained about tmux but tmux was installed anyway by other plugin so it worked all fine.

 

RAR & vim/nano maybe more might be available via https://pkgs.org/

you could also use rar, rar2fs, etc. via docker
just install apropriate containers and write some neat aliases for your shell

Edited March 1, 20251 yr by IZSkiSurfer

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.

16 hours ago, IZSkiSurfer said:

Okay I've got mine running again.
What I did so far:
Remove all 3 Unassigned Devices* plugins (didn't help), removed NerdTools (which isn't supported anymore due to you know ...), Unraid Connect and ZFS Master for Unraid. Rebooted and it worked. Now I reinstallled Unassigned Devices* and ZFS Master for Unraid and it still runs after a reboot. So I assume it's either related to Unraid Connect (and I also do havve had the API message...) or to NerdTools. Otherwise it might have been one of the others which was resolved by uninstalling and reinstalling them, but I doubt it.

 

Let us know if you have either NerdTools and/or Unraid Connect installed and if uninstalling helps...

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.

On 3/1/2025 at 3:16 AM, JorgeB said:

Rename /boot/config/pools/cache.cfg to bak, then reboot and see if it starts without the pool, if yes, then create a new pool, assign all the devices, start array to reimport it.

Uninstalled Unraid Connect which didnt work.  Then renamed cache.cfg to cache.bak and the array started.  Thanks!