-
Bad Cache Disk in RAID1 cache
Here you go. Thanks! homeserver-diagnostics-20250704-1510.zip
-
joshdinsdale started following Bad Cache Disk in RAID1 cache
-
Bad Cache Disk in RAID1 cache
Hi All, first post go go easy. I've been experiencing some performance issues with a couple of docker containers (mostly plex, slow DB performance). After messing about checking the plex database and a few other things I've come to the conclusion one of my cache SSD's is on the way out and needs removing/replacing. I have two SSD's in raid1 mode, I dont have a replacement for the bad one yet (and im not sure when i will be able to get one), so for now i just want to get it out of the cache to hopefully improve the performance. After doing some digging I found i can convert the cache to single disk mode which seems like the best option, however im not sure of the best way to do this. If i do this with both disks in, how do i specify which one becomes the new 'single'cache disk? Is the better option to stop the array, pull the bad disk, start the array backup with the degraded cache and THEN do the single disk balance procedure? Any advice would be much appreciated.
-
[Support] ich777 - Application Dockers
I've actually just solved this. As per this page https://stackoverflow.com/questions/67459316/enabling-chromium-to-sync-with-google-account, you can add the specified oauth2 details to chromium. I did this by adding a new Variable in the docker settings called EXTRA_PARAMETERS and setting the value to --oauth2-client-id=77185425430.apps.googleusercontent.com --oauth2-client-secret=OTJgUOQcT7lO7GsGZq2G4IlT Not sure how long this workaround will last but will do me for now!
-
[Support] ich777 - Application Dockers
Can anyone assist in getting browser sync working in the chromium docker? It seems to have the default Deb API keys so assumed that would be enough, but when i sign in it goes through ok but doesnt start the sync process.
-
[Support] Octoprint docker template - Spants
I'm having issues getting octoprint to connect to my printer. Unraid picks it up as a ch340 and presents it as /dev/ttyUSB0 and with an id in the by-id folder. I've tried the normal pass through option and also running the docker in privileged mode but it won't connect. I've tried different USB cables and also plugged the printer into my laptop and it definitely works that way. Does anyone have any suggestions?
joshdinsdale
Members
-
Joined
-
Last visited