gerhard911 Posted April 18, 2012 Share Posted April 18, 2012 My unraid server has crashed several times with this error. From the last console screen I can see the error message in the title repeated multiple times. Process can be hdparm or sh. Does this message indicate a Linux bug? Possibly a hardware issue? After each failure the server reboots and unraid starts the array without problems but a parity check auto starts (and runs for @ 16 hrs with a 3TB parity drive + 12 data drives). Server will generally run for a couple of days without issue. No discernible pattern to the crashes. Latest one I was writing to the array but it has happened overnight with no activity as well. There are also some other diagnostics that would be very time consuming to write down and possibly of little use without a full syslog. It appears that there is no syslog retained on the flash drive. Is there a way to force the syslog to write to flash? If so, do I need to be concerned about filling up the flash drive (2GB)? Thanks in advance for any assistance. edit to add I am running unRAID 5.0-beta13 Link to comment
dgaschk Posted April 18, 2012 Share Posted April 18, 2012 Capture a syslog. See here: http://lime-technology.com/forum/index.php?topic=9880.0 Link to comment
gerhard911 Posted April 18, 2012 Author Share Posted April 18, 2012 Thank you! Hopefully the telnet console will do the trick. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.