March 4, 201016 yr Author This is odd almost a day and not even a hint of what these errors could be from.
March 4, 201016 yr In the past, when we've seen kernel messages dealing with the file-system, the file-system was corrupted and needed repair. See here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems
March 4, 201016 yr So did it fix itself? A corrupt file system will never fix itself. It takes manual steps as described in the wiki. In the interim, have you run a memory test on your memory? It is the most frequent cause of unRAID kernel crashes. Joe L.
March 5, 201016 yr Author I did a parity ck last night and all was well with it. This morning after I seen the check went good, I wanted to reboot the array. When I pressed stop the array seemed to lock up. I give it a little bit but it was unresponsive, couldnt even telnet in or get a display at the console. Killed power. When it came back up it showed "starting" for the longest time maybe like 15 minutes. 4 drives came up showing unformated but one by one they came online.
Archived
This topic is now archived and is closed to further replies.