July 30, 200916 yr Hi, I can't seem to get this fixed. Has anybody else run across this problem? I boot my server and I can't access any shares. The console shows all my disks as NEW DISK in red. I run frequent parity checks and my last one checked out good. Maybe less than 5 days old. Here is my system log file -- I appreciate any suggestions or solutions. Thanks very much.
July 30, 200916 yr Hi, I can't seem to get this fixed. Has anybody else run across this problem? I boot my server and I can't access any shares. The console shows all my disks as NEW DISK in red. I run frequent parity checks and my last one checked out good. Maybe less than 5 days old. Here is my system log file -- I appreciate any suggestions or solutions. Thanks very much. The lines in the syslog that are describing the root cause are: Jul 24 23:17:54 Tower kernel: md: invalid superblock checksum Jul 24 23:17:54 Tower kernel: md: initializing superblock The config/super.dat file on your flash drive is corrupted in some way and has a bad checksum. Easiest way to recover, assuming your flash drive can be written to is to use the "trust my parity" process as described in the wiki: http://lime-technology.com/wiki/index.php/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily Joe L.
July 31, 200916 yr Author Yes, that was the problem. Thanks Joe L. The system came back on line and the parity check completed without errors. All my shares and data seem to be intact. Thanks very much for the help and quick response. (I had been messing around with it for over a week trying to bring it back to life.) Much appreciated.
Archived
This topic is now archived and is closed to further replies.