Parity Check after Disk failed and remove?

[cracksilver]

Hi there 

 

I had a disk with reallocated sectors and removed it with this https://wiki.unraid.net/Shrink_array --> The "Remove Drives Then Rebuild Parity" Method because it was on a extern USB Disk Array. This was probably the problem. Actually I do not need the disk anymore.

 

After did a new config I started the array. Everything works and shares are reachable like before. 

 

Now my question. Do I have parity check manually? There ist still the "not installed disk" visible in main tab. See below...

Also i attached the tower-diagnostics-20181210-0302.zip

 

Thank you for any help.

cracksilver

 

 

[JorgeB]

You didn't remove the disk correctly, it should not be listed under array devices any longer, repeat the procedure.

[cracksilver]

Hi Johnnie

 

Thx for reply.

 

I did The "Remove Drives Then Rebuild Parity" Method twice.

The failed disk is now under UD visible. How can I do it again now?

 

Do I have to check parity manually?

 

cracksilver

[JorgeB]

Yes, but you didn't do it right, you kept the emulated disk.

[cracksilver]

and what should I do know in your oppinion?

[JorgeB]

You should repeat the procedure and follow the instructions carefully, if the emulated disk is still present you're not doing a new config.

[cracksilver]

What about this procedure:

 

- stopp array

- put another cleaned HD as disk 3

- do NO new config

- start array

 

[JorgeB]

That works, but it's not what you were trying to do, you need to decide if you want to keep this 3 or not.

[cracksilver]

Actually I dont want to keep 3 disks in the array. The reason is simple. My HP Microserver Gen8 has space for about 4 Disks. The third disk is connected via USB and is mounted in a extern Disk Case with another 3 Disks. Im unhappy with USB in the array, because the USB Controller does the job not like I want. For example, after a reboot the Disk case is down and has to start up manually by press the button. This is unlucky for the array wants actually to start with all disks available for it needs.

 

But if I put it back and reach a correct running array I should have another try to remove the disk 3 correct.

 

 

[JorgeB]

You don't need to put it back to remove, just do a new config without it.

[cracksilver]

Thats wat I did last night. After remove disk 3 I did a new config and that's I tried twice...

[JorgeB]

For the last time, you did it wrong, if you had done a new config emulated disk3 wouldn't be there anymore.

[cracksilver]

Ok. And what I've done wrong asking myself...

I shouldn't be that complicated

 

Whats the correct workflow then?

 

- stopp array

- do NO new config

- start array

[trurl]

The correct workflow is exactly as listed in that wiki you linked. Where are you getting this from?

25 minutes ago, cracksilver said:

do NO new config

There is nothing like that in that wiki, and if you aren't doing New Config then that explains exactly the results you are getting.

 

Please go back to the wiki and quote what you perceive to be the relevant steps in your next post.

[trurl]

If you did New Config before then you must have left out the very most important part of step 7:

Quote

 Unassign the drive(s) you are removing.

 

[cracksilver]

sorry I copied from the thread befor...

 

Now I did it again. Now I did it right!

The problem was that I have just clicked on "done" not on "appl". Probably it was to late last night

 

after stopping array:

 

and after did an new config (with clicking on "apply") and started the array it looks perfect:

 

thank you for your patience with me..

have a good day/night, wherever you are located

cracksilver

 

[cracksilver]

Everything works like a charme again ,-)

UnRAID really rocks and has a lovely community. Thank you.