Adrian

Yea that's what I'm hoping. I'm currently running an extended test on one of the drives. Probably take another 6-8 hours to complete. When that's done, I'll try the other drive. And yup, I disabled the spindown. ok, so if the extended test passes for both, just try to start the array and then upload new diagnostics. Got it.

mediaserver-diagnostics-20220718-1723.zip FYI, this is unfortunately captured after I rebooted the server.

So something happened and 2 drives are marked red. I think one is actually dead and the other is fine. I'm running an extended SmartTest on one of them and then the other. I have dual parity. What's the process to "recover" from the two red drives if 1 or both are bad? Do I simply replace the bad drive(s) and rebuild? I've never done this with more than 1 drive.

I was trying to see if I could add a new Video path to Plex for my home videos and I guess I was poking around not really knowing what I was doing. I tried using " Add another Path, Port, Variable, Label or Device" and after I hit Add\Apply, a window popped up (the reconfiguring window) and after I closed it, now the Plex docker is missing. I'm thinking maybe some error with what I tried to add. Any idea how I can get it back without losing any of the data\history ?

Just got back in town, thank you! this worked.

So what's the default username/password to use for a new install? And where exactly is that documented, just curious to see why I had trouble finding it.

Worked perfectly, no issues. Thanks!

So if this is the disk I'm clearing, I'd be running the following? dd bs=1M if=/dev/zero of=/dev/md16 status=progress

Great, thank you!

Any thoughts on what the deal is with doing the drive clear method and unraid getting stuck when I go to stop it? I have another drive I want to remove. I already moved all the files off to another drive.

Twice I've tried this method and twice it hangs on step 9. When the clearing is complete, stop the array How else can I easily remove a drive that no longer has any files on it? before the steps it mentions the following: One quick way to clean a drive is reformat it! To format an array drive, you stop the array and then on the Main page click on the link for the drive and change the file system type to something different than it currently is, then restart the array. You will then be presented with an option to format it. Formatting a drive removes all of its data, and the parity drive is updated accordingly, so the data cannot be easily recovered. Could I do this instead of running the script and then continue from step 9? Because whatever this script is doing, Unraid doesn't like it and puts it in a state where it gets stuck stopping the array and I can't even reboot/shut it down cleanly. Removing an empty drive shouldn't be this difficult.

I was trying to understand more of what each step is doing. At this point, the drive is unmounted (by the script), but still assigned. How does this prepare unraid to allow me to unassign it at step 13 without causing unraid to complain about a missing disk? If I unassign it without running this, it complains that it's missing, but if I run this, it doesn't. This is the one I'm probably most unclear on that I want to understand better. This one I understand, since the drive was zeroes out, it doesn't affect parity. Telling it that parity is valid (which it is) is just a confirmation telling it that you know you removed a drive that doesn't affect parity so it can accept the parity drive as it is?

Can someone explain what exactly is going on in the final steps for clearing a drive. Specifically 11-14 https://wiki.lime-technology.com/Shrink_array The "Clear Drive Then Remove Drive" Method 10. Go to Tools then New Config 11. Click on the Retain current configuration box (says None at first), click on the box for All, then click on close 12. Click on the box for Yes I want to do this, then click Apply then Done 13. Return to the Main page, and check all assignments. If any are missing, correct them. Unassign the drive(s) you are removing. Double check all of the assignments, especially the parity drive(s)! 14. Click the check box for Parity is already valid, make sure it is checked! 15. Start the array! Click the Start button then the Proceed button (on the warning popup that will pop up) 16. Parity should still be valid, however it's highly recommended to do a Parity Check

When you added the container (assuming that you're using 6.1.9 as its easier to do this than under 6.2+) you inadvertently changed the port. Just hit the icon under the docker tab and edit the container. The docker screen for this container should look something like this (virgin install of Needo's sickrage for you to test FCP with it, with bogus pathnames however) ok, yea I'm on 6.2+ and I didn't see how I could even edit it so I wasn't sure how I might have changed it in the past, but if the previous version allowed editing, then I can see how I may have changed it by accident as it was probably my first docker app and I wasn't familiar with how all that work. I went ahead and just removed it and added it again and it looks good now. Thanks, Adrian

Odds on you changed the Container port of the app when you wanted to only change the Host port. Pretty much there is zero reason to ever change the container port, and doing so will generally break the app, hence the error. How would have I done that? And how do I fix that?

I just installed this today and had it run its scan. It's reporting the following error: Docker Application SickRage, Container Port 8081 not found or changed on installed application The docker image that I have installed is needo/sickrage.

ok, I guess excluding the directories that I rarely access would help. I'll give that a shot. hehe...well if you could convince me that it would be fast enough to be worth it maybe I could get inspired

Is there anything I can do to make it quit faster? Whenever I'm working on my server and it requires multiple shutdowns, it's a real hassle to shutdown as the server is waiting on the drives to unmount. Using -q doesn't do anything, it still keeps going. I have to kill multiple Find processes manually before it finally finishes. Thanks, Adrian Unraid 4.7