July 21, 201213 yr Author Also, I am wondering if it would make sense to do a file system check on the other drives I have, one by one, and then try to rebuild the data drive (with the 3TB)? Or would the fact that the error is probably on the parity drive make that pointless?
July 21, 201213 yr First check the file system on the 3TB. Maybe you will get lucky.. And will be able to rebuild on the drive from parity. Second, if that doesn't work... If you can fix the file system on the 2TB drive, some, most, or all the files will be recovered. Edit: we're thinking the same. Sent from my SAMSUNG-SGH-I897 using Tapatalk 2
July 21, 201213 yr Ok. Got the key, rebooted, etc. Now - I can't seem to run a fs check on a disk outside of the array! Not sure what to do here. It is easy. Use the comand ls -l /dev/disks/by-id to get the device name of the device outside of the array Let's say it is /dev/sdf The file system is on the FIRST partition, so to access it you append a "1"to the base name of the device. reiserfsck --check /dev/sdf1
July 21, 201213 yr Thanks Joe. I usually use my search skills to find answers. Tough to do from the phone. Sent from my SAMSUNG-SGH-I897 using Tapatalk 2
July 21, 201213 yr Author Ok. I attempted to check the fs on the 3tb, and got an error message - I'd meant to copy it down but didn't, unfortunately. However, the data rebuild onto that drive only got to I believe the 5GB mark, so I don't think there is much on it. I now have the 2TB being checked. So - if I can repair errors, I guess I'd just try to add it to the array again? If not... well, I will look into maybe copying data off it somehow and re-initializing the array. I have a ways to go before the check is done, though. Will post when complete. Joe, Thank you - I did search for this, but hadn't found the answer yet! "ls -l /dev/disks/by-id" gives me "no such file or directory", for some reason. I'd actually tried "reiserfsck --check /dev/sdf" , but left the "1" off One thing I have also been searching for is: which number would the parity drive be? sda1? I ask because I didn't want to run a filesystem check on it.
July 21, 201213 yr Author Tried to run a chk on the 3TB - "your filesystem is not big enough to contain the filesystem of (732566632) blocks as was specified in the found superblock. Failed to open the filesystem".
July 21, 201213 yr Joe, Thank you - I did search for this, but hadn't found the answer yet! "ls -l /dev/disks/by-id" gives me "no such file or directory", for some reason. I'd actually tried "reiserfsck --check /dev/sdf" , but left the "1" off One thing I have also been searching for is: which number would the parity drive be? sda1? I ask because I didn't want to run a filesystem check on it. Sorry. "disk", not "disks" (I mis-typed) ls -l /dev/disk/by-id and you MUST use the first partition (with the "1" added to the base name of the drive) Any correction action on the base name will not find the superblock (since it is not there) and if you attempt to then rebuild it, you'll corrupt the file-system that is on there. Joe L.
July 21, 201213 yr One thing I have also been searching for is: which number would the parity drive be? sda1? I ask because I didn't want to run a filesystem check on it. It is safe to run the command with --check. You may as well run it on all of the data disks. What you could do is remove the 3TB drive. Assign the 2TB to the slot and run the new config utility. This will set a new disk configuration, and invalidate parity. I don't believe the current parity is good anyways. Then, you should be able to run the file system check. This should work. Ok - but won't I lose the contents of that 2TB drive then? No. After setting New Config the drives indicators should all turn blue and parity will rebuild when the array is started.
July 22, 201213 yr Author Ok - I have checked the filesystem on all of the drives. The only errors I had were actually on the parity drive ("bad root block"). Oddly, the 3TB drive also passed the check, and I say "oddly" because I had only gotten to about the 5GB mark on it when the rebuild failed. The drive still says there is 1.2 TB free. I am planning on researching the reiser fs a bit - I seem to recall something about the journal being quite small, but containing all of the file info. So maybe the actual data isn't there, but the journal is? In any case, I have the 2TB back in place, and am running a parity rebuild on the array with that one in place. When it's complete, I will do a smart test on the parity drive to be sure it is ok, and then just add the 3TB to the array as an additional data drive.
July 22, 201213 yr Ok - I have checked the filesystem on all of the drives. The only errors I had were actually on the parity drive ("bad root block"). Oddly, the 3TB drive also passed the check, and I say "oddly" because I had only gotten to about the 5GB mark on it when the rebuild failed. The drive still says there is 1.2 TB free. I am planning on researching the reiser fs a bit - I seem to recall something about the journal being quite small, but containing all of the file info. So maybe the actual data isn't there, but the journal is? In any case, I have the 2TB back in place, and am running a parity rebuild on the array with that one in place. When it's complete, I will do a smart test on the parity drive to be sure it is ok, and then just add the 3TB to the array as an additional data drive. The parity drive NEVER has a file-system on it. There will never be a superblock found, as there is no file-system. If you attempt to put one on it (attempt to fix the superblock), it will cause the next parity check to fail (and be useless as a parity drive to protect the others in the array until a proper parity sync is again made.)
July 23, 201213 yr Author That's what I'd thought - just someone had said it wouldn't hurt to check the fs on the parity drive, so thought I would see what it did. At any rate, less than an hour left on the parity rebuild, so hopefully that will complete successfully, and I will be all set. Anyone have any thoughts as to why the 3TB drive was reporting 1.2 TB free (and no errors when I ran reiserfsck) when it had only gotten to the 5GB or so mark before failing the rebuild? I would have expected it to be mostly empty...
July 23, 201213 yr Something with the error message you got when attempting to rebuild onto the 3TB... I would run pre clear on that drive. Sent from my SAMSUNG-SGH-I897 using Tapatalk 2
July 24, 201213 yr Author Thanks. I just finished the preclear. Now (and I will open a new thread for this if you think I should), I stop the array, add the new drive, check the "Yes I want to do this" checkbox - and the page refreshes. As in, I can add/remove disks, etc - the selects are still active. I can't seem to actually start the array! ~Sean
July 24, 201213 yr Author mbryanr, I got an email that you had posted a reply - but I don't see it. Can you re-post? Thank you, Sean
July 24, 201213 yr It should attempt to format the disk..... Anything in the syslog? Sent from my SAMSUNG-SGH-I897 using Tapatalk 2
July 24, 201213 yr Author I'm attaching it... but I see this: Jul 23 22:07:25 Tower kernel: md: import disk6: [8,96] (sdg) WDC_WD30EZRX-00MMMB0_WD-WMAWZ0113519 size: 2930266532 Jul 23 22:07:25 Tower kernel: md: disk6 new disk The "format" button never appears. The page refreshes as though I hadn't added the disk. syslog.txt
July 24, 201213 yr Create a new thread... It should be formatting.. Sent from my SAMSUNG-SGH-I897 using Tapatalk 2
July 25, 201213 yr What version of pre clear did you use? Sent from my SAMSUNG-SGH-I897 using Tapatalk 2
July 25, 201213 yr Author I used the preclear.sh script - I just precleared again last night, thinking that perhaps since I had at some point tried to use the drive for a data rebuild it might need to be done again. No luck, though.
July 25, 201213 yr What version # though? The current version is 1.13. If you have an older version, please download the newest one. Older versions did not have the ability to properly handle larger disks. (larger than 2.2TB)
July 25, 201213 yr Author Oh, I'm not sure. I'll be sure it's the latest version when I get home. I hadn't realized that there was an issue with earlier versions.
July 25, 201213 yr Oh, I'm not sure. I'll be sure it's the latest version when I get home. I hadn't realized that there was an issue with earlier versions. The larger disks and unRAID's support of GPT partitions did not exist when the earlier versions were written. type: preclear_disk.sh -v to see the version.
July 26, 201213 yr Oh, I see. Well - I have just checked, and I have version 1.13 good. that is the latest version at this time.
Archived
This topic is now archived and is closed to further replies.