I would appreciate any insight into my issue.

 

Upgraded my unraid server today with new mobo, ram, and processor.  

Upgrade was completed in a few hours and I was able to boot into unraid, but noticed on the console that the IPaddress for the server had changed with the upgrade.

I was able to access the server over the network with the new ipaddress and all seemed well. All dockers, VM's etc. working, and hardware was working at that point.

As I do have port forwards on the router for remote access, I decided to try and change the server ipaddress back to the original one.

I went into the Network settings and changed it there per suggestions on the forum. At that point, I lost access to the server over the network immediately and haven't been able to get it back.

 

Things I have done.

 - changed network config file on the flash back to original post upgrade ipaddress. No help.

- rebooted the router multiple times after any change. No help.

- renamed network config file on the flash, rebooted unraid, new file created with newyet another ipaddress at boot. Still no access from the network to the new ipaddress.

Unraid boots sucessfully every time, shows the ipaddress as last entry on the console, but no access able over the network.

Also noticed that when I check the router, the unraid server never shows up as a connected device.

 

I am trying to find out how to produce diagnostics from the command line to add to this note and will do that once i get the correct commands, if possible.

 

Thanks in advance.

 

any help would be greatly appreciated. 

Adding Diagnostics File 

tower-diagnostics-20240701-1656.zip

Are you access thr http://10.0.0.158 ?

Yes, I have tried both http://10.0.0.158 and also https://10.0.0.158

 

There is a change in the symptoms from yesterday though. Yesterday, the tower never showed as being connected to the router. Today, when I checked the router, it shows the "Tower" connected on ipaddress 10.0.0.158. Bur I still cannot connect via the web interface

 

Try removing this from the go file:

 

ethtool -s eth0 wol g

JorgeB, Thanks for the help, but I do not appear to have a go file. I searched the net for the location of the go file in unraid, and was told it is a file on the flash drive. I checked the flash drive on windows and no go file.

 

I have also just restored the flash drive from a backup I made prior to upgrading the hardware. It boots up fine but the console says that the ipaddress is now 169.254.32.119. However, if I type ifconfig in the console, it says that the br0: interface ipaddress is 10.0.0.158. also, I have no other devices connected to the router with an ipaddress beginning with 169. 

 

I also noted that after the server boots, the "Tower" shows up on the windows network, but when I try to access it, windows is saying that the server refused connection.

 

It appears that the network setting are hosed but I am unable to correct.

to repeat, everything worked fine after the upgrade until I attempted to change the IPaddress in the Network Settings to the servers former ipaddress. At that point all web connectivity stopped and have been unable to get it back.

 

Thank you again for the help.

34 minutes ago, tomjrob said:

but I do not appear to have a go file.

Without a go file the GUI will not work, but there's a go file in the diags, post the output of

 

cat /boot/config/go

 

Those diagnostics were posted before I restored the flash drive from a backup. I used the Unraid creator tool to do the restore and now I realize that the tool does not copy everything from the backup over . One of the things that is not moved over is the go file, amongst others.

There is no cat directory, but I was able to look into /bot/config/ and there is no go file.

 

Can I just copy all files from the backup over to the flash drive with another tool and then boot?

 

I have been an unraid user for 10 years and have never been this deep into the weeds. All from trying to change the ipaddress using the network settings. Not sure where to go from here. the server is unuseable if I cannot access the interface.

So I did copy the Config folder from the backup and then I was able to boot and access the array over the network. So progress here, but somehow the disk configuration got confused and and decided Disk1 of the array was the wrong disk (it wasn't). However I just started the array anyway and the disk is being rebuilt.

 

I would still like to change the ipaddress of the array back to what s was before the upgrade but I will wait on that because at least the upgrade is completed and the array is working.

Is there anybody who knows the proper way to change the ipaddress correctly without losing network access, I would be grateful for the info.

 

this would save me the effort of adding port forwards, etc. to the router for the new address and also save me from having to change all of the Wireguard settings for VPN access.

 

In any case, thank you JorgeB for your assistance here.

5 minutes ago, tomjrob said:

I would still like to change the ipaddress of the array back to what s was before the upgrade but I will wait on that because at least the upgrade is completed and the array is working.

 

You could set the IP address to be a static IP address in the GUI.     SETTINGS   >>>   Network Settings      BUT you then have go to your router settings and 'tell' it what you did.  (It will remember about the old hardware and what IP address it had!)  You will need the MAC address of the NIC when you do this.  I can't give you specific instructions because each router has different approaches to configuring a static IP address.  ( You might have to go the router Manufacturer's website and download the manual...)

 

13 hours ago, tomjrob said:

Those diagnostics were posted before I restored the flash drive from a backup.

Next time please post the current diags, looking at old ones may not be relevant, like in this case.

I decided to leave the array at the new ipaddress so all is complete here.

I am still not sure why my flash backup did not contain all of the files, including the go file, but after restoring from a prior backup, I was able to update after the array booted, and all is well. Only app lost was web-virt-manager. Looks like that is no longer an option. I hope Limeteck has plans to provide that functionality somehow going forward.

 

Thanks to all for the help.