Selfhosted

40479 readers

474 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

Proper procedure for migrating servarr services from JABOD to zfs (self.selfhosted)

submitted 8 months ago by snekerpimp to c/selfhosted

2 comments fedilink hide all child comments

Setting up my server as a newbie some years ago, I did not have the ability to purchase more then one 8TB hard drive. Outgrew that rather quick and now I have two additional 16TB drives, in a Just A Bunch Of Disk configuration, mounted to different /mnt mount points. I know this is not ideal, but lacking the ability to expand further or buy new drives for a new zfs pool and transfer, I don't have much of a choice but to wipe the drives, set up a zfs raid and re-download everything.

I have everything set up in docker-compose files, so I'm pretty sure I just need to keep those and the folders where the configs are, modify the compose files with the new file structure and... I am unsure where to go from here. Will everything start being grabbed as soon as my dockers spin up? Is there an additional procedure I need to do to make sure I don't wipe my existing config files with blank empty ones? Is there an easier way of doing this?

all 3 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 8 months ago (1 children)

Yes, as long as you update the volume mounts, the change will be invisible.

But you should have a backup anyway.

[–] snekerpimp 1 points 8 months ago

Already have a 3-2-1 backup of the config folders and compose files, and I have backups of the VM if anything goes south. Making sure my logic train was on the right path.