• verdigris@lemmy.ml
    link
    fedilink
    arrow-up
    6
    ·
    3 months ago

    I don’t think lack of precaution was the issue here given that it was an unexpected power failure, but it is a fairly easy fix with a chroot.

    • Scipitie@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      2
      ·
      3 months ago

      Oh agreed! That’s why I’m with OP actually that arch might not be the right distro to go for.

      The person I replied to basically said “that’s what you deserve for not doing it properly” if I understood it correctly - that’s what I’m confused about as well.

      • verdigris@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        3 months ago

        Yeah it seems half the commenters missed OP’s clarifying comment and just think he started a kernel update with 2% battery life.

        • Scipitie@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          1
          ·
          3 months ago

          Hehe true. And even that happened to me after a couple of tired “Syu enter”. But then again I learned something new with nearly every repair!

    • badloop@discuss.online
      link
      fedilink
      arrow-up
      3
      arrow-down
      3
      ·
      edit-2
      3 months ago

      If you know your battery is shot and you don’t have a way to save your install if the power goes out, then you just don’t update. There are plenty of ways to protect against this that have already been mentioned (battery backup, backup kernel, etc). OP was just playing with fire.

      • verdigris@lemmy.ml
        link
        fedilink
        arrow-up
        5
        ·
        3 months ago

        That’s kind of overzealous. I would expect most desktop users to run kernel updates without being plugged into a UPS, this is functionally identical. It’s not like it’s an unrecoverable error, but yeah if you’re updating a critical system you should have redundancies in place.