rsbonini

Ok, so I did the disk reassignment with parity valid, that went smoothly. I then ran the parity check without writing corrections to parity. The check completed this afternoon, reporting 545 errors but also reports "Parity is valid". Should I run a correcting check? The other drives weren't involved in any of the drive dying, unfinished clear, data rebuild fiasco so shouldn't they be trusted more? A parity check was conducted two days prior with 0 errors.

Did the first step as you suggested, reassigned the new empty drive as disk4 and rebuilt disk4. Appears that the rebuild completed with no issue. The system reports that parity is valid, with the last time it was checked being the same time it completed the rebuild of disk4. This means that disk5 was properly cleared and I can now do New Config > Unassign disk5 with valid party checked, correct?

Ok, that makes perfect sense. I think the drive was cleared, but can't be 100% certain.

Diagnostics attached. Thank you for the quick response. I tried to run the clear_an_array_drive script, but I think it bailed or didn't complete because disk5 now shows: "Unmountable: Wrong or no file system". cygnus-diagnostics-20230203-2050.zip

Background: I recently added a new 8TB drive as disk5 to my array. There was no data on it, completely empty. While reorganizing some stuff last night I unplugged the server and the UPS died within moments (likely a bad battery) cutting power to the server. When I rebooted the machine disk4 came up disabled and there was some clicking from the server. Drive is dead. I didn't have a spare drive on hand and so thought I'd shrink disk5 out of the array (since it was empty), move the drive to the disk4 position and rebuild. I did the first part of the shrink process, up to clearing disk5. Now I'm worried that when I setup a new conifg the data currently being emulated from disk4 will be wiped. Does the following seem like a correct course of action: 1. pull the empty drive from the disk5 position; 2. put it into the disk4 position and rebuild; and 3. modify the config so that the disk5 position is empty? Unraid version: 6.11.5 2 parity disks

@PeteAsking Thanks so much!

I've installed the Unifi-Controller docker using the default option, which in this case is version 6.1.71. Unfortunately Unifi has declared my APs EOL and so any further updates to the Controller past 6.1.71 will break my ability to configure them. I needed something newer than 5.9 to get my USW-Aggregation working otherwise i would have left it at that. My questions are as follows: 1. Will leaving the docker repository poined at: linuxserver/unifi-controller run any risk of it updating itself past the current version? If so is there a way to disable this? 2. Is there a way to save a complete copy of the current docker build (not just the configuration) to restore from if needed in future and the "latest" branch has moved forward? Thanks in advance for any advice!