rossibg

Um... yea. I just used the word move as in the verb not meaning to reference the "mover" function in unraid.

Moved the remaining files manually which seems to have resolved my issue. Docker containers seem to work fine and the array does spin down which is what I was after. I'll add a second nvme to the pool for redundancy in the next few weeks and further configure for day to day things to go onto the pool and then get moved to the array for back up.

Any sugetions on how to have those files moved? manually deleting them seems like a bad idea.

OK, I moved across the appdata, domains, ISOs and system folders/shares using the instructions in the unraid manual but the drives still don't spin down. also for some reason there are a few folders which did not get removed from my array for some reason. Any ideas? ivanoviunraid-diagnostics-20240908-2013.zip

Here's the config of my Unraid setup. ivanoviunraid-diagnostics-20240906-1717.zip

So I've had an Unraid box running for a couple of months and have set up shares, VMs (home assistant) and Docker containers (qtorrent, plex, etc) with everything working quite well. The server is based on an HP EliteDesk 800 G4 with two 18TB HDDs and an nvme (with a spare slot for another nvme) for a cache drive. My use case for this box is primarily for long term storage with the occasional media/video download and streaming. This in my mind would mean that I should be able to reconfigure the system so that it allows the HDDs to spin down as the data hosted on them is only accessed occasionally. How should I structure the storage (two HDDs and an nvme) so that all of my docker containers and VMs run from the nvme(cache) and only wake up the array drives when I want to access the long term storage or stream some media? Is this even possible? I've recently enabled HDD spin down but the drives never spin down so my config is clearly not correct.