• 1 Post
  • 17 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle
  • I don’t think its rpi or network switch, unless you’ve overclocked rpi with liquid nitrogen 😅. So, I assume its TrueNas device.

    If it were a significant power difference, say 20-30 watts, you could easily find the process using htop/iotop. However, 6 watt difference is a relatively small value for a device with ~25 watts of idle power . It might be a process using just 1% system resources. That’s why I would look for systemd timers, cronjobs etc. to find scheduled tasks on specific times. Another possibility is automated S.M.A.R.T. self-tests. Those tests don’t show up in htop or iotop.



  • UPS devices normally uses wall (input) power, and switches to battery when input voltage is out of the target thresholds. So, input.load should represent the percentage of current wall power (in VA) relative to UPS’s max rated input power (VA). If your devices uses more power, input power from wall should increase as well.

    If it’s peaking in certain times, it could be due some scheduled job temporarily increase CPU frequency, or automated tasks like file system snapshot might power-up/spin drives longer than regular usage.


    • 2x18k - mirrored ZFS pool.
    • 1x47k - 2.5" drive from an old laptop used for torrents, temp data, non-critical pod volumes, application logs etc.
    • 1x32k - automated backups from ZFS pool. It’s kinda partial mirror of the main pool.
    • 1x18k - (NVME) OS drive, cache volumes for pods.

    Instead of single pool, I simply split my drives into tiers: cache, storage, and trash due to limited drive counts. Most R/W goes to the cheap trash and cache disks instead of relatively new and expensive NAS drives.



  • I have a APC Back-UPS 1600VA. It powers two desktop PC/Server, a monitor, and router. So far, it gets the job done.

    The biggest downside is; battery is not user replaceable, at least it’s not straight forward like the other models. If possible, prefer a UPS with the easy battery replacement option.





  • I was a backend developer for a startup company where:

    • Windows servers without any firewall and security hardening.
    • Docker swarm without WSL. We had to use 4 GB Windows base images for 50MB web apps.
    • MSSQL without any replication and backups.
    • Redis installed on Windows via 3rd-party tool that looked like a 2010 era keygen generator.
    • A malware exploited the Redis * what a surprise * and kept killing processes to mine crypto on CPU…
    • VPS provider forgot to activate new Windows Server on production and it kept restart for every 30 minutes until I checked the logs and notified them about the missing license.

    I left there after 6 months.


  • Biggest difference is being able to execute INSTCMD commands, at least that was the main reason why I developed my own tool. Another less important differences are: older ARM support and since it’s written in Rust, it’s much more efficient in terms of resource usage. TBH, being that efficient only makes sense for very low-power devices.

    Besides that, I don’t think you can go wrong with either project.