write error?

[smandable]

Hmm... no corruptions found on the 2 TB...

[smandable]

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".

[Joe L.]

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.

[dgaschk]

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.

[smandable]

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.

[Joe L.]

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.)

[smandable]

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...

[mbryanr]

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

[smandable]

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

[smandable]

mbryanr,

I got an email that you had posted a reply - but I don't see it. Can you re-post?

Thank you,

Sean

[mbryanr]

It should attempt to format the disk..... Anything in the syslog?

Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

[smandable]

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.

[mbryanr]

Create a new thread... It should be formatting..

Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

[mbryanr]

What version of pre clear did you use?

Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

[smandable]

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.