• 1 Post
  • 17 Comments
Joined 1Y ago
cake
Cake day: Mar 28, 2023

help-circle
rss

bestie why do you have <link rel=“alternate” type=“application/rss+xml” title=“selfh.st” href=“”> in your <head>? It doesn’t point to an rss feed, unless your site is an rss feed in itself? would be kinda crazy though

https://www.rssboard.org/rss-autodiscovery

should point to https://selfh.st/rss/ right?



Yeah. That’s what I used to do when I started out.

The simplest thing to do is install Debian on the computer and create partitions. You have 4 HDDs and 2 SSDs so it’d be stupid to create 6 separate partitions for each drive.

See in the BIOS if your motherboard supports software RAID1, so you are protected against drive failure somewhat. This will allow you to get something barebones running that’ll use at least 2 drives with redundancy. I assume the mobo RAID1 is stupid and only allows for max 2 drives, so the other drives will be just laying around useless. If that’s the case, probably use the 2 SSDs first. I see other posters recommending higher orders of RAID, but I only have 2 HDDs so I never really delved into that :P Perhaps that’s sound

With a system like that you could probably set up some small NFS for sharing your files by configuring it manually from the terminal.

Note that going with raw linux is “simpler” in the sense that it’s perhaps easier to wrap your head around or tinker with, but TrueNAS or Unraid have GUIs that will allow you to create e.g. the mentioned NFS share with a few clicks, rather than having to do it from the terminal. Depends on what you’re looking for. You could move up to TrueNAS or Unraid once you’ve played with raw Linux enough for example.


Once you have that,

I only ever dealt with ZFS and TrueNAS. ZFS will allow you to create a “partition” (pool in zfs terms) from many drives at the same time, so you’d be able to use more drives than just the two from RAID1.


The drives that you have are probably shitty SMR drives whose write speed dramatically slows down once you’re writing to them for a longer time. Consider buying CMR drives in the future, or just going all-SSD if it fits your usecase. ZFS hates SMR drives.


Chiming in with my org mode setup as well:

  • Keep notes on my NAS
  • Mount NFS share with notes on desktop and edit with Emacs
  • Create a WebDAV share of the notes (so shared both using nfs and webdav). Use the Android “Orgzly Revived” app from F-droid and log into the webdav share

I used to use Syncthing to avoid having both NFS and Webdav but it didnt sync



Well, Git is still centralized. Typically there’s only one main location where work on a project happens - a Git forge like GitHub, or in the simplest scenario just an SSH server.

Federation will help because it will allow working on a project in one forge from another forge. You could e.g. create a pull request on your own self-hosted forge (e.g. Forgejo instance) and then submit that pull request on another forge that’s hosted somewhere else. GitHub taking down a repo wouldn’t be as annoying, since people would still have the main sources of their pull requests in their own forges. And GitHub wouldn’t be able to remove their fork for whatever reason.



Hey, OP here again.

Here’s what I ended up with:

  • upgrading my TrueNAS CORE to TrueNAS SCALE - it was really easy, just upload a 1.3GB upload file through the web UI. CORE’s apps/plugins are based on BSD jails, where SCALE apps are based on Kubernetes/Docker, so I can any arbitrary Docker container from Dockerhub as I please, rather than being limited to BSD jails

  • migrating all the VMs/LXCs to matching TrueNAS SCALE Applications. So e.g. my hand-made Navidrome LXC was migrated to the TrueNAS SCALE Application. Sometimes there was no equivalent TrueNAS app for what I was using - e.g. Forgejo, so I just ran an arbitrary container from dockerhub.

  • decomissioning the Proxmox mini-pc (Lenovo M920q). I’ll sell it later or maybe turn it into a pfSense router.

I installed a custom TrueNAS app repository called Truecharts. It has some apps that the default repo doesn’t have, and it also has a nice integration with Ingress (Traefik), which allows you to easily create a reverse proxy using just the GUI.

I’m still yet to figure out how to set up Let’s Encrypt for the services I made available to the Internet. I can no longer do things the Linux way, i must do it the Kubernetes way, so I’m kind of limited. Looks like HTTP01 challenges don’t work yet and I’ll have to use DNS01.

Looking back, I’m happy I consolidated. The hypervisor was idling all the time - so what’s the point of having a second machine? Also, the only centralized machine has IPMI, so I have full remote control, and I’ll hopefully never have to plug a VGA cable again. Of course, there’s no iSCSI fault path anymore, though I’m happy I got to experiment with it.

The downside is as I said - I’m forced to do things the Kubernetes/Docker way, because that’s what TrueNAS uses and that’s the abstraction layer I’m working on. Docker containers are meant for running things, not for portability. I’m sad that I can’t just pack things up in a nice LXC and drag it around wherever I please. Still, I don’t thing I’ll be switching from TrueNAS, so perhaps portability isn’t that big of a deal.

I’m also sad that I … no longer have a hypervisor. Sure, SCALE can do VMs, but perhaps keeping TrueNAS virtualized would give me the best of both worlds.


ForgeFed and whatever Gitlab is doing with the PR federation taking off.

In the meantime I make my gh account as lean as possible.

  • removed real name, photo and all links
  • profile changed to private mode
  • all gists and stars removed
  • removed most useless repos, migrated one important repo to self hosted forgejo instance, remaining 2 are laying around

I use my personal account for work, but I’d close my account and create an employer-only one if I needed to.


Ah right, sorry, switched things up. Indeed, I also use my registrar’s DNS system, but if I switched to something that has an API supported by certbot (e.g. dns zones that cost 0.5 eur in large cloud providers) it would work.


I used [large american registrar], but switched to a small one in my country because I wanted to pay a local business. I found it from somebody’s compilation of companies that offer a TLD for my country, and I just picked the recommended one in that post. It was the one that charged the least.

Keep in mind that with a smaller registrar you won’t be able to get a TLS cert using the “do some shit with my domain records” method - you’ll have to always install the nginx/Apache etc. plugin for Let’s Encrypt


Thanks for making it clear that iSCSI power down is in fact one of the more grim scenarios, I couldn’t make it out how bad of a situation it is. In an enterprise environment a SAN being down would require some type of incident report.

UPS - as you suggested - would solve most of my problems to be honest.


I edited my post to clarify. TrueNAS also keeps documents, photos, torrents, music. I also use the mount feature so that the music server LXC can access music


I edited my post to clarify that TrueNAS keeps more than just VMs. It has photos, documents etc. as well.

Generally when people run two different servers at home, they keep the VM drives on the hypervisor and just use the NAS for storing bigger things like media files

This is simple and makes sense as well. My TrueNAS is only 2 HDDs, which is not ideal for VMs. I could get a larger drive SSD/M.2 drive for the hypervisor, though the Lenovo M920q supports 1xM.2 and 1x2.5" drive.

Hosting VM drives over iSCSI works in an enterprise environment, but if you can’t guarantee uptime for your storage solution then all you’re doing is adding failure modes.

Well, my whole setup comes from the fact that I wanted to cosplay as an enterprise environment (famous last words for a homelabber). I’ve been powering the TrueNAS up and down a lot due to some electricity-related construction in my apartament, and it brought out this flaw in my setup. I guess an UPS would be in order, as another poster pointed out.


It’d be nice to have Proxmox and TrueNAS side by side on one machine, but since TrueNAS forums are against the virtualization of TrueNAS (yes I know people do that, but I’m not willing) I’m somewhat stuck with having to have one bare metal machine per appliance.


How to make setup more resilient? Proxmox mini-PC \w iSCSI to TrueNAS
Hello. My setup is: - Lenovo M920q mini pc with Proxmox installed (this doesn't have IPMI, only vPRO and it's annoying me) - Fujitsu TX1320 M3 with TrueNAS Core installed - ZFS + RAID1 (this is a low-end "enterprise grade" server, and best thing - it has IPMI). The Proxmox PC keeps all its CTs and 1 VM on the TrueNAS using iSCSI. The idea behind my setup was that it felt nice that the TrueNAS would handle all the storage heavy lifting - ZFS, RAID etc., while the Proxmox mini PC would be a "compute-only" node that has a naked Proxmox install with some config. The problem with that is if the TrueNAS machine loses power or is restarted, the Proxmox CTs/VMs switch their filesystem to read-only and stop responding to requests. This is because the iSCSI connection is interrupted. **When the TrueNAS is back online, Proxmox doesn't make any attempt to restart the VMs/CTs - they'd still be broken.** It's annoying to me to have to VPN to the Proxmox web ui and wait 15 minutes until all the CTs/VMs are restarted and now again functioning on the "alive" iSCSI connection. I was wondering what are my options here to remove the dependency chain? I'm really into the idea of decomissioning the Proxmox node because I'm scared I won't be able to (over VPN) change the power state of the machine if something goes wrong, since it only has vPro and not iSCSI like the TrueNAS machine. By doing that, I'd consolidate the storage and the compute into the TrueNAS machine. Options I can think of: 1. Decomission the Proxmox node and move all Debian VMs/CTs to TrueNAS BSD jails. Is that even possible? Will all my Debian VMs work in BSD? 2. Decomission the Proxmox node, switch TrueNAS Core to TrueNAS Scale and move CTs/VMs to TrueNAS Scale's Linux VMs 3. Keep the Proxmox node and somehow figure out how to get Proxmox to refresh the CTs/VMs on iSCSI connection loss. 4. Keep the Proxmox PC, but switch it to iESXI hoping that it handles the iSCSI failure more gracefully EDIT: I didn't make it clear at first - TrueNAS stores more data than just VMs - documents, Linux ISOs (TM), photos, Syncthing
fedilink

I have a self hosted Forgejo instance with disabled user registration. The problem is as you mentioned ,- nobody wants to create yet another account. What’s more, it’s not possible to create PRs using e-mail.

I’d have to give out my e-mail somewhere on the git page then say “send patches here”.

It’s somewhat wise to disable user registration because users can freely fork your repos within your instance then change the fork to host whatever they want.