Res Publica Non Dominatur!

I’m just this guy, y’know?

In your interwebs, janitorializing things up and keeping the porns online.

  • 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: August 18th, 2025

help-circle
  • Mine would be when I had a 48 bay disk array / JBOD fail on me… badly. After a storm, it killed the larger card that allowed for me to get many of the drives into a PCIe 16x slot, and I was relegated down to only getting ~8 disks per box made from spare hardware. A single box I got 16 going. Add to this mix an SSD for mid-line caching.

    These were all running bcache on top of mdraid… One single mount.

    Yes I understand how obnoxiously stupid it was to run RAID6 on a 48 disk volume. It was almost all just stuff I could re-acquire over time, not irreplaceable things.

    I just HAD to solve this one though.

    In come several spare chassis / mobo etc… get a bunch of drives powered and on /dev/ , move to the next.

    A couple spare gigabit switches…

    several gigabit NICs…

    two explicit paths for each machine…

    a bit of iSCSI magic, and one machine now had the physical disks all exposed to it… mdadm --assemble blah blah, bit of UUID chaos…

    It’s surprising that while a bit speed limited (I think I got just around 110MB/sec reads), it was nicely performant for what a huge mess of wires and disks just strewn out around my rack.

    Managed to evacuate all I needed without much issue once I got that going. Now, I try to keep my arrays under 16 drives at a time, or keep a very rigid policy of “I can lose this and don’t care” vs “this box gets RAID10 and/or offsite backups nightly”.

    back up your critical stuff people!


  • root@kamidake:~# for i in /dev/sd? ; do echo $i; smartctl -a $i |grep Hours| awk ’ { print $10/8760}'; done

    /dev/sda

    15.6055

    /dev/sdb

    15.6979

    /dev/sdc

    6.04909

    /dev/sdd

    7.35708

    /dev/sde

    10.618

    /dev/sdf

    7.28071

    /dev/sdg

    10.5689

    /dev/sdh

    10.6264

    /dev/sdi

    2.28311

    /dev/sdj

    10.7498

    /dev/sdk

    10.5832

    /dev/sdl

    7.35502

    /dev/sdm

    10.643

    /dev/sdn

    10.8016

    /dev/sdo

    10.7558

    /dev/sdp

    9.11416

    root@kamidake:~#

    These are running ZFS and I have 2 other boxes with similar, most in the 10-12 year range. Spinning drives.

    Good stuff.











  • Seeing most of the negative comments here noting bare metal etc.

    Moving to the AIO build solved literally every issue I had with the single exception being the colabora office stuff.

    For the image stuff, basic file, download etc… been great.

    The Android app gives me grief, but I suspect that’s my janky Samsung phone killing it’s permissions.

    Considering they only officially support the AIO, it’s worth trying that out before passing full judgement. It has flaws, for sure, but it’s immensely complex and the AIO nullifies many of the variables that they can’t otherwise account for easily.



  • Elegoo petg and PLA have become my go-to over the past 2 years. Rapid vs pro tend to affect me more with how brittle the end product is than printing speed. I’m using a K2 Plus, but also printed on Anker M5C.

    Fun detail: you can order 10kg packs for a good discount vs other shops if you hit their site directly.

    My only gripe is they don’t have variety packs of their fancier stuff. Some of their silk is gorgeous.

    I usually have gotten about 35-40% rh on my should out of the bag. I still get good quality at that level, but would warn to actively dry a bit if you are in a more humid area for sure.