May 12, 201016 yr i just had my first crash and according to what i could briefly see on the monitor it was some sort of stack trace error. the system was not responsive via network, telnet or keyboard/mouse.. i had to power it off then back on and it is currently checking the parity. what should i do so that i don't loose data or have this happen again? thanks James syslog-2010-05-12.txt
May 13, 201016 yr A crash is frequently memory related. So, a memory test is in order. Then, it might be a file-system with some corruption that caused the crash. You should check the file-systems on each of your data disks as described in the wiki here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Other than that, all you can do is take a picture of the screen after a crash. It might contain clues. Joe L.
May 13, 201016 yr Author A crash is frequently memory related. So, a memory test is in order. Then, it might be a file-system with some corruption that caused the crash. You should check the file-systems on each of your data disks as described in the wiki here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Other than that, all you can do is take a picture of the screen after a crash. It might contain clues. Joe L. thanks i will try those tests, i am assuming that i should do them after the parity is finished... thanks james
May 13, 201016 yr A crash is frequently memory related. So, a memory test is in order. Then, it might be a file-system with some corruption that caused the crash. You should check the file-systems on each of your data disks as described in the wiki here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Other than that, all you can do is take a picture of the screen after a crash. It might contain clues. Joe L. thanks i will try those tests, i am assuming that i should do them after the parity is finished... thanks james It is best if you wait.
May 14, 201016 yr Author the parity finished and found no errors so i stopped the array and shut it down to run the memory test. so far it has been running for 16 hours and no errors. i think the memory is probably good, next i will probably run the file/disk check this weekend.. thanks
Archived
This topic is now archived and is closed to further replies.