Skaronator

Thanks for the quick response! So, is it correct to say that Unraid can spin down all disks to save power, and when accessing data, it will only spin up the specific disk containing the requested data? Additionally, does a single file always exist on a single disk (excluding the parity disk), ensuring that only one disk is needed for reading a larger file? Does the same behavior apply when writing data as well? If so, I might switch to Unraid. I've tried achieving something similar with Snapraid and MergeFS, but MergeFS stopped functioning once the disks spun down.

I read somewhere that Unraid only spins up the specific disk where the data is stored on, thus saving on energy cost but how does Unraid know which disk to spin up? Or is that fact only true when writing data?