6.12.3 Lost all networking (server doesn't get an IP from DHCP)

The included diagnostics are from 6.12.2 and for some unknown reason show an incomplete boot up sequence.

 

The diagnostics are missing the driver for the ethernet controller and hence interfaces are not created. This results obviously in no IP address assignments.

 

According to these diagnostics 6.12.2 doesn't have any interfaces at all, this contradicts your statement about reverting. It is impossible the system has connectivity

 

Install version 6.12.3 and include diagnostics of this version.

 

You are looking at a hardware or driver problem, not a bug.

 

Changed Priority to Minor

That's my problem. I installed 4 times last night 6.12.3 and this is what happens. I can take a video to show the upgrade process but here is what I did (like I've done hundreds of times. I've been running unraid for over a decade off/on). Bought my pro key in 2007. 

 

1. Go into Tools > Update OS

2. Unraid detects the upgrade 6.12.3

3. I click the acknowledge release notes and then hit the update button

4. The update dialog comes up, downloads the update zip file and installs. 
5. When the button on the dialog zip file changes from Close to Done I hit the Done button to dismiss it. 
6. I go back to the dashboard just to ma navigate away from the update OS page. 
7. I get the banner at the top to reboot. 
8. I reboot

9. No network. 

I should also say that I checked the file dates of bzroot, bzfirmware kocated in /boot and they are all July 14 which coincides with the 6.12.3 release. 

To revert I just go into the /boot/previous and copy the files back to /boot. This restores functionality. i did it 4 times last night. 

This is incredibly perplexing because I am not doing anything different to update to 6.12.3. And why the diagnostics are incomplete and show 12.2 I have no idea. It doesn't make sense esp if the file dates on the flash match the 12.3 release. 

Ok so I figured out what is going on (honestly couldn't really sleep), but I would like to keep this open as a "bug" because this hasn't happened with other versions, so I'm thinking some kind of logic/etc changed.

 

Root cause: I have a 2nd USB flash drive plugged in that has a different filesystem label (URBACKUP), I've had this for years.. Every upgrade has worked but this one. Going from 6.11 to 6.12, 12.1, 12.2, etc.. all worked, no changes. Unplugging before rebooting into 6.12.3 fixes it.

 

Explanation:

I am often physically away from the  server, and I need a way to restore the services if I'm not around. Unraid's biggest flaw in my opinion in the USB requirement, but I live with it because I still find Unraid the best system, it just means I have to find creative ways to ensure I can maintain the service.

 

The ONE thing you can't do remote is physically change a USB :), and since 2007, I've had many USB fail, but the problem is you don't always know until you reboot and if you're remote, you're screwed.

 

I clone the primary USB to the secondary USB nightly via cron/user scripts. This has worked for years, but the one thing I've learned: the backup USB cannot have the same filesystem label ("UNRAID") or you will get issues on boot. So I rename the filesystem label ("URBACKUP").. In the event of an issue with the USB, I can get access to the system via my VPN/IPMI/IKVM, rename the label to UNRAID, change the boot order in the BIOS, etc.. I have a process I've done a few times that works fine.

 

Again, this has worked for years, but not 6.12.3.. Not sure if the boot process or logic changed.. I do not have the backup USB in my boot order, so it never ever boots from this (another lesson learned from the past), but when Unraid boots and loads the kernel, that's when it seems to go wonky. 

 

Anyway, I understand this may get dismissed, but for some of us, we need ways to recover our systems remotely working within the constraints of the USB.. I need to find a way to get this to work with 6.12.3 now.

 

Thanks!

On 7/16/2023 at 9:14 AM, Stokkes said:

Ok so I figured out what is going on (honestly couldn't really sleep), but I would like to keep this open as a "bug" because this hasn't happened with other versions, so I'm thinking some kind of logic/etc changed.

 

Root cause: I have a 2nd USB flash drive plugged in that has a different filesystem label (URBACKUP), I've had this for years.. Every upgrade has worked but this one. Going from 6.11 to 6.12, 12.1, 12.2, etc.. all worked, no changes. Unplugging before rebooting into 6.12.3 fixes it.

 

Explanation:

I am often physically away from the  server, and I need a way to restore the services if I'm not around. Unraid's biggest flaw in my opinion in the USB requirement, but I live with it because I still find Unraid the best system, it just means I have to find creative ways to ensure I can maintain the service.

 

The ONE thing you can't do remote is physically change a USB :), and since 2007, I've had many USB fail, but the problem is you don't always know until you reboot and if you're remote, you're screwed.

 

I clone the primary USB to the secondary USB nightly via cron/user scripts. This has worked for years, but the one thing I've learned: the backup USB cannot have the same filesystem label ("UNRAID") or you will get issues on boot. So I rename the filesystem label ("URBACKUP").. In the event of an issue with the USB, I can get access to the system via my VPN/IPMI/IKVM, rename the label to UNRAID, change the boot order in the BIOS, etc.. I have a process I've done a few times that works fine.

 

Again, this has worked for years, but not 6.12.3.. Not sure if the boot process or logic changed.. I do not have the backup USB in my boot order, so it never ever boots from this (another lesson learned from the past), but when Unraid boots and loads the kernel, that's when it seems to go wonky. 

 

Anyway, I understand this may get dismissed, but for some of us, we need ways to recover our systems remotely working within the constraints of the USB.. I need to find a way to get this to work with 6.12.3 now.

 

Thanks!

I use Proxmox with unraid inside, which then allows you to add USB drives that way. Say, if you keep one on hand that's empty or otherwise,  (using a windows VM to add stuff to it and you can virtually unplug that way). My unraid is on the fits as well....keeps losing connection, can't even SSH now. Nginx goes down a bunch and more....this is one of the most unstable updates, and it's now october.....