• DefederateLemmyMl@feddit.nl
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    5 months ago
    • Boot to usb
    • Mount your root filesystem
    • arch-chroot your mounted root filesystem
    • mount /boot
    • mkinitcpio -p linux

    Steps 1,2 and 3 are the entry way to solve all “unbootable Arch” problems by the way, presuming you know what needs to be changed to fix it of course.

  • qjkxbmwvz@startrek.website
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    When I used Arch I updated once and it removed the running kernel and its modules. So when I plugged in a webcam it didn’t work, since the module was gone.

    Not a catastrophe, but it was an off-putting user experience coming from Debian. Arch felt more like a desktop OS, Debian feels more like a server OS to me (updates generally warn/confirm when you need to restart services or the machine).

    To each their own! Having more up to date stuff was a nice perk of running Arch, certainly.

      • qjkxbmwvz@startrek.website
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        5 months ago

        Oh I love Debian on the desktop! More a comment on the feeling of the OS being very concerned about downtime and stability, with minimal “surprises.” Not a bad thing at all!

  • Undearius@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    This got me looking to see if there is any way to have a fallback as I have had something similar happen to me.

    The general advice is to have a liveboot USB around. I even saw that you can have GRUB simply boot from an .iso file on the internal drives, which eliminates the need to keep a USB stick around.

    I haven’t followed the steps yet but I’ll give this a shot because it intrigues me.

    https://www.linuxbabe.com/desktop-linux/boot-from-iso-files-using-grub2-boot-loader

  • FQQD@lemmy.ohaa.xyzOP
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    I think I didn’t make it clear enough: My laptop was on the power during the update process, when the power randomly cut out - for the first time in about 6 years, it doesn’t happen often. Of course you can interpret it as user error - but I think it’s reasonable to update my system when plugged into, normally reliable power. The laptop battery is pretty much dead, so it would’ve shut itself down automatically anyway.

      • superkret@feddit.org
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        5 months ago

        Any immutable distro, Debian, Ubuntu, all their derivatives, Fedora, all its derivatives, OpenSUSE, Slackware, …
        Basically, 95+% of installed Linux systems would retain the old or a backup kernel during an upgrade.

        • rudyharrelson@lemmy.radio
          link
          fedilink
          arrow-up
          1
          ·
          5 months ago

          Any immutable distro, Debian, Ubuntu, all their derivatives

          Debian and Ubuntu are not immutable distributions by default, unless I am mistaken.

    • octopus_ink@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 months ago

      I don’t really get why you couldn’t pick one of your other installed kernels and boot that, but you seem pretty intent on blaming arch and I don’t feel like trying to troubleshoot it, so that’s that I guess.

    • SaharaMaleikuhm@feddit.org
      link
      fedilink
      arrow-up
      1
      ·
      5 months ago

      How dead are we talking here? Even on an older laptop a kernel update doesn’t take that long. Should have just kept it going, hoping for the best.