I just changed my parity wd20 ears with a 3tb one, everything ok

Parity is synced.

Then i took my old wd20 ears to add it to the array for data but i saw it was jumpered.. I thought it couldnt harm cause it was not in the array so i removed jumper and added it

I rebooted..

Stopped array and assigned it

Then it told me it had to be cleared so i said ok.. But then the unraid page/server comes unresponsive, i dunno why..

 

I rebooted and everything was ok but the drive isnt added..

 

What to do? I need some help here

 

I wish i hadnt removed the jumper

Should i put the jumper back?

Unless pre-clear is used, unRAID will clear the drive. It should take about 8 hours for a 2T drive. The server will be unavailable until it completes.

Unless pre-clear is used, unRAID will clear the drive. It should take about 8 hours for a 2T drive. The server will be unavailable until it completes.

 

So its normal that the webgui is unresponsive?

Yes. This is the reason pre-clear was first developed.

Skank (I have the hardest time typing that name without laughing)-

 

If you want your array to remain available, you can use preclear to clear the drive.  That way when you add it to the array it does not need to be cleared.

Afternnight running, its still not responsive, you sure this is normal?

Its also not sdX but hdc

 

Edit: running 10 hours now..

Yes! Its responsive again !

 

Just formatted it, and everything ok now

 

Is it normal that it is "hdc" instead of "sdX"?

all others are sdX

except for the cache which is "hdd"

Is it normal that it is "hdc" instead of "sdX"?

all others are sdX

except for the cache which is "hdd"

That generally indicates either a 40pin IDE style drive, or settings in the BIOS are set so as to make your SATA controller emulate an IDE connection for compatibility with older software. It's not an ideal situation, in that it might cause slowdowns, but changing it may have unpredictable results, so proceed with caution.

Is it normal that it is "hdc" instead of "sdX"?

all others are sdX

except for the cache which is "hdd"

That generally indicates either a 40pin IDE style drive, or settings in the BIOS are set so as to make your SATA controller emulate an IDE connection for compatibility with older software. It's not an ideal situation, in that it might cause slowdowns, but changing it may have unpredictable results, so proceed with caution.

 

so what should i do?

its a wd green 3tb ezrx

so what should i do?

its a wd green 3tb ezrx

Personally, if the speed is ok, and everything is working, I'd leave it alone. I'm all in favor of not messing with a working system. If it bugs you enough to tinker, look in your BIOS for SATA or disk controller mode settings, and post back with the options you have and what it's currently set on.

so what should i do?

its a wd green 3tb ezrx

Personally, if the speed is ok, and everything is working, I'd leave it alone. I'm all in favor of not messing with a working system. If it bugs you enough to tinker, look in your BIOS for SATA or disk controller mode settings, and post back with the options you have and what it's currently set on.

 

Any drive with a hd prefix will be slower than sd. SATA should be set for AHCI-only in BIOS. Disable IDE combined mode or legacy support. It goes by different names. The drive content will not be effected by this change.

so what should i do?

its a wd green 3tb ezrx

Personally, if the speed is ok, and everything is working, I'd leave it alone. I'm all in favor of not messing with a working system. If it bugs you enough to tinker, look in your BIOS for SATA or disk controller mode settings, and post back with the options you have and what it's currently set on.

 

Any drive with a hd prefix will be slower than sd. SATA should be set for AHCI-only in BIOS. Disable IDE combined mode or legacy support. It goes by different names. The drive content will not be effected by this change.

 

Thx

It seems my sata were all (6x) set to IDE

i changed it all to AHCI,

booted ok, and on my unraid all are sdX now

thx