URL: <https://savannah.gnu.org/bugs/?66777>
Summary: GRUB stopped being able to open my BTRFS filesystem
Group: GNU GRUB
Submitter: gnutoo
Submitted: Tue 11 Feb 2025 01:27:42 AM UTC
Category: Filesystem
Severity: Major
Priority: 5 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: Git master
Release:
Reproducibility: None
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Tue 11 Feb 2025 01:27:42 AM UTC By: GNUtoo <gnutoo>
Hi,
I use GRUB as a Coreboot payload (built either with GNU Boot or Guix,
I can share the package definition if needed).
I've the following disk layout:
/dev/sda1
|-> LUKS 1
|-> LVM PV / VG
|-> data (ext4, data)
|-> rootfs (btrfs, Guix x86_64 on one of the subvolumes)
|-> recovery (ext4, Trisquel 11 x86_64)
Few days ago, the GRUB built from GNU Boot didn't manage to open my
btrfs rootfs anymore (I can't do ls / in grub on that filesystem).
However I can access the btrfs filesystem once I booted on the
Trisquel 11 recovery partition / installation. On Trisquel 11, btrfs
check also found no issues. And I can also boot on my Guix
installation if I copy the kernel, initramfs on an ext4 partition and
that I load a newly created grub.cfg that has the new paths for these
files, but this will stop working as soon as I update the system.
I managed to reproduce the issue with both GRUB 2.12 and GRUB
6811f6f09 ("tpm2_key_protector: Enable build for powerpc_ieee1275")
that I both built with Guix.
For grub 2.12 I used the grub-coreboot package to make a payload, and
for the later I can share the packages if needed as it was not
straightforward as I needed to also package the gnulib used by GRUB
6811f6f09.
This happened to me in the past and the issue was probably gone after
some system update, but as we rely on GRUB in GNU Boot, leaving less
technical users to deal with potential isssue like that is not a good
idea, so I'd like to help trying to debug it, and so far the issue is
there at every boot, so debugging it looks doable.
The problem is that I've no idea how to start debugging the issue.
For instance I didn't find some equivalent to 'sudo tune2fs -l
/dev/[...]' for BTRFS?
Also is there some debug I can add in GRUB? As for getting the output,
I could create a package for cbmemc and output it to a file. If that
doesn't work I could probably manage to use some usb serial adapters
(this computer has no UART on its SuperIO), or at worse EHCI debug.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66777>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
