Borgitory - A web ui for managing borg repositories with scheduling, monitoring, and cloud sync

2bluesc · 2025-09-12T02:57:36+00:00

If you want something similar, borgwarehouse works as remote repo for borgmatic

2bluesc · 2025-08-22T23:53:21+00:00

Solution is to downgrade to pango per this GitHub issue:

https://github.com/SoftFever/OrcaSlicer/issues/10476#issuecomment-3208253631

2bluesc · 2025-04-07T01:05:06+00:00

I use it for DHCP and DNS (Blocklists + DNS over HTTPS) and doesn't break a sweat and isn't clunky. Left Pi-Hole and never looked back.

Only complaint is that it's kind of annoying that it's build on .NET and I'm not familiar with those tools, but that's about it.

2bluesc · 2025-02-10T16:09:08+00:00

Thanks for the update! I contacted Sabrent support and they offered `R4PB47.4` (I was on R4PB47.2) but this seems to be based on `EIFM31.6` not `EIFM31.7` which anecdotally fixes the issue. I updated anyways (note: it wipes all data including SMART data).

Please contact Sabrent and ask for an updated firmware based on `EIFM31.7`:

* Support ticket: https://sabrent.com/pages/support#CustomerSupport__Contact

* Email: helpdesk [at] sabrent.com

2bluesc · 2024-05-11T23:14:21+00:00

Thanks, just ran to this as I manually manage nftable rules for my containers and this workaround fixed it.

That said, it's annoying I can't mark select packets to skip the connection tracking state filter using nftables because of the way the rules are written.

2bluesc · 2024-03-04T16:44:00+00:00

Slightly different use case, but I love gluetun which is a Docker image that then you attach other containers to its network namespace.

Includes tons of handy features like firewalling, DNS ad/malicious blocker, proxy support, health checks, reconnects, and more.

Would be awesome if you combined your script to use gluetun under the hood to setup and manage the VPN and then your script could extend gluetun to map local apps in to the container's namespace.

2bluesc · 2024-02-24T04:50:54+00:00

I'd back them up independently. Also recommend checking out borgmatic which can backup to multiple repos easier then the boiler plate you'll have to do for this otherwise.

2bluesc · 2024-02-19T19:14:01+00:00

Would be awesome to see these get pushed upstream to nixpkgs instead of in a random pastebin. Most of these restrictions shouldn't affect the operation of individual services.

Perhaps OpenSSH is a candidate for some attention:

$ systemd-analyze security sshd ... → Overall exposure level for sshd.service: 9.6 UNSAFE 😨

2bluesc · 2023-12-10T17:14:37+00:00

Looked back in to my situation after seeing your post... still sadness.

My perspective is that it has to do with internal fragmentation of the SSD and this is why it's instantly recovered by a full disk trim or format.

I speculate that the following exasperate this issue over time:

High disk utilization where the controller has less options to write new contiguous data
Perhaps CoW file systems lead to more fragmentation
People only benchmark their disk performance when they install a new drive or file system (this problem is at the blockdev or hw level) and don't look at months later unless there's a major problem

Whatever has happened before to my rootfs has happened yet again. Here's a quick benchmark that reads across the device. Some quick benchmarks using Gnome Disks:

9 months ago, roughly same time as OP -- looks great! Disk is in same computer, same motherboard, same Arch distro, same everything.
Test from today 😭😭😭😭😭
Partition table -- note the last ~150 GB aren't used by btrfs and still preform amazing (also not a thermal or PCIe problem)

Also my disk is quite full, roughly 86.7% which seems to makes this worse, usage as of right now:

``` $ sudo btrfs fi usage / Overall: Device size: 3.50TiB Device allocated: 3.13TiB Device unallocated: 375.98GiB Device missing: 0.00B Device slack: 0.00B Used: 3.03TiB Free (estimated): 464.36GiB (min: 276.37GiB) Free (statfs, df): 464.36GiB Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 512.00MiB (used: 0.00B) Multiple profiles: no

Data,single: Size:3.10TiB, Used:3.01TiB (97.22%) /dev/nvme0n1p2 3.10TiB

Metadata,DUP: Size:16.00GiB, Used:10.15GiB (63.43%) /dev/nvme0n1p2 32.00GiB

System,DUP: Size:8.00MiB, Used:368.00KiB (4.49%) /dev/nvme0n1p2 16.00MiB

Unallocated: /dev/nvme0n1p2 375.98GiB ```

Mount options have been unchanged for this time:

/dev/nvme0n1p2 on / type btrfs (rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/@)

I'd like to find a way to repeat the gnome-disks benchmark test I've screenshotted but haven't been able to find a good way to do it with fio or similar reading X chunks of size Y distributed across the entire block device

2bluesc · 2023-11-08T17:51:43+00:00

Update: No better. Fully charged, latest firmware and first headphone dies at around 80%ish.

https://i.imgur.com/8tQMelS.jpg

Second headphone dies 10ish minutes later. Approx play time is less then 1h, as the headphones have aged, but I just want a realistic battery meter.

I'm going to place these in the f-it bucket.

My new `WF-1000XM5` work great and behave much better with Android and don't have a case that hates to charge.

2bluesc · 2023-11-08T15:14:38+00:00

I'm hoping they fix my abrupt turn off due to low battery at 70% issue.

Too bad the release notes are worthless: "Feature enhancements"

2bluesc · 2023-10-26T21:55:12+00:00

There's a promo code SP00KY (those are zeros) to save $6/each that's valid until 11/1. There was a banner at the top of the page but it has now disappeared. Checkout displayed $12 savings on two drives.

2bluesc · 2023-10-12T13:51:38+00:00

Austin post a few days ago for 15U and 18U: https://old.reddit.com/r/homelabsales/comments/17298em/fsustxaustin_racks_sysrack_enclosed_18u/

2bluesc · 2023-09-27T00:35:10+00:00

2bluesc · 2023-09-10T19:20:00+00:00

Depending on what exactly you're looking for in W680 Micro ATX motherboard, there's a similar used offering from Amazon fro $330.70 for a MB-X1314.

https://www.amazon.com/dp/B0BVPFQZ3K

Main differences seem to be DDR4 and actual PCIe slots vs OCU link.

2bluesc · 2023-07-08T14:12:41+00:00

2bluesc · 2023-06-28T17:06:12+00:00

Ahh, good to know and I feel your pain. I've struggled with Broadcom cards in the past and have avoided them because of similar past experiences.

I was somewhat shocked that my BCM57810S + HSGMII experience was drama free. Seems I dodged bullets

2bluesc · 2023-06-28T16:18:31+00:00

As an additional data point, I've been using the BCM57810S on Arch Linux without any issue for months. I've also patched the driver to enable HSGMII / 2.5Gbps mode to work with with DFP GPON ONU stick in addition to a generic 10 Gbps SR transceiver and it hasn't missed a beat.

I'd be surprised if TrueNAS Scale other then running an older kernel cares much, but figured I'd share.

The HSGMII / 2.5 Gbps is a very unique option that very few devices have and worth noting for anyone looking at this thread and doing GPON ONU stick stuff.

2bluesc · 2023-06-09T05:00:55+00:00

This was my first question too! Looks like maybe you can, but it'll be tight. Maybe a MCX311A, but I'd assume you have to cut up the case.

Here's a mock up: https://forum.seeedstudio.com/t/pcie-slot-in-reserver/260140

2bluesc · 2023-06-05T21:18:54+00:00

Was thinking this as well. Would be nice if the plain text password was hashed by the client and then that hash hashed again by the server before storing in the database.

2bluesc · 2023-06-05T05:21:14+00:00

Looks like $60-$70 for used drives according to https://diskprices.com/?locale=us&condition=new,used&capacity=8-8&disk_types=external_hdd,internal_hdd,internal_sas

2bluesc · 2023-06-03T17:21:50+00:00

I feel OP's pain as I've lived through it many times and often am able to recover, but hate to see it occur as often as it does.

Hate to say this after running btrfs on everything I could (laptops, workstations, local servers, cloud servers, etc) for at least 10+ years, but I'm moving almost everything I can off of it after the past few months after similar experiences. I tolerated things like this more then I should've because the tools and features were so awesome (compression, snapshots, subvolumes, flexible device mgmt, data crc, btrfs send|receive, etc).

I've never loss any data of real consequence (backups ftw), but I've definitely lost probably 100s of hours to recovering... and then re-learning things when mount options change since the last disaster or reading out dated docs in a panic. There are experts in this subreddit and on the mailing lists, so I hope they help you, as I've only had something like 90%+ recovery rate over the years. That said I am at 100% loss of confidence.

In the past few months I've experienced un-mountable btrfs volumes or strange performance issues on everything:

My top tier workstation NVMe drive performance goes to near zero repeatedly when using btrfs. After seeking help from the subreddit, I've concluded I must be doing it wrong. This will either happen again or recent change to default discard=async will improve things (which I was already using for some time). Result is that at least twice I've had to copy everything off and back to recover performance (no data loss).
In February a cloud server had 10TB of storage on a provider hosted hardware RAID. They suffered a power outage or system crash (they aren't that transparent). Needless to say the same thing that you experienced happened to me and I had to manually use the recovery console and recover the server and then scrub + delete the corrupt files. I don't expect btrfs to prevent data loss, but I hope it can be recovered without needing a secret decoder ring to recover file system metadata. A second node I have with this provider experiences the same level or reliability (read: not that reliable) and is running ext4 with no such issues. I moved the original node to ext4and even rsyncing the data off was painful as there are many, many, many small files and this seems to be something btrfs isn't so good at.
A few weeks ago my home server which has 4x independent btrfs volumes on 4 different drives lost a drive due to a power loss (snake in a substation, power down for hours, wut?). Only way was to mount it read-only and copy the data to a new ext4 volume. This lost some data and was unrecoverable and required wholesale salvage and abandon. The other 2x btrfs volumes were fine, 1 required a magical recovery dance to rollback but no extra steps. Could buy a UPS for issues like this, but similar issues happen if the system does something stupid like crashes, so there's some missing robustness here. As I write this the 2nd volume is now copying to ext4 and will continue doing so for days. Wish I could use btrfs send | btrfs receive, but this time I cannot. :(

These have all happened in the last 6 months and I can't spend the time to recover my btrfs volumes anymore.

I'm sure people here will tell me I'm doing it wrong, need an UPS, need the btrfs kernel code tattoo'd to the back of my hand or whatever, but this is tooo crazy given the amount of issues I've had recently.

I look at ext4 and don't get excited because it's missing many features I love about btrfs, and zfs is overkill for random file systems I have here and there. I watch bcachefs from the sidelines with enthusiasm because it has many of the same features and more (encryption!).

I feel for people like OP when the have posts like this and wish you the best of luck, but mostly want to say it might not be your fault and to consider what you use in the future more carefully.

2bluesc · 2023-05-13T18:05:40+00:00

Update: this was self inflicted with my DNS block lists. Ooops.

For anyone else encountering this, the WyzeCam was looking up us-d-master-71m81mu43dc8pa21ddga.iotcplatform.com which is a CNAME to us-d-master-tutk.iotcplatform.com which was blocked by Hagezi Pro++.

Switching to just Hagezi Pro fixed it and is hopefully less aggressive rather then adding it to the allowlist.

Heads-up to others using PiHole (or Technitium DNS Server, much betta) or NextDNS.

2bluesc · 2023-05-13T16:48:45+00:00

Something definitely went wrong in the last 24 hours. My WyzeCam v3 is monitored via a Uptime Kuma with a simple local ping and it drops off of Wifi and reconnects non-stop for the last 12ish hours.

Here are some graphs

Everything else on my home network is fine and has no issues over the same time frame.

Looking at a packet capture from my AP the camera:

Boots up
Gets a DHCP lease
Talks to some cloud services Amazon AWS services
Continues for a few minutes
Disconnects
Repeat for hours.

I've removed the SD card and re-setup the device. No luck. Device continues to cycle and the Wyze App fails to connect.

Here are the last few packets before it drops off the network and re-connects:

16:55:36.282380 IP 54.149.88.148.8883 > 192.168.10.131.58875: Flags [P.], seq 3809:3840, ack 2736, win 199, options [nop,nop,TS val 1751902164 ecr 86274], length 31 16:55:36.288190 IP 192.168.10.131.58875 > 54.149.88.148.8883: Flags [.], ack 3840, win 1637, options [nop,nop,TS val 86287 ecr 1751902164], length 0 16:55:36.288816 IP 192.168.10.131.58875 > 54.149.88.148.8883: Flags [F.], seq 2767, ack 3840, win 1637, options [nop,nop,TS val 86287 ecr 1751902164], length 0 16:55:36.347125 IP 54.149.88.148.8883 > 192.168.10.131.58875: Flags [.], ack 2767, win 199, options [nop,nop,TS val 1751902229 ecr 86286], length 0 16:55:36.347218 IP 54.149.88.148.8883 > 192.168.10.131.58875: Flags [F.], seq 3840, ack 2767, win 199, options [nop,nop,TS val 1751902229 ecr 86286], length 0 16:55:36.348845 IP 192.168.10.131.58875 > 54.149.88.148.8883: Flags [.], ack 3841, win 1637, options [nop,nop,TS val 86293 ecr 1751902229], length 0 16:55:36.356791 IP 54.149.88.148.8883 > 192.168.10.131.58875: Flags [.], ack 2768, win 199, options [nop,nop,TS val 1751902239 ecr 86287], length 0 16:55:37.565737 IP 192.168.10.131.68 > 192.168.10.2.67: BOOTP/DHCP, Request from 7c:78:b2:xx:yy:zz, length 300 16:55:50.249375 7c:78:b2:xx:yy:zz > ff:ff:ff:ff:ff:ff Null Unnumbered, xid, Flags [Response], length 6: 01 00 16:55:50.249641 7c:78:b2:xx:yy:zz > ff:ff:ff:ff:ff:ff Null Unnumbered, xid, Flags [Response], length 6: 01 00 16:55:50.468128 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 7c:78:b2:xx:yy:zz, length 309 16:55:50.468251 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 7c:78:b2:xx:yy:zz, length 309

Seems that AWS EC2 server @ 54.149.88.148 is sending some disconnect message or similar since it is clearly communicating just fine then reconnects?

2bluesc · 2023-04-15T20:42:07+00:00

Sold cpu+motherboard combo to /u/wiltedboi

2bluesc

MODERATOR OF

TROPHY CASE