Moving media library to bigger HDD - eviltoast

[SOLVED] 12 TB disk finally arrived, I used clonezilla. Using advanced settings and -k1 (everything else left as default) made exact disk with more storage. I just replaced disks, powered on and everything is up and running! Ty all ❤️

Hello selfhosters,

I’m running home server DIY PC with *arr stack in docker containers and its working surprisingly well. The problem I have is not enough storage for my needs so I ordered a new HDD.

At the moment I have OS (Debian) and some (config) volumes on one SSD while media library is on another SSD. I’d like to move only media library from old to a new HDD and stop using the old one.

What is the best way to move all files (including hard links?) to a new drive? Can I just copy files with same folder structure and then modify my docker-compose.yaml to point to a new HDD? Is backup and restore of *arr apps necessary? Is there any way to grab all torrent files from qbittorrent (or another way of backup?

Folder structure I have now:

System SSD:

  • SSD1/config/sonarr
  • SSD1/config/radarr
  • SSD1/config/qbittorrent

Data SSD:

  • SSD2/data/media/tv
  • SSD2/data/media/movies
  • SSD2/data/torrent/tv
  • SSD2/data/torrent/movies

THX!

  • lemmyvore@feddit.nlEnglish
    7·
    1 year ago

    rsync -avxH will copy the files between drives.

    You can simply mount the new drive in the same place as the old one after the copy, that way you don’t have to change any paths.

    • rambos@lemm.eeOPEnglish
      0·
      1 year ago

      Ill look into rsync, thx.

      About not changing paths, does it apply to my case? This is how I defined docker volumes:

          volumes:
      - /home/config/radarr:/config
      - /srv/dev-disk-by-uuid-4cfcd2b7-507b-4e3e-abd3-7b9c87d8ce64/data2000/data:/data
      • lemmyvore@feddit.nlEnglish
        2·
        1 year ago

        Well considering you made the mount point so specific to the drive you might as well change it. 😊 In the future consider something named after the directory’s function rather than physical support, such as /srv/docker/radarr/data. That way you can swap drives at /srv/docker and keep everything the same.

  • Pacmanlives@lemmy.world
    English
    1·
    1 year ago

    Method I use is a RAID 5 replace all my disks with larger ones. Grow RAID, LVM and then XFS. Went from 4TB drives to 8TB, and now 24TB drives using this method for the past about decade now

    • rambos@lemm.eeOPEnglish
      1·
      1 year ago

      Setting up a RAID is something I want to do in the future, but need more drives for that. Maybe next Xmass 🙃

  • C_M@feddit.nlEnglish
    0·
    1 year ago

    I would clone the second disk to the new disk (with gparted for instance) an then resize the partion to fit the disk. This way it would be a simple disk swap without needing to do anything else.

    PS: I think simply copying the files will go wrong with the hard links.

    • rambos@lemm.eeOPEnglish
      0·
      1 year ago

      My data SSD is 2TB and my new HDD is 12TB. I guess cloning will make 2TB partition on new HDD and then I have to extend it to 12TB? Did I understand that correctly? Do I need to use live OS or can I do it on running Debian OS? Do I have to change paths in my docker-compose after that? Please check another comment how I defined volumes, there might be a better way.

  • Tippon@lemmy.dbzer0.comEnglish
    01·
    1 year ago

    The disks will have a different UUID, so will be seen as different devices. I can’t remember what you need to do, but I’m pretty sure that the *arrs have a guide for transferring to a new disk without the files being detected as new.