January 3, 201610 yr So I have been running my array sans a parity drive for some time. I know... idiot move. Parity drive died a while back and I just never replaced it although I had a disk waiting for that purpose. Well I finally had a data drive crap out. Not much on it but movies and tv shows not a huge loss. So I was trying to get it fully removed from the array so that I could bring the array back online. I had stopped it to try to get it to detect the drive. I am running v5.0 and I went to utils and clicked New Config. I went back to the drives. Assigned them back to disk1 through disk8. Where as those disks were previously disk2 through disk9. Assigned a parity drive which I precleared. Brought the array online. Unfortunately it showed disk1 as unformatted. I cancelled parity and brought the array back offline. I put them back on disk2 through disk9 brought it back online without a parity drive. Unraid still showed the disk as unformatted. I ran reiserfsck --check /dev/md2 it said it could not find a superblock So I ran reiserfsck --rebuild-sb /dev/md2 and selected 3.6.x After that I reran the check. Here is the results: root@UNRAID:/boot# reiserfsck --check /dev/md2 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Sat Jan 2 17:41:01 2016 ########### Replaying journal: No transactions found Zero bit found in on-disk bitmap after the last valid bit. Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) At this point I dont know what to do. I would love to try to get the data off this disk but I don't what to do now. I did read something about pre 5.0 I think I upgraded this from a 4.7 install so I dont know if it did something special. I also dont really know if at the time of my original setup if MBR was aligned or unaligned. Any suggestions? Appreciate the help. Thanks!
January 3, 201610 yr It's not completely clear what your situation is, so I'll start with some questions. It sounds like one drive went bad, was it the one that now appears unformatted? (By the way, this is much safer in unRAID v6, wish you had upgraded.) Just to be sure, the drive that was assigned to Disk 1 and appeared unformatted is the same drive you re-assigned to Disk 2 and tried to use reiserfsck on? Is it possible that this 'unformatted' drive is actually the bad drive from before? Had you tried to recover the data on that bad drive? When you used --rebuild-sb, did you use the exact instructions and parameters from the Check Disk File systems wiki page?
January 3, 201610 yr Author Hey RobJ, Unfortunately I just realized the additional bonehead move I made. So what happened is I had 9 disks in the array. Disk1 failed. I installed a new disk into the array and precleared it. I cleared the config and then added the drives back into the array. I was trying to install the new precleared disk as the parity drive. But I installed it as data drive and installed one of the existing data drives to the parity drive. I brought the array online with the data drive assigned as the parity drive which started the parity sync. I did cancel the parity sync but not right away. Is there anyway I may be able to salvage some of the data off that old good data drive which I inadvertently attached as the parity drive and started the parity sync on? At this point I have no idea what might have been on it. Hoping someone might be able to help. Thanks! It's not completely clear what your situation is, so I'll start with some questions. It sounds like one drive went bad, was it the one that now appears unformatted? (By the way, this is much safer in unRAID v6, wish you had upgraded.) Just to be sure, the drive that was assigned to Disk 1 and appeared unformatted is the same drive you re-assigned to Disk 2 and tried to use reiserfsck on? Is it possible that this 'unformatted' drive is actually the bad drive from before? Had you tried to recover the data on that bad drive? When you used --rebuild-sb, did you use the exact instructions and parameters from the Check Disk File systems wiki page?
January 3, 201610 yr ... I was trying to install the new precleared disk as the parity drive. But I installed it as data drive and installed one of the existing data drives to the parity drive. I brought the array online with the data drive assigned as the parity drive which started the parity sync. I did cancel the parity sync but not right away. Is there anyway I may be able to salvage some of the data off that old data drive?... Same wiki as already given. Check Disk File systems
January 3, 201610 yr Author I read it and now that I am running my commands on the correct disk this is what I am seeing: root@UNRAID:/# reiserfsck --check /dev/md8 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md8 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Sat Jan 2 23:06:34 2016 ########### Replaying journal: No transactions found Zero bit found in on-disk bitmap after the last valid bit. Checking internal tree.. \block 372076015: The level of the node (59364) is not correct, (4) expected the problem in the internal node occured (372076015), whole subtree is skippedf inished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 1 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Sat Jan 2 23:08:29 2016 ########### I just did not want to make any more mistakes. Since I am now running rebuild-tree I assume this is going to be a mess when it is done. There was close to 3TB of data on this disk. Thanks for the help. I guess I should have been more thorough when I was fixing my system ... I was trying to install the new precleared disk as the parity drive. But I installed it as data drive and installed one of the existing data drives to the parity drive. I brought the array online with the data drive assigned as the parity drive which started the parity sync. I did cancel the parity sync but not right away. Is there anyway I may be able to salvage some of the data off that old data drive?... Same wiki as already given. Check Disk File systems
January 3, 201610 yr Author Well my repair finished. I lost about 1.5 TB of data. Now have the arduous process to look at the files in the lost+found directory. Learned my lesson. Building parity now and will be looking at offsite backup for important files. Thanks!
Archived
This topic is now archived and is closed to further replies.