March 29, 201412 yr Hi All, Thanks in advance for any help you can give. I believe I am running version 4.7 and have syslog attached. ( I hope) Server became unresponsive in XBMC and could not telnet in to server so.......... I did a hard reset. Restarted array and now it sees all my hard drives as new drives. I was not having any trouble before this and have never had any issues with any drives on the monthly parity checks. Please help, I'm kinda freakin' out! Thanks again for any help P.S. syslog file was 280 kb so I included a .zip file syslog-20140328-180628.zip
March 29, 201412 yr I gotta nuttin. Sorry, I never used 4.7 BUT, if you did a hard reset, and now your configuration isn't working, what *I'd* do is pop the flash into a PC and use chkdsk on it. (Disk Utility on a Mac.) On v.5, hard resets often result in directory corruption on the flash. OR...if you have a BACKUP of your flash, try that.
March 29, 201412 yr Author Sorry, I should have added that tidbit of info, I did run chkdsk on it and it came back fine. Thanks for the reply!
March 29, 201412 yr Sorry, I should have added that tidbit of info, I did run chkdsk on it and it came back fine. Thanks for the reply! Do you have a backup of your flash drive. If you do you could try coping your config directory from your backup. You problem sound to me like a super.dat file corruption since that is where the drive assignments are maintained - as far as I know anyway.
March 29, 201412 yr Author Sorry, I should have added that tidbit of info, I did run chkdsk on it and it came back fine. Thanks for the reply! Do you have a backup of your flash drive. If you do you could try coping your config directory from your backup. You problem sound to me like a super.dat file corruption since that is where the drive assignments are maintained - as far as I know anyway. I am completely sure I made a backup, however I am now completely sure I cannot find it.........
March 29, 201412 yr Mar 28 17:38:59 UnRaid kernel: md: invalid superblock magic Suggest emailing Tom for assistance.
March 29, 201412 yr Assign all the drives as data drives and start the array. One drive will be unformatted. The unformatted drive is the parity drive. If you have a cache drive identify it now. Stop the array and enter "initconfig" on the command line. Assign the parity drive (and cache drive) and the other disks as data disks. Start the array and parity will rebuild.
March 29, 201412 yr Author Assign all the drives as data drives and start the array. One drive will be unformatted. The unformatted drive is the parity drive. If you have a cache drive identify it now. Stop the array and enter "initconfig" on the command line. Assign the parity drive (and cache drive) and the other disks as data disks. Start the array and parity will rebuild. Thanks dgaschk, If I assign them as data drives, then I do not have to worry about them being reformatted? I guess that is my biggest concern, that I lose all my data. Did you happen to look at the log? I was curious as to what the issue was. Thanks again dgaschk! I will try it when I get home from work Don
Archived
This topic is now archived and is closed to further replies.