Server Froze and On Reboot Weird BIOS message came up

Hello,

During the watching of a show, the server froze suddenly (I seemed to have lost netwrok access). I ended up rebooting the server and during the post it had some weird BIOS is missing message (which scrolled passed to fast to read). Then unRAID started and I can access it again as per usual. Normally I have the drives being recognisied before unraid startes and this didn't seem to happen - yet the system appears to be working??

I am posting my log in the hope someone can tell me if something is amiss. Thanks.

One more question. Can you refresh the network address under unraid without rebooting? Not sure I"m using the correct terms here, but I'm asking if I can get a new address on the server without rebooting using the cmd line.

Thx for the help.

syslog-2016-03-10.txt

System appears to be working fine, and if so, then the BIOS is fine too, not missing.  The only oddity was the obtaining of an IP.  There was a delay in connecting, then you were offered one address, then it was rejected, and another was offered, successfully.  Odd!

Mar 10 17:26:00 Tower kernel: REISERFS (device md6): checking transaction log (md6)

Mar 10 17:26:00 Tower kernel: r8169: eth0: link up

Mar 10 17:26:00 Tower dhcpcd[1071]: eth0: carrier acquired

Mar 10 17:26:00 Tower kernel: REISERFS (device md6): Using r5 hash to sort names

Mar 10 17:26:00 Tower dhcpcd[1071]: eth0: broadcasting for a lease

Mar 10 17:26:01 Tower dhcpcd[1071]: eth0: offered 192.168.1.65 from 192.168.1.254

Mar 10 17:26:01 Tower dhcpcd[1071]: eth0: NAK: from 192.168.1.254

...

Mar 10 17:26:02 Tower dhcpcd[1071]: eth0: broadcasting for a lease

Mar 10 17:26:02 Tower dhcpcd[1071]: eth0: offered 192.168.1.66 from 192.168.1.254

Mar 10 17:26:02 Tower dhcpcd[1071]: eth0: acknowledged 192.168.1.66 from 192.168.1.254

Mar 10 17:26:02 Tower dhcpcd[1071]: eth0: checking for 192.168.1.66

Mar 10 17:26:07 Tower dhcpcd[1071]: eth0: leased 192.168.1.66 for 259200 seconds

Which makes me curious why you asked about refreshing the IP.  If it were me, I would reboot the router.  Then when you have time, check the router settings, make sure IP assignments (if any) look correct, no conflicts.

That's an old machine, old BIOS.  It wouldn't surprise me to see hiccups on boot.  Could be dust buildup, CMOS battery getting weak, etc.  You can Ctl-Alt-Del repeatedly, and get an idea what the fast passing message was.

System appears to be working fine, and if so, then the BIOS is fine too, not missing.  The only oddity was the obtaining of an IP.  There was a delay in connecting, then you were offered one address, then it was rejected, and another was offered, successfully.  Odd!

Mar 10 17:26:00 Tower kernel: REISERFS (device md6): checking transaction log (md6)

Mar 10 17:26:00 Tower kernel: r8169: eth0: link up

Mar 10 17:26:00 Tower dhcpcd[1071]: eth0: carrier acquired

Mar 10 17:26:00 Tower kernel: REISERFS (device md6): Using r5 hash to sort names

Mar 10 17:26:00 Tower dhcpcd[1071]: eth0: broadcasting for a lease

Mar 10 17:26:01 Tower dhcpcd[1071]: eth0: offered 192.168.1.65 from 192.168.1.254

Mar 10 17:26:01 Tower dhcpcd[1071]: eth0: NAK: from 192.168.1.254

...

Mar 10 17:26:02 Tower dhcpcd[1071]: eth0: broadcasting for a lease

Mar 10 17:26:02 Tower dhcpcd[1071]: eth0: offered 192.168.1.66 from 192.168.1.254

Mar 10 17:26:02 Tower dhcpcd[1071]: eth0: acknowledged 192.168.1.66 from 192.168.1.254

Mar 10 17:26:02 Tower dhcpcd[1071]: eth0: checking for 192.168.1.66

Mar 10 17:26:07 Tower dhcpcd[1071]: eth0: leased 192.168.1.66 for 259200 seconds

Which makes me curious why you asked about refreshing the IP.  If it were me, I would reboot the router.  Then when you have time, check the router settings, make sure IP assignments (if any) look correct, no conflicts.

 

That's an old machine, old BIOS.  It wouldn't surprise me to see hiccups on boot.  Could be dust buildup, CMOS battery getting weak, etc.  You can Ctl-Alt-Del repeatedly, and get an idea what the fast passing message was.

Thx Rob for the input. Yeah...it's getting old now, but it's usually very reliable. I did reboot the router (first thing I tried). It didn't help. Weird thing was that I could ping the server and it replied, but I couldn't connect through my HTPC, the GUI or SMB shares.

I gave it a clean out mid last year - still very clean and replaced the cmos battery at the same time. "Ctl-Alt-Del" will make it cleanly powerdown. I found if I used the the shift pgup/down buttons I could review the comand line stuff, but only as far back as unraid starting. This message was prior to that.

It could just have been a one off weirdness. Sometimes, the universe trys to be messen with ya!

It could have been an IP conflict that caused the original issue. I reboot my router regularly, so times I get a conflict message on my own PC.  I'll keep an eye on it.

Appreciate the assistance.

Sounds like you took the steps I would have.

You can Ctl-Alt-Del repeatedly, and get an idea what the fast passing message was.

 

"Ctl-Alt-Del" will make it cleanly powerdown. I found if I used the the shift pgup/down buttons I could review the comand line stuff, but only as far back as unraid starting. This message was prior to that.

I meant doing it repeatedly at the beginning during posting, long before anything was starting to boot, right after the message passes.

It could have been an IP conflict that caused the original issue. I reboot my router regularly, so times I get a conflict message on my own PC.  I'll keep an eye on it.

That's another good reason to consider setting up static IP's on the various machines, and/or as IP assignments on the router.  It avoids issues like this, and makes it convenient to always know what the IP is for everything.  (And keeps the syslog a little cleaner.)

I meant doing it repeatedly at the beginning during posting, long before anything was starting to boot, right after the message passes.

Ahh..that makes sense. DIdn't know you could do that.

That's another good reason to consider setting up static IP's on the various machines, and/or as IP assignments on the router.  It avoids issues like this, and makes it convenient to always know what the IP is for everything.  (And keeps the syslog a little cleaner.)

I used to run a static IP on my server, but my router died. The new one I got came with an ISP package and isn't as good. With this new router and a static IP on my server, if often started without a network connection, so I switched it back to a auto one. The new one couldn't reserve an IP like my old one could. Sure wish I was better at computers.

Really appreciate the help. Cheers