Comment on Move UnRaid from metal to Proxmox

• just_another_person@lemmy.world ⁨6⁩ ⁨months⁩ ago

  You’re thinking about this wrong way though. Why are trying to abstract the thing that keeps your disks working properly? What’s your gain here?

  source

  • jjlinux@lemmy.ml ⁨6⁩ ⁨months⁩ ago

    Oh, ok. Mainly 2 things:

    1. Manage all my containers and VMs over ProxMox instead of inside UnRaid directly, effectively leaving UnRaid to be just manage storage only.
    2. This, from my understanding, will in turn allow me to play with container options other than docker (docker is awesome, I know, but it also has limitations), effectively opening new roads of knowledge to me. UnRaid doesn’t even support Kubernetes or LXC.

    While I’m aware that I can even compose dockers in UnRaid if there’s no UnRaid docker template available, it’s not the most user friendly way for managing those containers, in my opinion.

    Another reason is that I’m always trying to learn new things, and from my limited experience with ProxMox (I’ve only been playing with it for about a month or so on an old rig), ProxMox is incredibly easy and powerful when it comes to container and VM deployment. The management options seem to be infinite.

    Your point is very solid, which is why I’m contemplating segregating UnRaid and ProxMox into 2 separate rigs as opposed to virtualizing UnRaid.

    These are hard decisions. Keep just 1 rig and spend way more time and probably migraines configuring this, or just build a new rig for ProxMox and migrate all my containers and VMs to it, which is faster, but will come at a higher monetary price, including power consumption.

    source

    • just_another_person@lemmy.world ⁨6⁩ ⁨months⁩ ago

      Just get a separate host for whatever the VM stuff you want. You won’t need to worry about messing anything related to storage up, AND you’ll be able to mess with all the networking stuff without impacting your NAS.

      If you’re just trying to run some simple services, just get a $300 Ryzen minipc. Plenty powerful for what it sounds like you’re looking to do.

      source

      • jjlinux@lemmy.ml ⁨6⁩ ⁨months⁩ ago

        Yeah. I told my wife what I wanted to do, and she actually would rather have me spend the money than risk spending too much time if and when I break something. I’m thinking a minispc Ryzen 9 or a Ryzen 7 venus, set it up with a 4TB NVMe. That should do the trick. It’s a bit over 300 bucks, but will be a bit more future proof. 64GB DDR5, and fire it away.

        source
• pyrosis@lemmy.world ⁨6⁩ ⁨months⁩ ago

  Have you considered the increase in disk io and that hypervisor prefer to be in control of all hardware? Including disks…

  If you are set on proxmox consider that it can directly share your data itself. This could be made easy with cockpit and the zfs plugin. The plugin helps if you have existing pools. Both can be installed directly on proxmox and present a separate web UI with different options for system management.

  The safe things here to use are the filesharing and pool management operations. Basically use the proxmox webui for everything it permits first.

  Either way have fun.

  source

  • glasgitarrewelt@feddit.de ⁨6⁩ ⁨months⁩ ago

    That sounds like a great idea.

    At the moment I am using Openmediavault as a VM within proxmox - I pass my HDDs through to this VM. Openmediavault let’s me do all the stuff I want to: Share folders via SSH, NFS and raid-management.

    Do you know if I can do the same with proxmox directly? Do you maybe have a link where this way is described in detail?

    source
  • jjlinux@lemmy.ml ⁨6⁩ ⁨months⁩ ago

    I actually never considered this. And if I’m understanding you correctly, this would render using UnRaid unnecessary.

    This is great info. I’m going to fit my current ProxMox test rig with a few disks I have (old small disks I have replaced over the years that still work) and test this option first. This might make this easier.

    If this works out, I can still keep the server I set up off-site to mirror my storage, right? Even if that is still UnRaid? I need more coffee.

    source

    • pyrosis@lemmy.world ⁨6⁩ ⁨months⁩ ago

      Yup you can. In fact you likely should and will probably find yourself improving disk io dramatically compared to your original thoughts doing this. It’s better in my opinion to let the hypervisor manage disks operations. That means in my opinion it should also share files with smb and NFS especially if you are already considering nas type operations.

      Since proxmox supports zfs out of the box along with btrfs and even XFS you have a myriad of options. You combine that with cockpit and you have a nice management interface.

      I went the zfs route because I’m familiar with it and I appreciate it’s native sharing options built into the filesystem. It’s cool to have the option to create a new dataset off the pool and directly pass it into a new lxc container.

      source

      • jjlinux@lemmy.ml ⁨6⁩ ⁨months⁩ ago

        I’m very inclined to use this method instead.

        I would like to ask for some suggestions on the initial process to migrate the data from UnRaid.

        Considering that:

        • My disk pool is made out of 2 10TB disks, for a total of 20TB
        • It also has a 10TB parity disk
        • The pool is using just -6TB of the storage

        The option I see is:

        • Get another 10TB disk
        • I can clear the parity drive and copy my data from the pool to that disk for migrating
        • Configure the pool disks to RaidZ and once I complete that, use the other 2 disks as parity pool

        Or, I bite the bullet, get brand new 10TB disks, 12 to make it Raidz2 and have a storage pool of 40TB (35 usable?). I’m thinking 4 groups of 3 disks each should do the trick. Then use the same method to migrate my data.

        With 64GB of ECC RAM, I should have a pretty swift storage IOPS that way.

        source

        • -> View More Comments