ryankenn

I did the full stop. But I don't know how to tell which instance of the files is the more current? I just deleted the cache System and it is seemingly working. Maybe I'll post a last log tomorrow to see if it all looks good. tower-diagnostics-20260205-0048.zip

How do I see these files? I made System Export ready so in Windows I now see that share and it has two files in it. Docker and something else, but are those instances the ones on the cache or the dupes. NVM I did find it. So clicking the view on the System share it shows the files are located on the Cache and Disk 1. Clicking the Disk 1 it gives me the option to delete. But are the versions on the cache complete? Or should I delete the cache versions then re-run the mover.

That's weird. I stopped both the Dockers and even though I have no VM's I stopped all anyways. I will try the Move again tonight.

I made the adjustments. The only concern is those shares now show as orange exclamations saying "some or all of the files are unprotected". I ran a Parity check and this morning still show the same. tower-diagnostics-20260203-1928.zip

The minimum free cache field is greyed out on the drive. If there some other setting I need to activate to make that field active?

So these three? I just don't know how this all works when their sizes show as way larger than my Cache drive.

Well its all done and running. I adjusted the cache/array settings for my three major shares as well as letting them spread over all 4 drives. I am running low on space which is what prompted me to first look at this but IDK if I should just start a new thread for questions on how to go about that part of my upgrade. tower-diagnostics-20260202-1913.zip

Will do thanks!

Wow I think that worked. Updating the plugin's allowed the thinking wave to finally cease. I then stopped the array and applied the update which finally successfully applied. So no I am on 7.2.3 and on reboot with Plex off and the array started I am seeing massive reads on the cache drive and reads/writes across the array. Fingers crossed this did it, thanks for all your help! About 3 hours and I have 600GB free and climbing on the cache so it looks to be fixed. Weirdly I guess the out of date plug ins which prevented the update also prevented the cache dump. Thanks for your help!

I have rebooted a couple of times. Mainly to see if turning off the autostart on the Plex docker would allow array to correct itself. Its the only Docker/VM or Plugin I have running on this, its specifically a Plex server so there is no real fluff, and I think is why its run so well so long. I will address those max/min values for the future. I am going to be upping my drives as I am nearing the end of my comfort level with space. As for the appdata and system shares, that is something I will take a look at. Does setting all the shares to live on the cache mean I need a much larger drive there? I have about 14TB of media and a 3TB cahce drive. I also don't know if I want to switch it now while the cache drive is having issues offloading.

Added that file. Shares are Movies, TV, 4K and Documents

I have had this server up for a long time, and rarely peek in as it just runs like a tank. Its used for file storage and as a Plex server. In the last few days new media moved onto the server was stuttering during playback. When I logged in I was greated with 10's of messages about the cache being full. Sure enough of the 3TB it has 2.88 sitting on it. Also I noted in the main screen the "thinking" wave is just going forever. I don't run any VM's and the only Docker is Plex. I set Plex to not auto restart and rebooted the tower. It came back up with Plex off and I manually selected to run the mover. As of now I have not seen any movement. I only have three shares and they are specified to live on the array not the cache. Nothing is being transferred in or out with Plex off. But I have the thinking wave non stop. Any ideas what is going on? I also pulled up the logs just now and I see that when I execute the move, in the same second the log shows it completed. I can see my scheduled hourly moves try to happen. tower-diagnostics-20260131-1040.zip

This has happened again. Frankly I have no idea how I got it back up and running but the battery in my backup must be failing. On restart, Plex is unhealthy and unusable. I feel like last time I removed the app and reinstalled and that fixed it but there must be something else. So frustrating this Docker just can't see to restart itself anymore. I never had this issue previously. Seems like config is looking at an Empty Preferences XML. I have two folders that look very similar, one is PlexMediaServer and one is Plex-Media-Server. Both inside the library have the same setup, and empty Preference XML files. I feel like I changed a path or deleted something last time to get this to work. Thoughts?

I had my server go down tonight (hard down) as the power was out and I wasn't home so the battery backup ran out of juice. On restart because everything was off I updated Unraid to 6.12.1, and updated the Plex docker while I was at it. Now I cannot access Plex from anything. In the console, when I click the icon, normally the top option is WebUI and it lauches the app on my laptop, no it just says >_ console and lauches a blank window with a number sign. No devices can access the server. In the tower is says started, but at this point it say uptime is 55 mins (unhealthy). I don't know if it has to do some work first before its accessible, I do have over 7TB in the folders it accesses. But I am pretty certain in the past it just came up almost instantly and was usable right away. I know the files are there as I can see the folders through remote desktop and play the files. Any tips are welcome, thanks. **Aside**, in the past I just rebooted the server and it would work. This time it asked for a USER/Pass. When I accessed it from my laptop I had to set a password to get the GUI up, default was root and I had to set a password. I am not sure I ever had that before, don't know if its just a function of this latest update or not. dhcplog.txt docker.txt syslog.txt Docker Log Plex.txt

You are my hero.

Maybe I was just misreading. I had thought that USB drives would show in this version of Unraid, but I installed Unassigned Devices and I do see the two of them sitting there. Hopefully this means I can preclear them through this Docking Station.

I was hoping to use this docking station I already had: https://www.amazon.ca/dp/B019DNBU7G/ref=sspa_dk_hqp_detail_aax_0?smid=A1ZAFAL1WND4H&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUExNE9CQTkyRkU5TVlXJmVuY3J5cHRlZElkPUEwNDAwNTg4MTdJRzYxSkRMWTlXTSZlbmNyeXB0ZWRBZElkPUEwNTIwMzYyOUozNUpETEw5N0pQJndpZGdldE5hbWU9c3BfaHFwX3NoYXJlZCZhY3Rpb249Y2xpY2tSZWRpcmVjdCZkb05vdExvZ0NsaWNrPXRydWU&th=1 I want to preclear 4 drives I plan on putting into a new box I'm building along with the 3 in my existing small server. I put the first drive in the TARGET slot of the enclosure and its plugged in and on. I cannot see the drive anywhere in Unraid. During the process I also installed the BinHex preclear Docker to get ready and futzing with it using the -l function it does show the USB Docking Station as the only option to preclear because its not part of the array, so the box does know the docking station is attached and working, but it doesn't show the physical drive I have plugged into the station. Are dual slot stations like this just not suitable for preclearing drives? Or is there something I have to refresh in Unraid to get the unassigned drive to show? **During typing I also tried adding a 1TB drive I had around. In the screenshot you can see where I first only showed one USB Dock drive, now I do show two so I am assuming the preclear program does actually see the drives but can't translate the serial numbers to me? I have to know the SDF is Bay one and SDG is Bay two. Can I preclear the drives from this stage even though they don't show in the Unraid OS I am running Unraid 6.7.2.