I assume that I can get 4.7 support here , I did not see where else to post for support. I will gladly upgrade to 5 once I get this server up and running.

 

This server has been running for years with no issues. I went away on vacation for a month and decided to shut down my server since no data was to be used or exchanged. Upon starting it up everything seemed to be a normal boot process of the bzimage and bzroot, except when it reached a point where it stoped with a call trace. Please see attachment.

 

Not sure what my next step is. Can someone please assist me with troubleshooting?

 

Much appreciated!

 

Camel

Over the years, computer components gather dust, contact surfaces may gather tiny amounts of corrosion or oxidation, things vibrate loose, things age, etc.  Might be time for a maintenance checkup.  Open it up and blow it out, clean fans and filters, re-seat everything including chips, cards, cables (both data and power), and flash drives.  Don't touch the CPU heat sync though, unless you KNOW it's too hot.  Turn it on and make sure all fans are spinning.  Close it up and reboot.  You might try a memtest too, from the boot menu.

It was a good idea to clean up everything. Thought there might of been a loose power cable on the parity drive but it was fine. Took everything apart cleaned it up nicely including new thermal paste on the processor. Did a memory test that finished fine, I am still at the same place, same screen.

 

Any other ideas?

 

Thanks,

Camel

Any other ideas?

Shooting blind here.

 

Maybe try putting the USB boot drive in a different slot.

 

Try preparing a fresh flash drive with the 4.7 install files, assuming you still have them. As long as you don't assign any drive slots, you won't hurt your data, and it would be instructive to see if it stalls at the same spot.

Prepare a different flash drive with the v5 download and see if it boots okay => DO NOT assign any drives to it ... you just want to see if this also results in a kernel panic.    If it boots okay and you can access the Web GUI okay, then this indicates something may be wrong with your flash drive.    If you get essentially the same issue, then you have a hardware issue of some sort.    If that's the case, run MemTest for  few hours (run the version on the v5 flash as it's a lot more recent and more likely to support your relatively new chipset).