martinich

I recently upgraded my Unraid server from 7.2.5 to 7.3.1 and ran into a confusing networking issue that took some investigation to resolve. I am posting my findings here in case it helps someone else. SymptomsBefore the upgrade: The Unraid GUI and Docker containers were accessible through the same IP address. The server obtained its IP address via DHCP. My router provided a DHCP reservation based on the server's MAC address. After upgrading to 7.3.1: The interface called shim-br0 has taken the IP address associated with eth0 interface, that was bridged to br0 even though it's MAC address did not match the router configuration. The Unraid GUI was no longer reachable on its original IP address. The router still showed the original IP address assigned to the server, but to a different MAC address than specified in the reservation. Docker containers continued to work normally and were accessible on the old IP address. The Unraid GUI became reachable on a different IP address. When investigating the interfaces, I found: br0 had the original MAC address that was configured in my router's DHCP reservation. shim-br0 had a different MAC address. br0 and shim-br0 were using different IP addresses. This resulted in a situation where the original reserved IP address was no longer being used by the Unraid GUI and any system services like smb. Solution1. Disable DockerNavigate to: Settings → Docker Set: Enable Docker = No 2. Disable Host Network AccessWhile Docker was disabled, I also disabled: Host Network Access 3. Reboot the ServerAfter rebooting: The shim-br0 interface disappeared. Only the normal br0 interface remained. 4. Change Unraid from DHCP to a Static IPNavigate to: Settings → Network Settings Change: IPv4 Assignment Method from DHCP to Static Then manually configure the IP address that you want Unraid to use (in my case, the original IP address). Save the settings and reboot the server. 5. Verify ConnectivityAfter rebooting: The Unraid GUI was again reachable on the desired/original IP address. The br0 interface was correctly using that address. Everything appeared to function normally. 6. Re-enable Host Network Access and DockerFinally, I re-enabled: Host Network Access Docker ResultAfter Docker started again: The shim-br0 interface was recreated automatically. However, the previous issue did not return. The Unraid GUI and services remained reachable on the configured static IP address. Docker containers continued to work correctly. Both br0 and shim-br0 now show the same IP address. ConclusionIt appears that after upgrading to Unraid 7.3.1, the interaction between DHCP, Docker networking, and the shim-br0 interface caused the host network identity to become inconsistent. Switching Unraid from DHCP to a static IP while Docker and Host Network Access were temporarily disabled completely resolved the issue. Once Docker and Host Network Access were re-enabled, the system continued to operate normally and the shim-br0 interface no longer caused any IP address confusion. Hopefully this helps anyone else who encounters a similar issue after upgrading to 7.3.x.

I would like to share my findings in case someone else encounters a similar issue after upgrading to Unraid 7.3.1. System Information Motherboard: ASRock IMB-X1316 Boot device: Samsung FIT 64 GB USB flash drive UPS connected via USB: APC Back-UPS BX950MI Previous Unraid version: 7.2.5 New Unraid version: 7.3.1 Original BIOS version: P1.10 (2023-10-11) Symptoms After upgrading from Unraid 7.2.5 to 7.3.1 and rebooting, the server never came back online. Connecting a monitor showed that the system was hanging during the boot process. The boot files were verified successfully, but shortly afterwards USB-related errors appeared: usb 1-11: device descriptor read/64, error -110 usb 1-11: device descriptor read/64, error -71 usb 1-11: Device not responding to setup address. usb 1-11: device not accepting address, error -71This was followed by storage errors involving the boot device: I/O error, dev sda device offline error, dev sda FAT-fs (sda1): FAT read failedEventually Unraid failed to mount required boot components: SQUASHFS error: Failed to read block 0x0 unable to read squashfs_super_block cannot mount /boot/bzfirmwareAt this point the boot process stopped. Initial Workaround After searching for similar issues, I moved the Samsung FIT boot drive from its original USB 2.0 port to a USB 3.x port on the rear I/O panel. The server immediately booted successfully. At first I suspected: a failing flash drive, a damaged USB port, or a corrupted update. However, further testing did not support those theories. Investigation While running successfully from the USB 3.x port, lsusb -t showed: Bus 001: APC UPS Bus 002: Samsung FIT USB flash drive The system logs were completely clean after boot. No USB resets, disconnects, or storage errors were present. I then moved the boot drive back to the original USB 2.0 port and rebooted. The failure returned immediately. Moving the drive back to the USB 3.x port allowed the system to boot again. This behavior was fully reproducible. BIOS Discovery During troubleshooting I noticed that the motherboard was still running the original release BIOS: Version: P1.10 Date: 2023-10-11ASRock has released several newer BIOS versions since then. I updated the motherboard BIOS directly to version P1.80. After the update, I moved the boot drive back to the original USB 2.0 port and tested again. Result The BIOS update did not cause any problems and it well fairly easily. The problem disappeared completely. The system now boots normally from the same USB 2.0 port that consistently failed before the BIOS update. Multiple reboots have been successful. Conclusion In my case: The Samsung FIT flash drive was not defective. The USB 2.0 port was not defective. The Unraid installation was not corrupted. The root cause appears to have been a compatibility issue between: the newer Unraid 7.3.1 kernel, the motherboard’s USB/xHCI implementation, and the original P1.10 BIOS. Updating the ASRock IMB-X1316 BIOS from P1.10 to P1.80 completely resolved the issue. If anyone experiences USB enumeration errors, disappearing boot flash drives, or cannot mount /boot/bzfirmware messages immediately after upgrading to Unraid 7.3.1, it may be worth checking whether a motherboard BIOS update is available before replacing the flash drive or other hardware. Hopefully this helps someone save a few hours of troubleshooting.