I updated to 6.10.2-rc3 and now seem to be stuck. Connecting to the server locally it says IPv4 address not set. I followed suggestions in this topic No Network After 6.10.2. Turning off VT-d has not resolved it in my case.

Also to note my server name has defaulted back to "tower" and the disks are not assigned. I have added two new SSD drives whilst powering down for updating.

 

 

tower-diagnostics-20220611-1746.zip

Why did you update to such an old release?   6.10.2 is available on the Stable branch, and 6.10.3-rc1 on the Next branch.

1 hour ago, itimpi said:

Why did you update to such an old release?   6.10.2 is available on the Stable branch, and 6.10.3-rc1 on the Next branch.

This is what the auto update updated too via the webui on the next branch. Also 6.10.3-rc1 released the following day after I updated.

1 hour ago, KeyBoardDabbler said:

This is what the auto update updated too via the webui on the next branch. Also 6.10.3-rc1 released the following day after I updated.

Strange - but the 6.10.2 release on the Stable branch is newer than any 6.10.2 release on the Next branch.   I would suggest getting onto the 6.10.3-rc1 release to see if that fixes your issue as doing so would eliminate any of the issues arising on the 6.10.2 release.

47 minutes ago, itimpi said:

I would suggest getting onto the 6.10.3-rc1 release to see if that fixes your issue as doing so would eliminate any of the issues arising on the 6.10.2 release.

 

I have moved onto 6.10.3-rc1 but the issue is still there. Unable to connect.

 

i have reattached new logs.

tower-diagnostics-20220612-0008.zip

You have link on eth1 but not on eth0, either swap the LAN cable to the other NIC or boot using GUI mode and go to Settings -> Network Settings -> Interface rules and make eth1 eth0