1. I have a pro license.  One day my server wouldn't boot. 

2. I bought a new USB 2.0 drive and put my 6.11.5 backup from 2023-02-24 on it using the Unraid tool

3. I booted into the Unraid GUI.  It knows my system config but won't start array because the key file (Pro.key) doesn't correspond to the USB Flash boot device.

4. I used the "Replace Key" feature in the My Servers drop down menu (in upper right corner)

5. After signing in with Unraid.net credentials I get an error (with a pic of Newman from Seinfeld saying "you didn't say the magic word") and text that says "Failed to receive message from your Unraid server".  Another string says "No data received from Unraid webgui.  Registration must be started from your Unraid webgui [which I did!].  If you did and you received this message please contact support"

I'm out of moves.  Any ideas what's happening?  It's not clear to me if getting a new USB drive means I must get a new key or not, but it clearly doesn't like my old key, and then is failing when I try to get another. 

 

UPDATE: I read that there were a lot of counterfeit Sandisk drives out there (which is what I used above) so I got another brand from Office Depot (Lexar) and am having the same problem.  Still stumped.

 

PS. I should add that the Unraid UI no longer seems to allow them to email you a new key as seen in this SpaceInvader One video (link is cued up to the exact place in the video)

 

Edited March 10, 20233 yr by defcon

Not sure what the error is about but contact support, they can replace the key for you.

I believe this error is happening for people in the Unraid OS GUI mode Firefox. I'll be attempting to fix this error today.

 

In the meantime, if you have a different client to access your Unraid webGUI with this should work.

Thanks for taking a look, @zspearmint.  Here's an update that might help you diagnose it (and my remaining problem if you have thoughts):

1) Lime/Unraid support sorted out the mapping of my key to my new flash drive's GUID.  Thank you! After uninstalling the my servers plugin and reinstalling it the licensing error disappeared. 

2) ...But then upon starting my array, it stopped and gave me a "stale configuration" error  

3) I read somewhere that rebooting can help, but also about some firefox issues. I was able to wipe all cookies/data from firefox settings (still in Unraid OS GUI mode) and still get back to the Unraid Main tab (in firefox) to have the reboot button work (despite having wiped cookies).  

When it rebooted it came up correctly and appears stable 

 

HELP STILL NEEDED HERE: 

My only remaining problem is that for some reason when I reboot I have to go to manually go to my system's BIOS and choose the UEFI Flash drive to boot unraid.  I'd like to put it back in my rack and get back to having it auto-boot into headless mode after power outage or OS upgrade without needing to connect a screen.  It's my only bootable volume and is at the top of the BIOS' priority list.  After the normal Asus boot screen, it switches to an American Megatrends (also BIOS? or maybe for my HBA?) screen that seems to report an error about one of my "Samsung SSD 970 EVO Plus 1TB" M.2 NVME drives since it then shows an error (see video and/or screen shots below) that says "Warning Please back up your data and replace your hard drive. A failure may be imminent and cause unpredictable fail. Press F1 to run SETUP".  I have two of these drives. I use one for all of my docker data and the other is just sitting there unassigned.  I had planned to mirror it in a pool with it's identical sister for redundancy and haven't gotten to it (and was thinking of waiting for zfs).  But now i wonder if the BIOS is somehow seeing it as a problem drive and forcing me to "Press F1 to run SETUP" thereby blocking the ability to autoboot into headless unraid.  Anyway I guess my next step is to mirror the two M.2 drives to remove the unformatted/unassigned one from the equation.  I know Unraid doesn't write the bios but any thoughts welcome!

40 minutes ago, defcon said:

But now i wonder if the BIOS is somehow seeing it as a problem drive and forcing me to "Press F1 to run SETUP"

Possibly one of the devices is failing SMART, there's usually a BIOS option for that, to disable SMART monitoring, you can also post the diagnostics to confirm.

On 3/10/2023 at 10:32 AM, JorgeB said:

Possibly one of the devices is failing SMART, there's usually a BIOS option for that, to disable SMART monitoring, you can also post the diagnostics to confirm.

Thank you.  I disabled a BIOS option called "wait for F1 if error" and it now boots into headless. 

 

UPDATE:  I also saw a video that if your motherboard's (small disc-shaped ) battery is dead it can cause an error that holds the default boot so, I'll plan on replacing the battery too.

Edited March 13, 20233 yr by defcon