So I upgraded my CPU and after first boot I see my server has no IPv4 address. Looked at some old threads and deleted my network.cfg, it reboots I get an IP all fine. If I then reboot the system it once again is unable to set an IP. 

 

I have attached my diags if anyone can assist? Never had this issue before can't see why upgrading the CPU would cause this issue, I did notice my BIOS time was 1 hour behind updated that yet issue still occurs. 

 

Thanks

unraid-diagnostics-20200422-1428.zip

Plug the ethernet cable into the other port and reboot

Getting stuck at /bzimage

 

Edit: OK I restarted again its moving now.. will do same process as above. I do get that stuck at bzimage every so often after reboots. Is my flash drive on the way out?

Edited April 22, 20206 yr by witalit

Won't hurt.  That does imply though that the flash is having issues

Same issue unfortunately. 

 

 

redo the flash drive.  Just make sure to save the /config folder from it

Same again.. Damn man what's going on

Make another virgin boot flash.  Will that boot?  (Nothing will happen, as you're not going to register it or assign any drives)

Yeah sets an IP fine. Don't tell me I have to do a new config just for a CPU swap please

Edited April 22, 20206 yr by witalit

No.  The flash is corrupted.  Grab a copy of it's /config, completely redo it and toss that folder back onto it.  Or toss the /config from the original onto the one you just made and follow the prompting to transfer the licence.

Ah I actually used the same flash drive, was late when I read your reply. Still think its worth me trying a new flash disk? 

Replaced Flash disk just in case. Boots fine after I deleted network.cfg, rebooted and it stays. IP assigned from DHCP then I turn off Bonding and it drops I can no longer contact server. 

 

I restart Network service via IPMI, can get back on box. What I have noticed now is both my eth0 and eth1 have the same MAC Address? See below, last image is what my MAC should be for IPMI nic.

 

 

 

 

 

Edited April 23, 20206 yr by witalit

@Squid Any ideas?

Same users have issues getting a DHCP address with latest release, try setting a static address.

2 hours ago, johnnie.black said:

Same users have issues getting a DHCP address with latest release, try setting a static address.

As easy as that.. :). Working fine now after a reboot, guess I can just keep it static anyways. Thanks to Squid and Johnnie for the help here. 

 

Has this been reported as a bug at all?

 

Cheers

1 hour ago, witalit said:

Has this been reported as a bug at all?

It's a known issue and it should be corrected on the next release.