New Install Issue - Kernel Panic - Not Syncing: Fatal Exception in Interrupt

[faceless]

Hello Everyone,

I just built a new box using all of the recommended parts used in the lime-technology servers (Lian-Li case, ASUS board, etc..). Everything boots up fine and I can access the machine via the browser and directly via the command line prompt. Unfortunately, once I start copying my movies over it copies about one file and then crashes with the following error:

895.036821 Kernel Panic - Not Syncing: Fatal Exception in Interrupt

I then need to reboot.

Any help would be much appreciated.

[RobJ]

No immediate ideas, I haven't seen that error before.  It's always best to start with the usual simplification and isolation steps.  Provide a hardware list, and try to capture a syslog, especially one after the crash.  Try earlier versions of unRAID, capture their syslog for comparison.  If using Users Shares and/or Security, turn them off.  Try unassigning the parity drive and doing the same file copies.  Check your power, check temperatures, airflow, check cabling - try swapping cables.  Connect the drives to different ports.  Run the Memtest overnight.  Hopefully results from one of these steps will provide a clue as to the problem.  Has this hardware been tested with another operating system?  Try booting hardware diagnostics disk or a live CD.

[Lanstrom]

I had a similar problem like that too !

Turned out to be the power supply.  I swapped it over and now unRAID is stable.
I only tried it as I had tried everything else and nothing sorted it.

 

[faceless]

Very odd indeed. Did try another power supply to no avail. Temp/cabling/airflow looks good. Haven't yet tried testing with another OS though. Anyone else seen this error before. Weird thing is that it only occurs when I am doing a write. Server is fine overnight as long as there are no writes. Reads seem fine.

[coppit]

I recently upgraded to 4.5 beta 6. I was shuffling files around, trying to consolidate things a bit. Suddenly the server became unresponsive. I rebooted it and hooked up a monitor. Now I get this error.

[coppit]

Hm... Looks like bad memory. 1016 out of 1024 during the boot memory test, and memtest86+ finds lots of errors. I'll try replacing it.

[Joe L.]

Hm... Looks like bad memory. 1016 out of 1024 during the boot memory test, and memtest86+ finds lots of errors. I'll try replacing it.

It could just as easily be incorrect voltage, timing, or clock speed settings for your memory in your BIOS.  If any of those are incorrectly set, even for perfectly good memory, it would still test badly.

Check the BIOS... the settings are sometimes automatically set by the BIOS, and frequently it gets the settings wrong.  If so, set the correct values manually for your specific RAM strips and re-run the memory test.

Of course, if the voltage, timing, and clock speed were set properly, it could just be a bad RAM strip.  Test each in turn, replace as needed.

Joe L.

[Joe L.]

Hello Everyone,

I just built a new box using all of the recommended parts used in the lime-technology servers (Lian-Li case, ASUS board, etc..). Everything boots up fine and I can access the machine via the browser and directly via the command line prompt. Unfortunately, once I start copying my movies over it copies about one file and then crashes with the following error:

895.036821 Kernel Panic - Not Syncing: Fatal Exception in Interrupt

I then need to reboot.

Any help would be much appreciated.

Kernel Panics are almost always related to bad memory.   

run a memory test, through at least one or two full cycles... It might be incorrect voltage, timing, or clock speed settings for your memory in your BIOS.  If any of those are incorrectly set for your specific memory, you could easily get a kernel crash.

Check the BIOS... the settings are sometimes automatically set by the BIOS, and frequently it gets the settings wrong.  If so, set the correct values manually for your specific RAM strips and re-run the memory test.

Of course, if the voltage, timing, and clock speed were set properly, it could just be a bad RAM strip.  Test each in turn, replace as needed.

Joe L.