What's something you just learned, that you should have known for a while? - eviltoast
  • radix@lemm.ee
    link
    fedilink
    arrow-up
    103
    ·
    1 year ago

    Don’t mess around with partitions on your disk when it’s past midnight, you’re extremely stressed, and you don’t have (easily accessible) backups.

    • the_third@feddit.de
      link
      fedilink
      arrow-up
      15
      ·
      1 year ago

      Yes, that does sound like good advice even from a morning, first coffee is brewing kind of viewpoint.

    • x4740N@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      ·
      1 year ago

      Additionally don’t do maintenance on your computers when tired, learned from experience

        • x4740N@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          edit-2
          1 year ago

          I was doing phyical maintenance on a old laptop of mine where I fried a cable because I plugged the battery in and forgot to plug that cable in but I forgot to unplug the battery before plugging that cable in and ended up frying a cable when plugging it back in

          Luckily it was only the cable that got fried

          But that’s in the past now

    • Zikeji@programming.dev
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      Ha, I don’t fuck around with anything that make break my PC or phone until a weekend with no commitments comes up.

    • KSP Atlas@sopuli.xyz
      link
      fedilink
      arrow-up
      7
      ·
      1 year ago

      I once tried partitioning the disk i was running on because i was new and didnt know that wouldn’t work, cfdisk now has a warning if you try to do that

    • hactar42@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      I had to extend the boot drive on a VM that also happened to run the application our entire company used to make products. This was back in the day when extending VM drives took forever because of the way the hypervisor worked. I only had a small window to do this between our Europe plants going offline and the US plants starting up.

      So I used a community tool that would extend the drive in seconds. Turn the VM back on and queue “NTLDR is missing”. I also discovered that the backups for that server hadn’t completed successfully in so long there was nothing to restore from. In my effort to save 30-45 minutes, cost me 8 hours completely rebuilding the server and a day of lost production in the US plants.