I am not a robot. I promise.

  • 3 Posts
  • 126 Comments
Joined 2 years ago
cake
Cake day: July 9th, 2023

help-circle
  • That wouldn’t have mattered either way, whether the tear area was properly perforated or not from the factory, or whether I would have done it myself.

    I perfectly cut where it should have been cut with scissors, but still the zipper was poorly adhered to the bag, weaker adhesive than the zipper itself, so the zipper itself still peeled loose from the bag.

    I anticipated something might go wrong, hence the photo before I even tried to open it, plus I already had a generic zipper bag handy before even trying to open it.

    Put it this way, the turkey won’t be going to waste…





  • Nah, not meant to be perforated, but is meant to have a dotted line printed above that yellow instructions bar. The package did have the pre-slit cuts on both ends, in the appropriate location where I ultimately just decided to cut it instead, as I’ve seen all too many of those sort of tear open zipper bags just tear miserably wrong and ruin the whole package.

    Sigh, even after like perfectly cutting the bag on the intended area where the dotted line should have been, still the zipper was barely adhered to the bag and the whole zipper peeled loose, making the built in zipper ultimately still useless ☹️

    Hey, at least I pay attention for potentially defective resealable packaging though, the turkey sure ain’t gonna go to waste.

    I’ve also seen other zipper bag issues with shredded cheese, where the two sides of the zipper don’t even line up and can never actually seal. I just fold those bags over like 3 or 4 times at the end and use a chip bag clip on those.

    Also, why is it that cardboard cereal boxes and similar with the quick rip strip are almost always glued right under the part that’s supposedly meant to easily and quickly rip loose?

    Sigh, too many mildly infuriating things on my mind to keep adding to this list…






  • I hear ya there, but…

    I be getting really confused when one config boots from /dev/sda, but when I have my backup drive attached (not the boot device), it boots from /dev/sdb

    Hell I dunno, I probably confused the hell out of my laptop plus myself with my cutout mod reconfiguration, but it’s happy to boot from almost anything now.

    Almost…

    Hey, at least I know how to restore to my previous state from backup via dd 👍




  • My 128GB is meant as an integrated NVME drive.

    Meant to be. I literally cut a service panel hole under the laptop to remove or reinstall it whenever I feel like, or maybe eventually upgrade it.

    I’ve been booting off of other devices, like my 8GB USB flash, 100GB USB HDD, and even Live Boot USB DVD drive. It’s actually been very convenient, as I can boot off of whatever the hell I want from USB.

    My backup is on a 4TB, so really no worries to me, I can more or less freely experiment around with whatever OS I want, and if it doesn’t work right, I can just dd my backup over whatever again, and it just works.

    But why doesn’t the dd 100GB>128GB work as I’d expect?

    Obviously that’s not the exact dd command I used, for privacy reasons.

    🤷


  • The goal was to migrate the 100GB to the 128GB, hopefully expand it, and format the 100GB for future temporary/experimental use.

    I never planned on having both drives actively running at the same time, so I don’t think there should have been any UUID issues, nor did I run across any errors suggesting such an issue.

    But even without expanding the partition, the dd command should have 1:1 copied the 100GB, with space to spare, and be bootable, right? Or so I thought…

    I had no problem dd restoring the original 128GB contents though, so at least I didn’t bork everything. Also the 100GB external USB is still fine. 👍

    🤷


  • You sound like you know some things that perhaps I don’t know.

    Slightly different question…

    I have a 128GB SSD with Linux Mint MATE 20.3, and I did a full and successful dd backup to my 4TB backup drive.

    I have a 100GB external USB hard drive as a test medium for Mint MATE 22.1. I am happy with my test setup, and tried to dd that over to the 128GB SSD. But it wouldn’t boot.

    I restored the original 128GB SSD image and all is good right now, but why the hell didn’t the 100GB>128GB even boot?

    Edit: Secure Boot has been disabled all along, screw that headache.






  • over_clox@lemmy.worldtoSelfhosted@lemmy.worldTape drive backups
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    2
    ·
    5 months ago

    Tapes can have long term issues in storage, as the tape reel winds will eventually start to bleed over magnetic signals from one wind to the next.

    In analog world, they call it tape hiss. In digital world, with good error correction, it can last a long time, but is still ultimately prone to data corruption, eventually…

    I recommend a video surveillance rated multi terabyte hard drive, they’re designed to run 24/7. I have two 4TB Seagate Skyhawks.