My unraid system has experienced a crash that I need help in deciphering my problem.  When the lockup occurs I have no access via the webservice from my windows 7 PC or using putty to telnet in.  I do have a keyboard and monitor on the unraid box.  I have attached a digital picture of what the screen showed and it is attached to this posting.  The keyboard is completely unresponsive and my only option is to turn the unraid box off and then back on at which point it will reboot normally and function normally for what appears to be a random amount of time.  With the most recent crash I pulled the flash drive and looked at the logs directory and nothing had been written to this since October 2nd.  I have not changed any hardware since January when I added a monoprice sil3132 sata expansion card.    I have been running 4.5.6 for the past two weeks or so.  I had a crash like this three months or so ago and did not think to take a picture of the screen – I rebooted and everything worked for a month or so.  I had another crash yesterday and I rebooted and it happened again today at lunch time.

 

Can anyone decipher what is happening based on the  screenshot since I can not capture logs?  Is there another way to get logs?  Any help would be greatly appreciated!

Dan

The one thing you can do is to perform a file-system check on all your data disks.  (because it is referencing reiserfs in the stack trace)

 

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

You should also do a memory test if you have not recently.  Kernel panic's are often caused by bad or incorrectly configured memory. (could be wrong clock speed, timing, or voltage)

 

Joe L.

When I went home for lunch and discovered the crash - I did run a memtest and left it running - so I will check on that tonight.  I built this box in Feb 2009 and have had very few issues until the last couple of months - so I assume if I had and timing clock speed or voltage issues I would have been having issues much sooner than this...unless the memory went bad...I'll let you know what memtest shows.  How long should I let it run?  For reference the motherboard/hardware is as follows:supermicro c2see with two 1GB ddr3 corsair xms3 memory sticks and a Celeron E1200 processor.

 

I'll read up on the file system check.

 

Thanks,

Dan

 

The symptoms of my recent problem appears to be the same. However, I hadn't logged in as root on my console to get the message that you showed displayed. I'm also going to do a memtest to see what's up. In my case the motherboard and RAM is new, but again, it was working for a couple of weeks before this problem showed up.

I ran memtest for 3.5 hours and it completed 5 passes with no errors.  Did I run this long enough?

 

I ran memtest for 3.5 hours and it completed 5 passes with no errors.  Did I run this long enough?

 

I think so.

Sorry it took so long to post back - life got in the way of me trying Joe's suggestion.  When I ran reiserfsck - I did find an error on one drive and it suggested the rebuild tree option.  I ran this and it looks like my issue is resolved.  I guess only time will tell but everything has been fine for 3 days.

 

Thanks for the help!

 

Dan