Yikes; I must be rocking it old-school. Is it no longer preclear_disk.sh?

 

While we're on the subject...when I put the wd30efrx in the array (to preclear), it's gonna take the array off-line; because the parity is no longer the biggest drive. I can do without it for tonight/tomorrow...while I run 2 preclears; but is there a way around this (having the array off-line that is). [solved]

 

OK...is it alright to re-install unMenu and screen, now that I'm 5.0-rc11?

 

Also...5.0 says "If you are adding a new disk or replacing a disabled disk, try Parity-Swap" (love 5.0 already!). "Parity-Swap"...is that actually a thing now?

 

Thanks

^^^ This has me stumped. As stated above...I accidentally selected my new drive for a drive slot; selected. I never brought the array online.

 

Then I realized I needed to un-select the new disk, for the array to start; and I'm trying to run a preclear_disk.sh. It keeps saying "that disk is part of the array and won't run preclear".

 

It's unselected; I even unseated, rebooted, and re-seated. Still says it's part of the array. PooP!

^^^ This has me stumped. As stated above...I accidentally selected my new drive for a drive slot; selected. I never brought the array online.

 

Then I realized I needed to un-select the new disk, for the array to start; and I'm trying to run a preclear_disk.sh. It keeps saying "that disk is part of the array and won't run preclear".

 

It's unselected; I even unseated, rebooted, and re-seated. Still says it's part of the array. PooP!

 

Stop the array and un-assign the drive.

Does the main screen say it's missing and still list the s/n of the new drive? If yes, try starting and stopping the array with the drive not assigned.

Thanks for chiming-in guys. I've started a dedicated thread for this (http://lime-technology.com/forum/index.php?topic=26550.0 where there's a screen shot of my main); but let me elaborate.

 

This is a 3T drive, and it's meant to replace the current parity; so I'm trying to preclear first. I put it in a hot-swap slot, and accidentally assigned it. I did go to start the array, but it wouldn't...because the new 3T drive was bigger than the parity.

 

No harm/no foul I thought; I unassigned, realizing I was just supposed to peak at the sdx assignment anyway. Array started up fine right after...in other words, it's not looking for this drive, or considers it missing. Yet...I still get the error when I try to pre-clear.

 

I've stopped the array, un-seated the drive from the server; re-booted, re-started the array...re-seated the drive, and tried preclear then. Same result. 

Thanks for chiming-in guys. I've started a dedicated thread for this (http://lime-technology.com/forum/index.php?topic=26550.0 where there's a screen shot of my main); but let me elaborate.

 

This is a 3T drive, and it's meant to replace the current parity; so I'm trying to preclear first. I put it in a hot-swap slot, and accidentally assigned it. I did go to start the array, but it wouldn't...because the new 3T drive was bigger than the parity.

 

No harm/no foul I thought; I unassigned, realizing I was just supposed to peak at the sdx assignment anyway. Array started up fine right after...in other words, it's not looking for this drive, or considers it missing. Yet...I still get the error when I try to pre-clear.

 

I've stopped the array, un-seated the drive from the server; re-booted, re-started the array...re-seated the drive, and tried preclear then. Same result. 

 

OK guys; I've solved that sub-issue (see dedicated thread for solution; but it was pretty simple. Just didn't want to screw-up my array, with the wrong move).

 

I'm in the home-stretch, big-picture wise. I figure I'm looking at close to this business week, to preclear this 3T drive twice. After that, I want to swap my parity. It's been a while: is that as simple as un-assign old parity, swap drives; re-assign new parity, and run parity check?

 

Then it'll be 2 preclears on the 2T parity being replaced, and put that sucker in the array.

It's been a while: is that as simple as un-assign old parity, swap drives; re-assign new parity, and run parity check?

 

Not quite.  Run a fresh parity check on the old set up first, to ensure that each of your data drives can be completely read without error.  You will need to prove that you can do that before you have to do it for real to build the new parity. 

It's been a while: is that as simple as un-assign old parity, swap drives; re-assign new parity, and run parity check?

 

Not quite.  Run a fresh parity check on the old set up first, to ensure that each of your data drives can be completely read without error.  You will need to prove that you can do that before you have to do it for real to build the new parity.

 

OK, thanks. So...parity-check with old parity, un-assign; new drive, assign to parity...re-run fresh parity check?

 

Simple enough.

It's been a while: is that as simple as un-assign old parity, swap drives; re-assign new parity, and run parity check?

 

Not quite.  Run a fresh parity check on the old set up first, to ensure that each of your data drives can be completely read without error.  You will need to prove that you can do that before you have to do it for real to build the new parity.

 

OK, thanks. So...parity-check with old parity, un-assign; new drive, assign to parity...re-run fresh parity check?

 

Simple enough.

 

Parity-check with old parity, un-assign; new drive, assign to parity, allow parity to regenerate on new drive (not sure if you have to force that or if it just happens), then re-run fresh parity check.

^^^ Great; thanks.

 

Now I'm just waiting on the preclear(s). Going surprisingly "quick"; 70% after 5 hours, of a 3T drive (oh wait...it's been a while; there's like a second part, that takes much longer...right?  )

First part - read everything.

Second part - write all zeroes.

Third part - write "precleared" signature.

Fourth part - read everything again.

 

Steps 1, 2 and 4 all take roughly the same time.  Step 3 is very quick.