Skip to content

A new Archlinux upgrade, a new unbootable system

It’s that time again…

First my grub broke. So I had to type my config manually:

root (hd0,0)
kernel /vmlinux26 root=/dev/mapper/lvmopraid-root
initrd /kernel26.img
boot

Then my logical volumes can’t be found. Type this in the recovery shell:

lvm lvchange -a e lvmopraid

I commented on an archlinux bug about this.

And then nothing started anymore on boot, because everything is migrating to systemd (as opposed to systemv), without telling me… Still working on fixing that.


    6 Comments ( Add comment / trackback )

    1. (permalink)
      Comment by Rowan Rodrik
      On February 16, 2013 at 15:34

      How far into the ten year timeline of that bet are we? I’m afraid things aren’t going very well for my side of the wager.

    2. (permalink)
      Comment by halfgaar
      On March 3, 2013 at 21:22

      A late reply, but never late than never.

      I really don’t remember when the bet was. I do know that I’m right 🙂

    3. (permalink)
      Comment by Rowan Rodrik
      On March 4, 2013 at 17:45

      In think around 2006.

    4. (permalink)
      Comment by Rowan Rodrik
      On March 4, 2013 at 17:47

      What does “never late than never” mean, by the way? Something along the lines of “I’m too tired to type”?

    5. (permalink)
      Comment by halfgaar
      On March 5, 2013 at 10:25

      That is recursive reasoning, designed to give you a stack overflow.

    6. (permalink)
      Comment by halfgaar
      On May 16, 2013 at 08:49

      And I did another upgrade, and I have a unbootable system again. This time it doesn’t assemble the RAID array (even though the mdadm hook and tool are included in the initramfs) and therefore can’t find the lvm root. When it drops to a recovery shell, type:

      mdadm --assemble --scan
      exit

      If the cure is that simple, why is it so fucking hard to get it right? I’m really getting sick of this shit.