Strahdvonzar
Members
-
Joined
-
Last visited
-
Even though my Dockers are working without any issues , i get "Docker Service failed to start" when i go to the Docker page and apparently nothing is displayed. I have attached my diagnostics. I have not gone to the settings for disabling - reenabling docker in case they dont come back. mainserver-diagnostics-20250519-2150.zip
-
What is the best practice for developers (it also applies to many more use cases) using unraid in terms of caching and array storage? Currently i code on Cache and have rsync scripts for syncing to the array. That way , i avoid the strain on the array disks due to the often access and i also keep my code backed up "safe" in the array through rsync. Is there a "native" way to achieve the same result without relying on rsync custom scripts or should i just skip the "cache" all together and use the Array for my purposes and just accept the increase wear on my disks? Generally i have various use cases in my setup that require often access to data through the day , with speed not actually being a factor. Is the wear on the array disks so taxing that staying in a "Cache -> rsync -> Array" setup the best way to go?
-
Restarting the Machine fixed it.
-
Unraid Version : 6.12.10 (Unraid OS Plus) I have an External USB HDD ( Samsung D3 Station ) for a couple of years on Unraid without issues. At some point , a few days ago , while i was on vacations it became inaccessible. Movies/TV Series are stored there and the "*arrs" started complaining. When i got back i simply removed the power and put it back on and everything seemed to work as expected , but after a couple of days the same issue appeared again. This time i removed it from the Unraid and attached it on a windows desktop. The Desktop had no issues accessing the HDD and its contents. I went on and run a diagnose and fix from the windows tools and everything worked fine. Got it back again on the unraid but the same issue exists. I also changed a few USB Ports just in case , but it did not solve the issue. In "lsusb" the Disk is displayed. In "Unassigned Disk Devices" the disk is displayed. Navigating to the disk though fails.
