Clean Reboot and now I can't get past initial motherboard splash.

[blocker85]

Here's what I see (cursor is blinking at bottom):

 

It looks like the UNRAID usb drive isn't booting, obviously, but I can't seem to get into the motherboard BIOS either.  Thoughts?  I haven't previously had any issues booting to the USB drive.

 

 

 

 

My Hardware:

• Intel S2600CP
• 2x Intel E5-2650
• 32GB (8x 4GB) Micron RAM

 

Software Setup:

• unRAID 6.4.1
• plugins:
  • Community Apps
  • Dynamix SSD TRIM
  • Fix Common Problems
  • Nerd Tools
  • rclone
  • Unassigned Devices
  • User Scripts
• Dockers
  • Couchpotato
  • lidarr
  • sabnzbd
  • sonarr
  • deluge
  • headphones
  • krusader
  • netdata
  • ombi
  • plexserver
  • plexpy
  • qbittorrent
  • rutorrent
• VMs
  • macOS High Sierra

 

 

[John_M]

Reset the CMOS memory. There's usually a link on the motherboard. Consider replacing the 3V Lithium cell.

[blocker85]

On 4/22/2018 at 11:59 AM, John_M said:

Reset the CMOS memory. There's usually a link on the motherboard. Consider replacing the 3V Lithium cell.

 

I did both and still having some trouble booting but it did eventually boot.  Now I'm getting call trace errors in Fix Common Problems...here are my diagnostics.  Anything stick out?

tower-diagnostics-20180426-0737.zip

[John_M]

Your server was never going to boot if you were unable to enter the BIOS. Now you've reset it you'll have to go through the settings that made it able to boot reliably from USB in the first place.

 

It looks like you have a DHCP problem. The lease on your IP address expired and couldn't be renewed so your server assumed a link local address.

Apr 25 23:00:22 Tower dhcpcd[2633]: br0: carrier acquired
Apr 25 23:00:22 Tower dhcpcd[2633]: br0: rebinding lease of 10.0.1.15
Apr 25 23:00:27 Tower dhcpcd[2633]: br0: probing for an IPv4LL address
Apr 25 23:00:27 Tower dhcpcd[2633]: br0: DHCP lease expired
Apr 25 23:00:27 Tower dhcpcd[2633]: br0: soliciting a DHCP lease
Apr 25 23:00:33 Tower dhcpcd[2633]: br0: using IPv4LL address 169.254.36.227

I'm not sure what caused the call trace, I'm afraid.