this post was submitted on 07 May 2025
6 points (87.5% liked)
Self Hosted - Self-hosting your services.
14565 readers
1 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
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
Important
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate. This is strongly encouraged!
Cross-posting
- !everything_git@lemmy.ml is allowed!
- !docker@lemmy.ml is allowed!
- !portainer@lemmy.ml is allowed!
- !fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
- !selfhosted@lemmy.ml is allowed!
If you see a rule-breaker please DM the mods!
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I doubt this part.
I think as soon as the NAS is working, the others (including prox) should use it, and no additional complications.
It's probable that I'm missing something but I couldn't get the share to be available to any other VM or LXC on ProxMox until I passed the pool from TrueNAS back to ProxMox.
I'm all for getting rid of the TrueNAS VM as long as I can reassemble the zfspool in ProxMox without losing the data (though if I did, no big deal). And I'd also like a user friendly way of monitoring the health of my disks.
zfs itself can do that. The zpool members know the pool and the other members.
So I don't need to take care to re-mount them in the right configuration? I'll do some googling but I wasn't sure if I needed to do some backup preparation of something.