• 0 Posts
  • 22 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • smartctl --scan | awk '{print $1}' | xargs -I {} sh -c 'echo -n "{}: "; smartctl -A {} | awk "/Power_On_Hours/ {printf \"%.2f years\n\", \$10/8760}"'

    /dev/sda: 0.30 years #14TB WD Elements (shucked)
    /dev/sdb: 2.64 years #8TB WD My Book (shucked)
    /dev/sdc: 12.37 years #3TB WD Red
    /dev/sdd: 2.86 years #12TB My Book (shucked)
    /dev/sde: 13.47 years #3TB WD Red
    /dev/sdf: 1.26 years #14TB WD Elements (shucked)
    /dev/sdg: 10.55 years #5TB WD Red
    

    Most of these drives served on Windows Server bare metal w/ StableBit DrivePool + SnapRAID before migrating to Proxmox mergerfs + SnapRAID & ZFS. My raidz1 pool has a combine total of 36+ years lol. Yes I do have backups. :)


  • Yes I read it when it first came out, and again after a recent update. It’s very opinionated and I remain unconvinced the criticisms amounts to very much. At the least, certainly not to the point where words like nazi and fascist should be thrown around!

    For example, I dislike Yarin’s and Lunduke’s politics but I did at least watched Yarin’s interview. (Did you? It was boring, and entirely tech-oriented, nothing controversial at all.) But… trial by association I guess. And anyway, it’s not the article itself I have a problem with - it’s the borrowing of second-hand opinions as if they should be your own. Sometimes, it’s prudent to reserve judgement (until ‘verifying every single thing’), or criticise specific ideas, without leaping to ad hominem per consortium.


  • I find it wild in this day and age how questions like (“why do WE hate” such and such) are being asked in the first place, then answered through one person’s opinion piece mindlessly linked from all angles. Please, for gawd sake, stop listening to random fedditors/redditors about what opinions you should adopt!

    IMHO (<- there’s a novel approach), the criticisms of FUTO are just as biased and political as FUTO themselves, and everyone should be sceptical of bias from all sides. Apparently, focusing on ‘privacy, decentralization, and right to repair’ - is being too political, and they’re not allowed to have a philosophical take on what they imagine successful open source to be. (Incidentally, I’m not necessarily on FUTOs side, just pissed off at the nature of social media to obviate the need of critical thinking and make everything black or white.)


  • announced

    What announcement? There’s been a new Personal Plus plan around for several months already - introduced without much fanfare, and simply brings the user count from 3 to 6 for a fixed small fee. Presumably this is due to feedback from personal users wanting to contribute something other than nothing.

    Where do you see the free Personal plan has changed at all?


  • custom domain

    From what I gather, this refers to the email address you sign up with.

    If you use something like a non-gmail email address when signing up, it starts you off on the business plan with a trial (which you can instantly change to free). (Note: they’re gonna change this auto-detection thing with shared domains soon due to a security hole.)

    I believe you can still use a custom domain (instead of the randomised *.ts.net provided one) with DNS lookups in your tailnet, on the personal (free) plan.


  • Droolio@feddit.uktoSelfhosted@lemmy.world•TIL - Caddy
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 years ago

    Do ignore me then, I assumed you might know the reference and only I mean’t it in good humour. :) (Without spoiling anything - in the unlikely event you might some day watch it - Mr Milchick is a character that uses ‘big words’. Your choice of words struck a chord.) I will say though, you’re seriously missing out. The cinematography alone is brilliant and the acting exceptional.



  • Multiple backups may be kept.

    Nice work, but if I may suggest - it lacks hardlink support, so’s quite wasteful in terms of disk space - the number of ‘tags’ (snapshots) will be extremely limited.

    At least two robust solutions that use rsync+hardlinks already exist: rsnapshot.org and dirvish.org (both written in perl). There’s definitely room for backup tools that produce plain copies, instead of packed chunk data like restic and Duplicacy, and a python or even bash-based tool might be nice, so keep at it.

    However, I liken backup software to encryption - extreme care must be taken when rolling and using your own. Whatever tool you use, test test test the backups. :)


  • There’s no point doing anything fancy like that - wireguard over Tailscale is pretty pointless, as Tailscale is literally wireguard with NAT traversal and authentication bolted on. Unless you enable subnetting, it can’t get more secure than that.

    And even if you do enable subnetting (which you might wanna do if you need access to absolutely everything), you can use Tailscale ACLs to keep tighter control - say, from specific (tagged) devices.



  • 100% this. OP, whatever solution you come up with, strongly consider disentangling your backup ‘storage’ from the platform or software, so you’re not ‘locked in’.

    IMO, you want to have something universal, that works with both local and ‘cloud’ (ideally off-site on a own/family/friend’s NAS; far less expensive in the long run). Trust me, as someone who came from CrashPlan and moved to Duplicacy 8 years ago, I no longer worry about how robust my backups are, as I can practice 3-2-1 on my own terms.




  • You should take it to a data recovery specialist if the data is really really important but for lightly-damaged sectors, you want ddrescue (oldie but goodie) or HDDSuperClone (no longer developed) or OpenSuperClone (fork of HDDSuperClone, more actively developed).

    You can combine some of these tools with commercial programs like dmde, UFS Explorer, or R-Studio - to target specific files for a quick result - but basically it’s best to get a full disk image off the bad drive onto another drive/image.






  • Yes, I also work in IT.

    The paid GUI version is extremely cautious on the auto-updates (it’s basically a wrapper for the CLI) - perhaps a bit too cautious. The free CLI version is also very cautious about making sure your backup storage doesn’t break.

    For example, they recently added zstd encryption, yet existing storages stay on lz4 unless you force it - and even then, the two compression methods can exist in the same backup destination. It’s extremely robust in that regard (to the point that if you started forcing zstd compression, or created a new zstd backup destination, you can use the newest CLI to copy data to the older lz4 method and revert - just as an example). And of course you can compile it yourself years from now.