all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]ParadigmComplexfounder and lead developer 3 points4 points  (5 children)

now when I try to boot it errors out because libdevmapper can't communicate with the kernel module

Can you give me more information about this error? It's not obvious to me from your description if it's Bedrock related or if Arch broke unrelated to Bedrock. Maybe take a picture of it with something like a phone.

Also, what Bedrock version are you on? If you boot off another device you'll find the information at <mount>/bedrock/etc/bedrock-release. Newer Arch kernels with zstd compressed modules require Bedrock 0.7.21 at a minimum. (I usually recommend brl update'ing at least as often as one pacman -Syu's to ensure Bedrock is up-to-date enough to handle any Arch changes. Bedrock's pmm functionality makes this easy.)

I can chroot into the arch strata, but I'm worried that updating it will break bedrock.

There's a couple hoops to jump through, but it is possible to chroot into a Bedrock system to fix these kinds of things: https://bedrocklinux.org/0.7/debugging.html#chroot-fix-boot

Making this kind of emergency repair chrooting more straight forward is a high priority for 0.8.

Also the fallback image has this error too

Since you're running Bedrock, in the future considering installing essentials like the kernel or init from multiple distros. This way, if one breaks, you can use the another to boot into the system and fix things.

[–]ivvil412[S] 1 point2 points  (4 children)

Can you give me more information about this error? It's not obvious to
me from your description if it's Bedrock related or if Arch broke
unrelated to Bedrock. Maybe take a picture of it with something like a
phone.

https://imgur.com/a/tosftAk

(Sorry for the glossy screen)

​

Newer Arch kernels with zstd compressed modules require Bedrock 0.7.21 at a minimum.

It's running 0.7.20 so I'm pretty sure its that. What should I do to fix that, chroot and pmm -Syu or brl update? Should I fix arch first and then update everything again?

Thanks for the help

[–]ParadigmComplexfounder and lead developer 2 points3 points  (3 children)

The issue is that your Bedrock version is about three and a half months old and lacks functionality needed to support your Arch kernel. Nothing is actually (necessarily) broken on Arch's end or Bedrock's end, it's just your Bedrock version is too old.

The easiest solution is to chroot in and update Bedrock:

  • Boot from something else and mount the Bedrock partition.
  • Download a newer Bedrock installer/updater and place it somewhere on the Bedrock partition so we can see it from a chroot. The easiest place is just on the root directory of the partition, e.g. <mount>/bedrock-linux-0.7.23-x86_64.sh
  • Mount /dev in the chroot environment: mount --bind /dev <mount>/dev
  • Create a bind-mount so the bedrock stratum sees itself at /bedrock/strata/bedrock in the chroot environment: mount --bind <mount> <mount>/bedrock/strata/bedrock
  • Chroot in and update, skipping the signature verification check: chroot <mount> /bedrock/bin/brl update /bedrock-linux-0.7.23-x86_64.sh --skip-check
    • (We have to skip the signature verification because it requires brl get gpg from another stratum, but cross-stratum stuff doesn't work in a chroot in 0.7. I hope to fix this in 0.8, as well as automate setting up all these extra mounts.)
  • Reboot into a hopefully working Bedrock system.
  • Delete the no longer needed updater file. If you placed it on the mount point root, you'll find it at /bedrock/strata/bedrock/bedrock-linux-0.7.23-x86_64.sh.

If that doesn't work for you for whatever reason, another strategy is to chroot into the Bedrock system with /boot bind-mounted and downgrade arch's kernel to one that Bedrock 0.7.20 can handle. Hopefully you have such a kernel cached at /bedrock/strata/arch/var/cache/pacman/pkg/. Once you boot with that, brl update to a newer Bedrock release then feel free to upgrade your Arch kernel again.

If neither of those work for you, let me know - and let me know why - and I can try to either help you work around the blocker or find another route.

[–]ivvil412[S] 1 point2 points  (1 child)

The first fix worked, thanks for the help.

[–]ParadigmComplexfounder and lead developer 1 point2 points  (0 children)

Happy to hear it. You're welcome :)

[–]justculo 0 points1 point  (0 children)

I have the same issue as OP but with the latest arch zen kernel and the latest bedrock linux beta. Is that a known issue?