Hi,

I’m running unRAIDServer-5.0.5-i386 with 15 drives plus parity.

One of my drives red balled (disk6) & I removed it with no problems. The array emulated the missing drive & life continued while I waited for the replacement disk which arrived today. I powered the array down to connect the new drive for preclearing but when I restarted it looked like I had a corrupted USB stick. Eventually I restored the most recent unRAID backup onto the stick and restarted. Unfortunately the backup predated my latest parity drive assignment. I’d moved the original 2TB parity drive to disk10 and added a new 3TB parity drive.

When I assign the drives to their correct slots I get red balls & Wrong indications for parity & drive10 and the array won’t start. Obviously the missing drive6 is no longer emulated.

Is there a way to force the array to accept my parity & drive10 assignments and restart trusting that parity is valid?

 

I’d appreciate any advice on how to proceed.

 

BTW disk15 always adds 30C to its reported temperature.

Select Utils->New Config and then assign the drives as desired. Make sure the parity drive is chosen correctly.

Dgachk thanks for the advice  . I acted before you posted. Here’s what I did:

 

1 Opened telnet session to root.

 

2 Entered ‘mdcmd set invalidslot 99’ – this cleared all my disk assignments.

 

3 Manually assigned my disks (including the one that had redballed) to the appropriate slots.

 

4 Started the array with the ‘parity is correct’ box checked.

 

5 Stopped the array & removed the disk that had redballed.

 

6 Started the array & checked that disk 6 was being emulated.

 

7 Compared 50 GB of system files with their disk 6 backups to check emulation.

 

8 Stopped array & replaced disk 6 with the pre-cleared new drive.

 

9 Started array / rebuild.

 

 

I incorrectly typed ‘mdcmd set invalidslot 99’ in step 2 I actually entered 'initconfig'

 

2 Entered ‘mdcmd set invalidslot 99’ – this cleared all my disk assignments.