Just replaced Unraid USB key and have copies settings over, but Unraid server cant be accessed on network over IP or by name. Suggestions?

It worked perfectly before and the settings are the same 

Edited November 26, 20232 yr by Bjur

Does the system boot fine if you select one of the GUI modes from the boot menu?

Thanks for answering. Havent tried that yet, but out of interest why would it make a difference?

Because right now we don't know if the GUI can be loaded at all...

Just tried a standart reboot, then all my dockers dissapeared.

I then tried to shutdown the system and start GUI mode, it gives Kexec error.

I just changed USB key and transferred license.

Don't get it.

Hope you can help.

 

 

Edited November 26, 20232 yr by Bjur

Updated with all pictures.

@SquidDoes it make sense?

Have tried with several USB keys to test both EFI and legacy. It wont boot from GUI.

I don't know what that error refers to.  I'd surmise though that you should try remaking the flash drive again via USB creator.  And then see if it'll boot as completely 100% stock

I've tried redoing the flash drive through USB creator and now changed the cache drive.

It boots fine with non gui and if I browse flash in unraid I can see it writes to the flash drive, since file dates has changed, but can't access Unraid anymore from Windows or Android like normal earlier. Tried both UNC and IP.

56 minutes ago, Bjur said:

I've tried redoing the flash drive through USB creator and now changed the cache drive.

It boots fine with non gui and if I browse flash in unraid I can see it writes to the flash drive, since file dates has changed, but can't access Unraid anymore from Windows or Android like normal earlier. Tried both UNC and IP.

If you can boot with non-GUI mode then you can get the diagnostics via the command line.   They will be put into the logs folder on the flash drive.  Posting those might help with diagnosing your problem.

Here is the latest diagnostics.

Just went to webinterface and did diagnostics.

unraid-diagnostics-20231129-1414.zip

On 11/28/2023 at 11:36 AM, itimpi said:

If you can boot with non-GUI mode then you can get the diagnostics via the command line.   They will be put into the logs folder on the flash drive.  Posting those might help with diagnosing your problem.

Did it help?

Everything looks normal to me, doesn't the link below get you to the GUI?

 

http://192.168.1.2

On 11/30/2023 at 3:57 PM, JorgeB said:

Everything looks normal to me, doesn't the link below get you to the GUI?

 

http://192.168.1.2

Yes the link gets me to the GUI just, but i cant access it through network map or network share like normal.

What troubles me more is that i completely loose connection to 192.168.1.2 and have to reboot/reset it to get it to boot up again.

Then i dont get access to the log files.

Any thoughts on what it can be causing this?

It was the same with the old USB Key, which is now changed with another i had laying around.

Try with a new flash drive using a stock insatll, no key needed, enable the flash share and see if it can be access, that will show if it's a LAN or server config problem.

Hi Jorge.

I tried a new USB and it worked.

 

The reason was my ident.cfg file was not good, a couple of examples:

hideDotFiles="no" became hideDotFiles="&no"

DOMAIN_LOGIN="Administrator" became DOMAIN_LOGIN="Adiinistrator"

also when it booted up I had a lot of errors saying it couldn't be fixed.

 

So I bought the USB key formatted it FAT32 in slow mode, took to long time, so just cancelled it and quick formatted it. Put Unraid on it and the old config where I changed ident.cfg to correct and hope that will fix it.

 

Also support said I should correct MacVlan, which I also did:)