unkdarkstar
-
Posts
5 -
Joined
unkdarkstar's Achievements
Noob (1/14)
0
Reputation
-
That is the board I have as well. Trying to debug over ipmi when not wanting a lot of down time was a mistake on my end. In watching the boot on mine it felt like I never saw it load the driver on boot. I never saw it like I do in stable. But what I did see was that it could not enable/find my vlan on my bond interface.
-
I feel like this linked to my problem and post as well. Only I couldn't even get mine to work on the first boot and rolled back asap. Booting Stable this is my driver. kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
-
I wanted to try rc5 to see if I can solve my stale nfs problem. I did the upgrade. Stopped the array and rebooted. Watching over ipmi I could see it boot. It was complaining about not bring to find vlan.120. The console didn't show any ip's to login to. It had the ip for bond0 but I was not able to ping the GW. After restoring the USB and watching it boot right after the drives it bring ixbge up but in rc5 I didn't see that. What I saw was the vlan error. The board is a Supermicro A2SDi-4C-HLN4F Edit: To be clear the network didn't seem to work at all. I should have spent more time trying to solve why but with the unit down I needed to get it back online. nas01-diagnostics-20220427-1728.zip