Random Reboots since upgrading to v2.4



  • I upgraded to v2.4 on Feb 8th and since then I have noticed random reboots.  I kept getting messages of the disk mirror rebuilding.  I thought I probably had a failing disk so I finally had some time to look into it today and actually it appears to be rebooting/crashing randomly from what I can tell.

    The uptime was only an hour when I looked at the console and I sure didn't reboot anything and we haven't had any power outages so it had to reboot on its own.  I've looked at the system logs and I don't see anything indicating any issues.  Before I upgraded this system just hummed a along without any issues.

    System is a ECS ITX board with a AMD E1-2100 APU, 4GB RAM, Onboard RealTek NIC and additional Intel NIC in PCI Express slot.

    Anyone got any tips or suggestions of things to look at?



  • Hi,

    If you have some time :

    • Add an UPS,

    • Test your drive(s),

    • Switch back to 2.3.5 (this means using an older FreeBSD kernel / driver set - this might be an issue)

    • Become a member of the Realtek NIC owner club.


  • Rebel Alliance Developer Netgate

    To determine what the problem is, we would need to see the crash dump output. Assuming it is keeping a crash dump.

    Have you see the console when it reboots? Is there any crash output scrolling by? Or does it just reboot itself?

    If it reboots without a crash dump, the odds are higher that it's hardware or hardware-related (drivers, etc)



  • How will a UPS help it from randomly rebooting?  Drives are fine, again this just started happening since I upgraded.

    I fear I am gonna have to downgrade, I am not exactly sure how though.

    @Gertjan:

    Hi,

    If you have some time :

    • Add an UPS,

    • Test your drive(s),

    • Switch back to 2.3.5 (this means using an older FreeBSD kernel / driver set - this might be an issue)

    • Become a member of the Realtek NIC owner club.



  • I have no idea if its keeping a crash dump.  Its a stock install, I haven't done anything fancy just installed some available packages.  As I said this thing was humming along without issue for well over a year until I just upgraded to 2.4.

    I looked into the log and I don't see anything, just the dmesg output of the boot.  It reboots on it own.  Where would I find a crash dump if it is keeping one?

    @jimp:

    To determine what the problem is, we would need to see the crash dump output. Assuming it is keeping a crash dump.

    Have you see the console when it reboots? Is there any crash output scrolling by? Or does it just reboot itself?

    If it reboots without a crash dump, the odds are higher that it's hardware or hardware-related (drivers, etc)



  • @chrispeden:

    I am not exactly sure how though.

    I don't understand.  2.3.5 is available for download.

    1. Save current config.
    2. Download and re-install 2.3.5 from scratch.
    3. Restore config, this will also re-install all packages.