antsu

You can check out anytime you like, but you can never leeeeeeeave!

Just play Hotel California.

Debian on the streets (servers), Arch on the sheets (laptop).

Worry not, Microsoft got you covered! https://bettersolutions.com/vba/enumerations/msotristate.htm

Briefly addressing the RAID types you mentioned:

• RAID-0: OH NO OH GOD PLEASE NO AHHHHHHH
• RAID-1: There’s nothing wrong with it, but it feels very weird to me that BTRFS can do RAID-1 over 3 disks. It’s still technically 2 copies of every block, meaning you can in theory lose any single drive and still recover the data, but idk, it just feels wrong.
• RAID-10: Again, weird that BTRFS allows this with an odd amount of disks. From what I can find, this has no advantage over RAID-1 with 3 disks and can in fact perform worse.
• RAID-5: It’s probably fine if you have backups, and you get the most usable space out of your disks, but performance will take a hit, and scrubs are terribly slow.

Now, you mentioned not wanting ZFS due to complexity, but really, it is no more complex to manage than BTRFS. It’s fairly easy to get it working on any modern Linux distro (Ubuntu has support out-of-the-box, Debian has it packaged as a DKMS module, Arch has it in AUR, and so on).

With ZFS, you could create a RAID-Z1 (equivalent to a RAID-5) without any of the performance penalties or risks that BTRFS RAID-5 has. Both have pretty much them same features, with the main difference that ZFS can’t be “re-balanced” to a different disk layout like BTRFS can, but it will also generally not corrupt your data if you look at it wrong. Everything else maps pretty much 1:1 between them. Both support:

• Transparent compression
• Transparent checksums
• Scrubbing
• Snapshots
• Block-level transfers (btrfs-send / zfs-send)
• Fairly intuitive CLI
• Filesystem (BTRFS) == Pool (ZFS)
• Subvolume (BTRFS) == Dataset (ZFS)

I had the same problem: Debian host + official Jellyfin Docker image, all set up according to the official guide, but it would fail to transcode anything.

There was no relevant information about what was wrong in the logs so what I did was:

• Copy the ffmpeg command from the logs.
• docker exec -it into the Jellyfin container.
• run the same ffmpeg command manually so I could see the error directly.

Long story short, because the Nvidia toolkit uses the driver/libraries from the host, the error was that I was missing the library libnvidia-encode1 on the host. After installing that, everything works as it should.

No, but I’m in the UK, so the lowest temp this doorbell has ever experienced here is around -8°C. Depending on where in the world you are, that might not even register as “cold”. Also, I’ve wired it with the official 16V power supply included in the box and the “chime adapter” dongle thingy, which turned out to be really important for it to function properly.

Nooooo Reimuuuu!

No idea how it compares to Ring, but my wife is a severe technophobe and she had no issues or complaints with Protect. We only have one doorbell + one camera connected to a CloudKey+ though, so your mileage may vary.

Motion detection works reasonably well as far as I can tell, with person, vehicle and animal detection too.

Regarding the doorbell, one option you have is to try finding a second-hand Unifi G4 Doorbell (non-pro). It can be wired with only the two wires you already have. Just make sure you have relatively good 5GHz WiFi reception near your front door, because the 2.4GHz antennas on this model are notably bad.

United by high cholesterol!

Yes, you can just install and use it straight away, no need to mess with self-hosting if you don’t want to. You also don’t need a subscription, that just unlocks some extra features.

RustDesk is excellent, it’s basically open source TeamViewer. And if you don’t want to use their servers, you can even host your own.

They scream, for they do not know!

As a former sysadmin, this is correct.

Hey. I realise my comment may have come off as rude and made me sound like an asshole. It was not my intention to be disrespectful, apologies for that. The reason I posted that is because I read your post (thanks for taking the time to write and share it) and it left me a bit puzzled. I respect wanting something stable, familiar and that requires minimal maintenance, but you seemed to imply this is not possible with a more “traditional” NAS setup. Many of the points you raised about wanting an applliance-like experience are equally achievable on most Linux distros, with no license fees, and with a lot more flexibility, should you need it in the future (although I understand you don’t need or want it).

Take Debian for example (a.k.a. the world’s most boring distro, in a good sense). With the knowledge you demonstrated about the underlying services involved (BTRFS, Wireguard, etc), it would have taken you no more time to configure the same set of services on a minimal Debian install, it would also run rock-solid for many years, and updates would be entirely at your discretion (as they are with RouterOS). Plus, your pockets would be 50 EUR heavier. But for me, personally, by far the biggest avantage of going with Linux for a data storage solution like this is the possiblity of using ZFS.

Also, have this Debian meme:

“I do not want to play sysadmin in my spare time.”

* proceeds to do a bunch of sysadminy things, but on a proprietary OS *

Huh…

59 according to docker info.

Also, whoever did the price tags is a coward.

Exactly. I took this photo the other day exactly for this reason (but forgot to post it anywhere).

This is the way.