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.

Put the old usb drive back in and I get this: Trying to sign out gives the same error I was getting before (GUID_NOT_RECEIVED / Invalid GUID) logs.gz

Tried replacing the USB key and now I get this. I reinstalled unraid connect before trying this.

I replaced the flash drive a few days ago, and still got the message. A second flash drive, same model/size (Kingston Datatraveller 32GB, purchased at the same time as the current flash drive) worked fine connecting to my servers on my trial install of 6.12. I also found this which may give a little more info:

Still having the same issue. Tried deleting the plugin folder and reinstalling, it let me sign in and said the server was registered, but as soon as I went back to the dashboard the "toLowerCase" issue returned.

I removed the plugin, then deleted the /boot/config/plugins/dynamix.my.servers directory. When I reinstalled the plugin, it had me login and link the server to my account again, but it just went back to giving me the "invalid GUID" and "Cannot read properties of undefined(reading 'toLowerCase')" errors again.

I noticed the i button in the top left corner gives some information about this problem, the GUID is listed as GUID-NOT-RECEIVED (which is why the error is saying my GUID ends in IVED and it's invalid). There doesn't seem to be any way to log out, and it looks like it saves the incomplete or corrupt installation through the uninstall process.

It won't let me sign out there either. Just keeps saying my USB GUID is invalid. I swapped USB sticks, but still getting the same error. Is there a way to delete the plugin config files somewhere? I tried uninstalling and reinstalling the plugin, no help.

Addendum to this.... The Toshiba drive was probably fine, but I RMA'd it anyways since it was under warranty. Hopefully I hear back from Toshiba soon. I continued to have issues and in the syslog I saw one of my Seagate drives was constantly giving "Power-on or Reset" errors. Since I had managed to rebuild one of the drives I was able to try swapping drives around to try to diagnose the problem, and I think I did. Turns out it was a power issue, at least partially related to the power disable "feature" in some newer drives. The other Seagate drives in that enclosure would throw reset errors intermittently after I moved the first one I noticed having an issue, and when I tried swapping over some WD 10TB drives they wouldn't be seen at all. I think the reason it did work silently for so long was that there are three power connections on the five bay enclosure. The three connectors came from a 5-cable SATA power connector, and I had attached a splitter with two 4-cable connectors to it (so 2 ports did not have 3.3v, the third one did). I unplugged one of the splitter connections and plugged in another connector on the original line that was close enough to plug in (with 3.3v) and haven't had a drive reset since. What bugs me is that the opposite should be the case - I should have more issues with more cables that supply 3.3v, not less. The alternative was to attach a sata-to-molex adapter and then a molex-to-sata adapter to that and then another splitter, which makes my skin crawl just to think of it. The last drive is rebuilding now, been solid for a day and a half, and should be finished tomorrow. I have two proper SAS expanders coming, finally decided to splurge, so my Frankenstein's Horror of four four-bay, one five-bay, and one three-bay drive cages, sitting on the floor, powered by a 1kw PSU sitting on top of it's box, hooked to a jumper board, with mini-SAS breakout cables and SATA power cables going every which way, will soon be replaced by two 15-bay, properly contained, towers 😁

I am getting the "Cannot read properties of undefined(reading 'toLowerCase')" error also, and when I try to sign out, I get an error that my USB GUID is invalid. I saw a couple other posts from a month ago saying the plugin would be updated to fix this, but the plugin updated since then and still having this issue. Is my USB actually bad? It is a cheap USB stick 🤷‍♂️

the system became completely unresponsive, so I shut it down. I then removed disk22 completely, leaving the slot open. The missing shares are back, I can access all the shares from the network. Share sizes are correct, and in /mnt all the disks are reporting normally. I have to assume the Toshiba 16TB drive was the culprit, and it was somehow screwing with the rest of the array, even when it was not part of the array, since removing it has returned everything more or less to normal. Rebuild is now causing constant drive activity lights, not intermittent, and the speed is still slow (~30 MB/s) but I have a lot of hashing going on in the background because of the shutdown. Hopefully that will clear up in a few hours and rebuild speed will get back to 60-90 - but even if it doesn't, five days for rebuild is a hell of a lot better than 150.