Hi all,
It’s been a long… years at work and my brain is fried currently with no bandwidth to properly determine how to migrate a BTFRS array from unraid over to proxmox. I can see the array in proxmox and am able to mount it but now I cannot for the life of me figure out how to
- verify that the data is intact
- assign it to a storage pool for use in vm’s
- view it within proxmox
I haven’t touched proxmox in years after settling on unraid a while back, but am looking to move back to a non-unraid config.
Anyone here have experience with btfrs and proxmox? Any good links to a tutorial or video?
Thanks!
If it mounts, and you can read it, then it’s fine and you just need Proxmox to pay attention to it. Works like any Linux install and you need to add the disk into fstab BEFORE Proxmox starts up. Here’s a thread: https://forum.proxmox.com/threads/how-to-mount-existing-disk-to-storage.66559/
I don’t have an answer to your question, but I’m curious why you want to get away from unraid. I’m an unraid user and am just looking for some insight.
I am somewhat fed up with unraid, reboot haven’t worked for over half a year because some service does not want to stop (and I have to manually restart it via power reset).
I am primarily running docker container and unraids GUI is really good however once you know to write the composes yourself I find it way more stable to do so especially because you can version control them.
I had many crashes over the last year where I could just not reach my services neither could I stop/restart them in the GUI or anything.
These things just didn’t happen on proxmox to me (yet) and that’s what I want to switch to a proxmox cluster fully
The big one for me is kubernetes, that said I have an unraid main and a thin Client I use to experiment with it
Maybe don’t work when your brain is fried.
When you are rested take your disks and put them in a new ZFS pool.
If you have new drives: make a zfs array and copy all files there
If you want to recycle drives while temporarily keeping the parity drives: from unraid 7 set a drive as unused, use the mover (or unbalance) to empty it, check if it’s actually empty by going to /mnt/diskX , format it as btrfs, set it as preferred for your shares, choose another disk to empty, use the mover to move all the data from the next disk to the new btrfs one, then remove the empty drive and add it to the btrfs raid. Repeat.
…why? He has a functioning array already. It mounts and is readable.
The unraid array it’s not an array, but a bunch of xfs partitions where a third party program is doing softraid. If opened on any other Linux distro, they will mount but parity drives are ignored
They literally said it was a btrfs array.
a btrfs “array” in unraid is composed by individual btrfs partitions mounted as /mnt/disk1 /disk2 /disk3 and so on, then there’s a daemon that makes a “unified” view at /mnt/user/, and it uses a different algorithm for parity.
There’s a way to make real btrfs raid arrays, but it has been introduced very recently (1-2 years ago), and it’s not the default that you create when you use the Web UI.
Sure…so I’m confused why you’re bringing XFS to the conversation.
for some reason i read xfs instead of btrfs…
their array implementation is stupid and smart at the same time. I love that you can mix and match disks at random, even with different filesystems (you can have one drive in murderfs, one in xfs, one in btrfs and the last one in zfs and all protected with the same parity drive), but i completely hate how my server is locked by a 25% iowait due to how much cpu intensive is their softraid. Maybe when they came out with this system 20 years ago it was groundbreaking, but now it is stupid. Now with unraid 7 released one week ago they’re starting to deprecate it (disabled by default in new install) in favor of native btrfs or zfs arrays
