Replace cache drive unraid

Replace cache drive unraid DEFAULT

How To Add Cache Drive(s) To Unraid

Notes based on this excellent Space Invader One video

  • : houses our docker’s container configuration content
  • : houses our VM’s data
  • : houses our docker’s and our VM’s

On Array And Cache ()

  • any other shares you don’t often write to
  • : Only stored on array.
  • : Keep on the cache but also on the array.
  • : Only stored on the cache, never moved to the array.
  • : Will store on the cache, if the cache is full will move to the array. If you do not have a cache drive, will store on the array, and if a cache becomes available the data will move to the cache.
  1. switch all the shares that you wish to store on the cache drive to , before installing the drive(s). Its possible this option is unavailable right now. if that’s true, just skip this step and we’ll cover it again later.
  2. shut down the server
  3. physically install your cache drive(s)
  4. boot up the server
  5. stop the array
  6. under “Pool Devices” for each device, click a new slot and select a device from the drop down
  7. start the array
  8. under “array operations” check off the “Yes, I want to do this” under “Format” which will format all unmountable disks, which should be our N new cache drives
    1. Be sure to double check that the disks listed under “Unmountable disk present” are the expected cache drive(s)
  9. If you didn’t do step one, (as it was unavailable), set the shares you want to set to be on the cache now. See the above section for my advice on which shares should leverage the cache.
  10. Stop Docker and the VM service
  11. Click “Move” which will move all the shares intended to be on the cache, on to the cache. We stop Docker and the VM service, as there are many files that cannot be moved when in use. (Settings -> Docker -> Enable Docker set to “no”)

If you installed more than one drive, by default they’ll be in RAID 1, giving you a redundancy incase one disk dies. This is my preferred method instead of increasing performance with striping but losing redundancy

Depending on the size of your shares, this can take a while. It took about 3.5 hours for my ~80 GB of data to be moved to the cache.


From Unraid | Docs

Jump to: navigation, search

This page describes how to replace your Cache drive without losing anything

Replacing or upgrading your Cache drive - for unRAID v6.2 and above

Note: these procedures assume that there are Docker or VM related files on the Cache disk. If you are absolutely sure there aren't, the Docker or VM steps can be skipped.
Note: this procedure can be performed with unRAID versions prior to 6.2, but you won't have the Use cache disk: Prefer option. So instead of doing steps 11 and 12, you will have to manually move all files back to the new Cache drive.
  1. Prepare your new Cache drive first. If it's not an SSD, you may want to Preclear it
  2. All plugins, Dockers, and VM's that use the Cache disk in any way must be stopped
    In order to avoid interference, we are about to disable a number of things. You may want to make notes of what you change, so you can reverse it afterward.
    Go to Settings -> Scheduler and change the Mover schedule so it won't run for the next few days (once this procedure is done, you'll change it back)
    Stop all VM's, then go to Settings -> VM Manager and set Enable VMs to No, then click Apply
    Stop all Docker containers, then go to Settings -> Docker and set Enable Docker to No, then click Apply
    If it's installed, make sure the Community Applications Appdata Backup plugin is not scheduled to run during this procedure
  3. Click on Shares and set all shares present on your Cache disk to Use cache disk: Yes. This will cause the Mover to move all shares OFF the Cache drive!
  4. Check that there is enough free space on the array and invoke the Mover by clicking Move Now on the Main page
  5. When the Mover finishes, check that your Cache drive is empty. Any files in the root will not be moved as they are not part of any share. You can ignore any empty folders and Recycle Bin folders, and temporary and trash files, but if there is anything else that you want saved, now is the time! Copy it to a safe place, such as on an array drive.
  6. Stop the array and unassign the old Cache drive
  7. If the new Cache drive is not yet installed in your server, power down and install the new drive, then power back up. Note: you can save yourself a little time by first setting array auto-start temporarily to No (Disk Settings -> Enable auto start).
  8. Assign the new Cache drive
  9. Make sure the file system for the Cache drive is set as you wish (click on the Cache drive and check File system type)
  10. Start the array, and let unRAID format it
  11. Change all shares that you want to exist only on your Cache drive to Use cache disk: Prefer. This will cause the Mover to move these shares back to the Cache drive.
  12. On the Main page, click Move Now
  13. When the Mover finishes, check that the Cache drive is no longer empty, and has all the right shares on it.
  14. Now you can change all shares that you want to be ONLY on your Cache drive to Use cache disk: Only.
  15. Re-enable anything in Settings you disabled before, such as Dockers, VMs, the Mover schedule, and array auto-start
  16. And finally, you can restart any Docker containers and VMs. You are done!
Credit for above goes to John_M and

Replacing or upgrading your Cache drive - for unRAID v6.1 and below

Written for unRAID v5, not fully updated for v6 but should work OK
  1. Preclear the new cache drive
  2. Disable the Mover schedule. Stop all plugins, Dockers, and VM's that run on or use the Cache disk in any way (unsure, but you may also need to temporarily disable Dockers)
  3. Log into your server as root
  4. Run Midnight Commander ('mc' <enter>)
  5. Navigate to your current Cache drive, should be at /mnt/cache
  6. Select all of your Cache files and folders, using the <Insert> button. (.sickbeard, .sabnzbd, etc...)
  7. Make a new backup folder on a specific drive on your array, such as /mnt/disk7/cachebackup
  8. Copy all of the Cache drive files and folders to the folder you just created
  9. Stop the array
  10. Go to the Main tab in the web GUI, and use the drop down for the Cache drive, at the bottom, to reassign the cache drive(s)
  11. Start the array
  12. The new cache drive will show up as unformatted, so go to the bottom of the Main tab, and format the drive. If you Precleared the drive, this should only take a few seconds
  13. With the array running, log into your server as root and run Midnight Commander again
  14. Copy all of the files and folders from your Cache backup (e.g. /mnt/disk7/cachebackup) back to /mnt/cache
  15. Stop the array (will stop all of your additional programs)
  16. Start the array. Bob's your uncle
  17. You may now re-enable the Mover schedule, and restart any plugins, Dockers, or VM's that run on or use the Cache disk
Note: Midnight Commander is used above, you could instead use rsync at the command line. (e.g. rsync -avXH /mnt/cache /mnt/disk7/cachebackup)

More information

Original forum link here
Original cache drive description from Tom here
  1. Modern laundry chute
  2. 10x10 round rugs
  3. Coolpad note 5 cover
  4. Replacement seat belt button
  5. Clearest am radio

[Guide] Move Your Docker Image and Appdata to an Unassigned Drive (DEPRECATED)

Unraid 6.9 Update

With the release of unraid 6.9 comes the ability to define multiple cache pools, which eliminates the need for moving your Docker data to an unassigned device. If you’ve already followed this guide and your Docker data is on an unassigned device, there’s no need to change things back. However, if you’re reading this guide for the first time, and you’re using unraid 6.9 or higher, I would recommend not using this guide and instead creating a separate cache pool for your Docker and VM data.


By default, unraid puts the Docker vDisk image and appdata on your the array, with no caching enabled. This is usually fine for one or two containers, but as you add more containers to the mix, your disk IO can increase and responsiveness for the containers can go down as a result. To fix this, you could set the shares for your Docker image and appdata to always be on the cache drive. This will work, but then you’re using up a chunk of the cache space constantly, and if you ingest a lot of new files frequently, you can run into a disk IO problem again. A better solution is to move the files to an unassigned drive, preferably an SSD. Keeping your Docker files on a dedicated drive can increase responsiveness for any container, but it can be especially helpful if you run containers that work with databases. This article will walk you through the steps needed to move your Docker installation to an unassigned drive.

This is an advanced topic that uses the terminal to move files, mount disk images, and make manual edits to configuration files. I have tested these commands on my own system successfully, but I am not liable if you break your installation. Please read through this entire guide thoroughly before attempting the process. If you have any questions, please post them here or on the discord and do not proceed until you have been given an answer.

Read Me First

This process assumes you have the array STARTED, and the disk you want to copy the image to is mounted as an unassigned device. If this isn’t the case, :stop_sign: STOP HERE :stop_sign: and ask for assistance.

In several of the steps below, you will need to enter commands in the terminal. Commands to be entered will be placed in . There will be some places in these code blocks where you need replace a placeholder with a specific folder or value from your system. Look for words with angled braces around them, like and replace everything, including the angled braces, with the proper value. Be careful not to replace or remove any characters outside the braces.

TL;DR Version:

IF your Docker vDisk image and appdata are both in their default locations ( and respectively), you can use the script below to take a shortcut.

  1. Back up your appdata folder. Use the CA Backup/Restore Appdata plugin.
  2. Stop the Docker engine (Settings > Docker > Enable Docker = No > Apply)
  3. Go to the Main tab and grab the name of the disk you want to use. Even if you already know the name, you need to leave the Docker settings screen for the script to work, so just go to the Main tab.
  4. Copy the commands below into your favorite text editor
  5. Search for and replace all instances of with the drive name from step 2
  6. Open the terminal window. Copy and paste the commands from your text editor into the terminal one at a time.
    • Please note, if you don’t have the CA Backup/Restore Appdata plugin installed, you can skip the second to the last command, the one right above
  7. Start the Docker engine (Settings > Docker > Enable Docker = Yes > Apply)
  8. Check the Docker tab to verify your containers are all listed, and then start them



Rita nodded. I took off my sweatpants along with my underpants. My heart was pounding like crazy, and a lump rolled up to my throat.

Drive unraid cache replace

The word "Bitch" from the mouth of the Sportsman sounded very dismissive. As if he was referring to trash or empty space. His gaze slid over me: Take off your trinkets.

The Perfect Home Server Build! 18TB, 10Gbit LAN, Quiet \u0026 Compact

I ran my palm over the reared body covered with a cloth of panties. He twitched at my touch. I haven't played with him for a long time.

Now discussing:

I will say that there was a lot of liquid, but I coped. The weirdness didn't end there. After that, they simultaneously began to piss on me in the literal sense. I thought I would choke on their urine.

824 825 826 827 828