• 0 Posts
  • 43 Comments
Joined 1 year ago
cake
Cake day: July 26th, 2023

help-circle

  • i bought a few smr drives, knowing they were smr. they were cheaper, a lot cheaper than the same amount of space in cmr. used only for static media storage, so that’s not a big deal, really., but holy hell was it slow getting stuff on them initially.

    i have a few self-powered externals that are also smr (quite common with those as they use 2.5in notebook hdd). when those things have to start shuffling bits around and rewriting tracks, sustained write speeds fall well under what even usb2 can send.


  • i bought a big external hdd recently on impulse… a clearance sale. it was really, really cheap. with the thinking that i could ‘shuck’ it because i’m short on space in a couple storage systems. i checked. i can, but i haven’t. hell, i haven’t even used it yet other than to run a full smart diag on it, followed by a full format and a read/write verify. took days. then i put it back in the box and have basically forgotten about it until now.

    you have to be careful on what models you buy. some have usb built onto the controller board (no internal sata) or other things (e.g. encryption chip, weird power) that make it more difficult or even impossible to use the internal drive in an environment other than the enclosure it ships in.


  • ares35@kbin.socialtoLinux@lemmy.ml[QUESTION] Flatpak or AUR?
    link
    fedilink
    arrow-up
    14
    ·
    edit-2
    6 months ago

    on my arch-based systems, i use repos first, aur second. appimages third. i do also have a couple minor things (that are self-contained with no dependencies) that were just ‘unzipped’ into their own directories and links added to menus where appropriate. note that i don’t game on these systems. i don’t have a lot of aur packages installed, so updates and subsequent recompile time isn’t an issue.

    i have yet to run into anything i want or need that isn’t available in those. so no flatpaks or snaps.


  • hard drives are going to be slow af copying data to itself, or moving data to a different partition on it.

    then you’re also adding partition size manipulation to the mix, which will also be slow af when data has to be moved off the ‘end’ of partitions to ‘make room’ to enlarge or create another with a different fs.

    your best option is to get another drive, even if it’s also a hard drive instead of ssd. use that to move (copy, really, to preserve the original as a backup for the time being) all the data to that you want to preserve.