I wrote this as a follow up to a previous post, but since I got no response I'll try with a new post. I have disk that is causing problems, so I wanted to remove it from the array. I found https://wiki.unraid.net/Shrink_array and started to follow the steps in "The "Clear Drive Then Remove Drive" Method". After 48+ hours finally the "clear an array drive" script finished, and I wanted to continue with the next step. However, at this point I find that the disk has been mounted again and a parity check is running. According to the main tab, the fs size is 16 GB, and 1.21 GB is used. A ls -al at /mnt/disk1 shows no files though. How did this happen, and more importantly, how do I continue?

eru-diagnostics-20200518-1836.zip

Edited May 20, 20206 yr by rockard

If the disk is mounting it can't be clear, that script is known to be extra slow with latest releases, if you still want to do that you can do it manually.

I still don't understand how it came to be that it was mounted again, and where the 16 GB fs came from, but I just gave up and ignored it and proceeded with the next steps. Looks good so far.

If you remove a drive that isn't clear, your parity will be wrong until you do a correcting parity check.

 

You would have been better off to just remove the drive and rebuild parity.