Do a new config with an intentionally "missing" disk?

[bubbaQ]

I have a 7-disk array that got a power surge which 1) killed a disk, and 2) corrupted the flash drive.

 

The system was idle, so I have a high degree of confidence that parity is good (or at least good enough to use to rebuild the fried disk).

 

I have a printout of all the drive assignments, so I can do a new-config.  But how can I do a new config and trust parity, with a missing disk?  I was thinking that I could install a spare disk for configuration purposes, save the config, then unplug it before starting the array, but that seems like a kludge.

 

Alternatively, is there a way to individually "trust" data disks?  The controller was fried too, and with the new controller the drives have different names in the unRAID UI, so although I have reassigned the right disks to the right slots, the system thinks they are the "wrong" disk.  If I can tell unRAID to "trust" what it thinks are wrong disks in slots 1,2,3, and leave slot 7 as "missing" I can rebuild #7.

 

 

Suggestions?

[JonathanM]

I think the set invalidslot option of mdcmd is still a viable method of doing what you want, but I would seek guidance from Tom before diddling around with important data. If you have a test array to play with, I would do that first.

[JorgeB]

This should work, if the spare is the same size of the bad disk:

 

http://lime-technology.com/forum/index.php?topic=47900.msg459246#msg459246

 

http://lime-technology.com/forum/index.php?topic=47486.msg454776#msg454776

[JorgeB]

Also, it's in one of the links but you have to be on v6.1.5 or above.