• 5 Posts
  • 52 Comments
Joined 3 years ago
cake
Cake day: June 21st, 2023

help-circle


  • This is also true of Jellyfin, though. I have apps on my Windows PC, my Android phone, multiple Nvidia Shield boxes on my TVs, plus the web interface if I need it.

    I switched over from Plex several years ago, and while it takes a bit more time to configure, compatibility for clients seems just as good for Jellyfin as it is for Plex.

    Most importantly, Jellyfin is strictly client/server, no “cloud” bullshit and no remote account is required; I don’t want Plex phoning home with a list of the media on my file server.




  • I’m leaving this here for continuity, but don’t follow what I said here. I have my containers set as privileged. I was wrong.

    I have a server that runs Proxmox and a server that runs TrueNAS, so a very similar setup to yours. As long as your LXC is tied to a network adapter that has access to your file server (it almost certainly is unless you’re using multiple NICs and/or VLANs), you should be able to mount shares inside your LXC just like you do on any other Linux machine.

    Can you ping your fileserver from inside the container? If so, then the issue is with the configuration in the container itself. Privileged or unprivileged shouldn’t matter here. How are you trying to mount the CIFS share?

    Edit: I see that you’re mounting the share in Proxmox and mapping it to your container. You don’t need to do this. Just mount it in the container itself.


  • I am virtually never out of town, but if I was, then no, I wouldn’t worry.

    If there was a technical problem that left my servers inaccessible, then oh well. It’s the same scenario as if I had shut them off. I’d fix it when I get back. This has never happened, though. I’ve had VMs crash, but I have never had a situation where any of my servers were completely inaccessible.

    The only situation I can think of where I’d need to immediately shut down a server would be a drive failure in my ZFS array, but the chances of this happening in conjunction with a loss of connectivity are exceedingly unlikely. If it was a major concern, I’d write a script to power down the server when a drive fails.





  • I definitely get that. The big thing for me is music, and I routinely buy physical and digital copies of albums to add to my collection. I don’t mind sending some money to help my favorite artists keep producing content that I enjoy. With video, though, it’s just so much harder. I’d be happy to pay $50 or more per month for what Netflix used to be, or even buy downloadable copies of a TV series that I like. That’s just not possible these days. I’d be subscribing to Netflix, Discovery, Paramount, Apple TV, probably a few more. It’s ridiculous. Forget buying and downloading TV shows; there’s no option for that at all. I’d rather just not watch TV or find an “alternate” means of getting the media I want.


  • I canceled Netflix several years ago after having used it as my primary source of media almost since they first started their streaming service.

    The problem I had is that the quality of their content decreased so dramatically that even though it worked fine from a technical perspective, there was nothing I wanted to watch. They used to have extensive back-catelogues of shows from all sorts of different national cable networks, tons of interesting foreign shows, documentaries, obscure indie films, etc.

    Slowly but surely this all disappeared. Networks stopped licensing content to Netflix. As soon as they realized that streaming was the way of the future, they wanted to capitalize on it with their own streaming services. In a way, Netflix was a victim of their own success.

    Now they’re essentially just a TV network of their own and not the aggregator of media that they used it me. The few decent originals that they have were just not justification enough for me to pay for a service I might use a few times a year.





  • It’s actually surprising how much just having a person in the room can alter the temperature and humidity levels. In my master bathroom, I have my bathroom fan set to activate when the dew point reaches a certain level (I’ve found that dew point produces better results than just humidity); the idea is that the bathroom will be ventilated when someone takes a shower and for however long it takes for the humidity to dissipate after they’re done. The funny thing is that every so often, I’ll take an excessively long poop (lets me honest, I’m scrolling on my phone), and the fan will kick on. Just being in the bathroom will alter the dew point enough that it triggers the fan.

    I also have a room that contains all my server/networking equipment. It’s climate-controlled, and I’m constantly monitoring temperatures. The times that in the room working, I can see a noticeable spike in the temperature graph, even though the only variable that’s changed is that there’s a person in the room.

    So my point is: OP might not have been having fun that night; it’s entirely possible someone just came in and went to bed.


  • There are really two reasons ECC is a “must-have” for me.

    • I’ve had some variant of a “homelab” for probably 15 years, maybe more. For a long time, I was plagued with crashes, random errors, etc. Once I stopped using consumer-grade parts and switched over to actual server hardware, these problems went away completely. I can actually use my homelab as the core of my home network instead of just something fun to play with. Some of this improvement is probably due to better power supplies, storage, server CPUs, etc, but ECC memory could very well play a part. This is just anecdotal, though.
    • ECC memory has saved me before. One of the memory modules in my NAS went bad; ECC detected the error, corrected it, and TrueNAS sent me an alert. Since most of the RAM in my NAS is used for a ZFS cache, this likely would have caused data loss had I been using non-error-corrected memory. Because I had ECC, I was able to shut down the server, pull the bad module, and start it back up with maybe 10 minutes of downtime as the worst result of the failed module.

    I don’t care about ECC in my desktop PCs, but for anything “mission-critical,” which is basically everything in my server rack, I don’t feel safe without it. Pfsense is probably the most critical service, so whatever machine is running it had better have ECC.

    I switched from bare-metal to a VM for largely the same reason you did. I was running Pfsense on an old-ish Supermicro server, and it was pushing my UPS too close to its power limit. It’s crazy to me that yours only pulled 40 watts, though; I think I saved about 150-175W by switching it to a VM. My entire rack contains a NAS, a Proxmox server, a few switches, and a couple of other miscellaneous things. Total power draw is about 600-650W, and jumps over 700W under a heavy load (file transfers, video encoding, etc). I still don’t like the idea of having Pfsense on a VM, though; I’d really like to be able to make changes to my Proxmox server without dropping connectivity to the entire property. My UPS tops out at 800W, though, so if I do switch back to bare-metal, I only have realistically 50-75W to spare.


  • corroded@lemmy.worldtoSelfhosted@lemmy.worldLow Cost Mini PCs
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    2 years ago

    I have a few services running on Proxmox that I’d like to switch over to bare metal. Pfsense for one. No need for an entire 1U server, but running on a dedicated machine would be great.

    Every mini PC I find is always lacking in some regard. ECC memory is non-negotiable, as is an SFP+ port or the ability to add a low-profile PCIe NIC, and I’m done buying off-brand Chinese crop on Amazon.

    If someone with a good reputation makes a reasonably-priced mini PC with ECC memory and at least some way to accept a 10Gb DAC, I’ll probably buy two.