Hey guys,

 

I've bought a new harddrive to replace my parity disk.

The old parity drive is now used to replace my old disk6, which was damaged (/has failed).

Like the manual said, i did the following:

 

I stopped the array

I powered down the server

I replaced the old parity disk with a new one (same size, but faster)

I replaced the failed disk with my old parity disk

I switched the server on and started the array

The system is now copying the parity information to the new parity disk.

 

But when i now (2 hours later) log on to the server, all disks are blinking.

Parity disk and disk 6 are blue blinking, the rest is green blinking.

So all the disks are spun down, but it says it is still copying. In fact it now is at 27%, and this number increases.

 

And now my question:

How is it possible that the array is still copying files from disk6 (=old parity) to the new parity drive, when ALL the drives are spun down??

Is it actually still copying? Or should somehow manage to safely power down the server, turn automatic spin down off, and then do the procedure all over again?

 

Here's a copy of my syslog. At the very end you can see that it spinns down the disks over and over again?

 

Anyone?

syslog.txt

It looks like it is still copying.  I'd say let it run.  It will take probably 10 hours or so for that phase of the process.

 

It also looks like the spin-down timers are still active on the two involved drives.  (and that looks like a oversight lime-tech can address in a future release)  The extra attempts to spin down the active drives should not affect the copy process.

Allright,

 

I'll let it run.

 

Thanx!!