jjross

Thank you for the help.

Thank you, as I said, I read the docs but I also know that sometimes they are out of date. Also, the section on "parity swap" specifically calls out: "Before starting, ensure the data drive you want to replace is disabled. If the drive has failed (shows a red indicator), it is already disabled. If the drive is healthy but you want to replace it, unassign the drive and start the array once without it to force Unraid to mark it as disabled." I do not want to replace a data disk. I want to take the old parity disk and add it to the pool. This doesn't seem to be called out in the instructions. It does, however, say this: "This procedure is only needed for replacing data drives in an Unraid array with a disk larger than the current parity drive. If you only need to upgrade your parity drive, simply remove the old parity drive, add the new one, and start the array. Parity will rebuild automatically" So I'm guessing I just need to pull the parity drive and add a new one? Is there a way to copy the existing parity data so I have some redundancy while parity is rebuilding? I do see mention of a "copy" button when I am replacing a failed data disk but nothing when adding a new disk.

Yes, but how?

Hopefully my title is self explanatory but ultimately I want to expand the capacity of my system but the drive I am adding is larger than my parity so I need to replace the parity and then I want to add the old parity disk to my array. The documentation's procedure only seems to reference replacing a failed data disk. I don't want to do that, none of my disks are failed, I just want to replace parity and expand the size of the array. Would I still follow the same procedure? Swap the new disk into parity and assign the old parity disk as a data disk (but not a failed data disk)?

Oh! I see that now. Thank you.

OK, so retention doesn't work on custom paths? Sounds good, I'll need to move my flash backup to the default location. Any chance we could add a tooltip or something to the plugin to make that clear?

I was following the docs to remove a drive from my system without having to rebuild parity and it looks like there are a few corrections that need to be made. Is there a way to do a pull request or something to have the docs updated? Specifically, under the "Alternate Procedure steps for Linux proficient users" it states that the command to run the clear is as follows: umount /mnt/diskX dd bs=1M if=/dev/zero of=/dev/mdX status=progress But as the /dev/ paths have changed the command is actually: umount /mnt/diskX dd bs=1M if=/dev/zero of=/dev/mdXp1 status=progress Also, the documentation links to a forum post which has the "clear an array drive" script but the script will not run on the latest versions without modifications (not the least of which is updating the dd command as above). There's a post in the forum thread that appears to have the relevant updates in it (here) but it would be preferred if the docs linked to a fully functional script. Honestly, ideally the system would have a built in procedure for removing a drive without rebuilding parity but if this is the supported, and documented, procedure for now then it should at least be accurate.

I made these changes to the script and it appears to work as expected. A little frustrating that the official documentation references this script and it doesn't actually work.

Am I doing something wrong? I'm having a situation wherein I am backing up my flash to a custom folder but it doesn't look like the script is including the flash in it's retention check. I noticed today because I am moving the flash backups to a cloud provider and I keep going over my space. When I checked the flash backup folder it had backups going back to early last year even though my retention is to keep backups for two weeks. Is there another retention setting for the flash backup or, perhaps, this is because I am copying the flash to another folder? Any suggestions as to what I might need to change? I can see that the retention is being check according to the logs and it's certainly cleaning up the appdata backup.

Oh! Thank you so much.

Silly question but how would I add a webui link to the folder? I can't seem to find a place to specify this in the GUI.

Thank you so much for this post. I had this exact same issue on UNRAID 6.12.10 For me, the script wouldn't run, seemingly because the names in /dev/ had changes so I manually ran dd and cleared things out. Then I couldn't stop the array but I followed your steps and everything seems to be working perfectly now. **EDIT** Whoops, I wasn't using "clear_array_for_shrink", I was trying to use "clear_an_array_drive" but had the same symptoms

I'm really sorry, I can't remember. It's certainly possible I didn't not create the folder as I typically assume it will be created automatically.

Ultimately it was a very easy fix but I find it interesting it hit two of us. Overall the container is working great!

Just thought I would note that I had the same issue. I kept getting the "Unable to find EVS commandline utilities" error. In the end I also fixed it by forcing a reinstall of the iDrive package with ./idrive -C