I have an installation of unraid with an array of 1 HDD and an SSD. Unfortunately the operating system is on the HDD and the disk is never put to sleep. Is it possible to move the operating system to the other disk?

hal2024-diagnostics-20240611-1106.zip

Edited June 11, 20242 yr by gh0stless
add diagnostic data

Attach Diagnostics to your NEXT post in this thread. 

I did.

58 minutes ago, gh0stless said:

Unfortunately the operating system is on the HDD and the disk is never put to sleep. Is it possible to move the operating system to the other disk?

Not quite sure I understand this?    If by OS you mean Unraid it is not on either drive as at boot it loads from the flash drive into RAM and runs from there.

 

if you are simply looking for reasons why disk2 will not spin down that will be because you have all the docker related shares located there.

 

 

 

But there are some folders that are created by the system.

Those are the docker/VM related shares.

 

It would be better if your SSD were assigned as cache. If you had done so, those shares would have been created on cache automatically.

 

And SSDs in the array cannot be trimmed.

 

You don't currently have parity. Do you plan to add it?

15 minutes ago, gh0stless said:

 

But there are some folders that are created by the system.

but there is nothing installed there that is part of the Unraid OS itself?   Those shares are used to support features like docker containers and VMs and you can control where they are located.   You currently do not have them set to go to the largest available drive.

 

I think you can get what you want by doing the following:

• Disabling the docker and VM services under Settings.
• use Dynamix File.Manager plugin to move the ‘system’, ‘appdata’ and ‘domains’ folders from disk2 to disk1 (the SSD).   You could also do this for the ‘isos’ folder but that may well be fine on the HDD.
• change the settings for the above shares so that they only include disk1 so that Unraid will not put any new files elsewhere.
• re-enable the docker and/or VM services

BTW:  most people keep SSD and HDD separate with SSDs in a pool rather than the main array.   The reason being that the moment you add a parity drive and that is a HDD you slow down write speeds to the SSD.

 

2 minutes ago, trurl said:

Those are the docker/VM related shares.

 

It would be better if your SSD were assigned as cache. If you hade done so, those shares would have been created on cache automatically.

 

And SSDs in the array cannot be trimmed.

 

You don't currently have parity. Do you plan to add it?

That sounds good.
I have a small thin client as hardware and I'm planning a microPCIe adapter with 4 additional hard drives. But I first have to build a case, etc. I'm mainly concerned about noise. So far, the SSD is shown as sleeping and the HDD is always running.

19 minutes ago, itimpi said:

BTW: Die meisten Leute halten SSD und HDD mit SSDs in einem Pool und nicht im Hauptfeld. Der Grund dafür ist, dass Sie in dem Moment, in dem Sie ein Paritäts-Laufwerk hinzufügen, und das ist eine Festplatte, die Sie die Schreibgeschwindigkeiten auf die SSD verlangsamen.

 

Thanks, I think I now have a better idea of how UNRAID organizes storage. Is it possible to dismantle an array later, for example if the SSD is empty?

Edited June 11, 20242 yr by gh0stless

3 minutes ago, gh0stless said:

Thanks, I think I now have a better idea of how UNRAID organizes storage. Is it possible to dismantle an array later, for example if the SSD is empty?

yes you could split it later, but it might make sense to do it now by:

• use Tools->New Config to allow you to reset the array
• return to the Main tab and (optionally)move the HDD to be disk1.   Note that it is also possible to leave disk1 unassigned
• assign the SSD to be a pool.
• start the array to commit the change.    Existing data on the drives will be retained.

if you are using docker containers you might want to install the appdata backup plugin to make periodic scheduled backups of the appdata share from the pool to the main array.

One more question:
I now have the SSD as a pool disk and cache and the array consists of the HDD.
Can I convert the array into a pool disk? (To keep appdata and containers on it) Later I want to add an array with another 4 new disks.

You could but would need to re-format all the disks.

On 6/17/2024 at 2:31 AM, gh0stless said:

One more question:
I now have the SSD as a pool disk and cache and the array consists of the HDD.
Can I convert the array into a pool disk? (To keep appdata and containers on it) Later I want to add an array with another 4 new disks.

Not sure I understand. What you probably need to do is move those folders to cache from the array.

 

Post new diagnostics for more detailed advice.