thelemonalex

joined 2 years ago
[–] [email protected] 1 points 3 hours ago

I see, okay, I understand now. Thank you very much for explaining that in detail!

[–] [email protected] 1 points 3 hours ago* (last edited 3 hours ago)

Okay, I have one of the pools that is pretty empty and has non-critical data, and I think I'll try migrating that first, and see if it's imported correctly by Proxmox.

About Containers, I think I'll have to do some more research because I think I haven't fully understood yet how they compare to VMs. Or like, when I should use the one over the other. I guess I could have a Container with a bind mount to a dataset that I want to be able to share over NFS or SMB, and handle that from whatever OS I put in the Container, right? But, I could also have a VM do that, and though it wouldn't be able to share the data with other VMs, it can do it over NFS, can't it? What are the advantages of doing one thing over the other?

Well, in any case, thank you for your patience, for going over each detail and taking the time to correct me where I'm wrong. I'm learning a lot, so thank you!

Edit: fixing grammar

[–] [email protected] 1 points 3 hours ago

Yeah, but I don't have two separate machines, that's why I'm using Proxmox. And I used TrueNAS previously, with TrueCharts, and I wasn't happy. It was pretty unstable and finnicky for me, and hard to go back to, after running docker in a clean Debian VM, which has been rocksolid so far. Still, thanks for your suggestion

[–] [email protected] 1 points 3 hours ago

Yeah, you're totally right. Okay thanks, will do

[–] [email protected] 1 points 3 hours ago (1 children)

Wow, that's awesome. I think that's actually the approach I'm going to go for. This way I don't need to buy hardware, and I don't need to work with TrueNAS anymore.

Where you talk about "walking the backups", do you mean that you can actually see the entire file structure of the container? I mean, I don't know how virtual disks are stored on the dataset. Like, as far as I know, a VM virtualized disk is just a file, right? So you'd have a ZFS dataset with a single file, for example? Could you then try and navigate the files inside this VM disk file, without the VM? Or did I misunderstand, and you're mounting the dataset, somehow, directly inside the VM? Is that like a passthrough for datasets?

In any case, thank you for sharing so much information and for offering help. I may take you up on that, as it seems that this is the approach that I feel most comfortable with.

[–] [email protected] 1 points 3 hours ago

Okay, thank you, that's good to know. However, I don't have two separate devices that I can use to separate the NAS functionality from the Docker functionality, that's why I was using Proxmox in the first place. And, I'm not sure how well Docker can run in OMV. But I'll still keep it in mind as an option, thank you!

[–] [email protected] 1 points 3 hours ago

Thanks, I'll keep it in mind

[–] [email protected] 1 points 3 hours ago (1 children)

Yeah, it won't happen again. I think I'll migrate to managing ZFS directly from Proxmox, and then handle SMB in a VM or something, because I'm worried about compatibility, with the PCIe SATA card, as the system's pretty dated.

[–] [email protected] 1 points 3 hours ago

Okay, good to know, thanks!

[–] [email protected] 1 points 1 day ago (4 children)

Okay, no VM, understood, but I do want to use a GUI for ZFS, because I'm basically a noob.

[–] [email protected] 1 points 1 day ago (4 children)

Okay, if Proxmox can handle all that, I'll be glad to ditch TrueNAS. However, I'm afraid that I won't know how to migrate. I've found this reddit thread about someone who tried to do the same thing (I think) and accidentally corrupted their pools. About skipping NFS shares, that would be a big improvement for me, but I'm very unfamiliar with bind mounts. If I understand correctly, you can specify directories that live on the Proxmox Host, and they appear inside the VM, right? How does this compare to using virtual storage? Also, how can I replicate the ZFS pools to an external machine? In any case, thank you for that info!

[–] [email protected] 2 points 1 day ago

I'm already running TrueNAS Scale, but I'm unsure about the docker support. I did use TrueCharts and such, but it was very unstable, so I moved away from that.

 

Hi everyone, I've been working on my homelab for a year and a half now, and I've tested several approaches to managing NAS and selfhosted applications. My current setup is an old desktop computer that boots into Proxmox, which has two VMs:

  • TrueNAS Scale: manages storage, shares and replication.
  • Debian 12 w/ docker: for all of my selfhosted applications.

The applications connect to the TrueNAS' storage via NFS. I have two identical HDDs as a mirror, another one that has no failsafe (but it's fine, because the data it contains is non-critical), and an external HDD that I want to use for replication, or some other use I still haven't decided.

Now, the issue is the following. I've noticed that TrueNAS complains that the HDDs are Unhealthy and has complained about checksum errors. It also turns out that it can't run S.M.A.R.T. checks, because instead of using an HBA, I'm directly passing the entire HDDs by ID to the VM. I've read recently that it's discouraged to pass virtualized disks to TrueNAS, as data corruption can occur. And lately I was having trouble with a selfhosted instance of gitea, where data (apparently) got corrupted, and git was throwing errors when you tried to fetch or pull. I don't know if this is related or not.

Now the thing is, I have a very limited budget, so I'm not keen on buying a dedicated HBA just out of a hunch. Is it really needed?

I mean, I know I could run TrueNAS directly, instead of using Proxmox, but I've found TrueNAS to be a pretty crappy Hypervisor (IMHO) in the past.

My main goal is to be able to manage the data that is used in selfhosted applications separately. For example, I want to be able to access Nextcloud's files, even if the docker instance is broken. But maybe this is just an irrational fear, and I should instead backup the entire docker instances and hope for the best, or maybe I'm just misunderstanding how this works.

In any case, I have some data that I want to store and want to reliably archive, and I don't want the docker apps to have too much control over it. That's why I went with the current approach. It has also allowed for very granular control. But it's also a bit more cumbersome, as everytime I want to selfhost a new app, I need to configure datasets, permissions and mounting of NFS shares.

Is there a simpler approach to all this? Or should I just buy an HBA and continue with things as they are? If so, which one should I buy (considering a very limited budget)?

I'm thankful for any advice you can give and for your time. Have a nice day!

 

Hi everyone! Just wanted to ask if anyone has any idea what this typeface is actually called? It says it's called "Growing", but I couldn't find it under that name... If anyone has a clue, or an idea of where I can search... I'll be thankful for anything you can provide. Have a nice day y'all!

view more: next ›