Bootloader-Konfiguration wegen Problem mit Snapshots nicht aufrufbar

Hallo,

beim Aufruf der Bootloader-Konfiguration vom aktuellen Tumbleweed erscheint diese Meldung:

YaST kann den Bootloader nicht konfigurieren, weil der Fund vom root-Dateisystem fehlgeschlagen ist.

command '/usr/bin/lsattr -d
/tmp/libstorage-Dj46J0/tmp-mount-rGytVx/@/.snapshots/972/snapshot' failed:

stderr:
/usr/bin/lsattr: Input/output error while trying to stat
/tmp/libstorage-Dj46J0/tmp-mount-rGytVx/@/.snapshots/972/snapshot

exit code:

Diese Snapshots sind in der btrfs-Partition vorhanden:

# btrfs subvolume show /
@/.snapshots/1/snapshot
        Name:                   snapshot
        UUID:                   1d3c32fb-d380-c145-b4a8-c8ef322e3919
        Parent UUID:            -
        Received UUID:          -
        Creation time:          2023-12-15 16:57:57 +0100
        Subvolume ID:           265
        Generation:             78085
        Gen at creation:        27
        Parent ID:              264
        Top level ID:           264
        Flags:                  -
        Send transid:           0
        Send time:              2023-12-15 16:57:57 +0100
        Receive transid:        0
        Receive time:           -
        Snapshot(s):
                                @/.snapshots/972/snapshot
                                @/.snapshots/973/snapshot
                                @/.snapshots/1092/snapshot
                                @/.snapshots/1093/snapshot
                                @/.snapshots/1100/snapshot
                                @/.snapshots/1101/snapshot
                                @/.snapshots/1104/snapshot
                                @/.snapshots/1105/snapshot
                                @/.snapshots/1116/snapshot
                                @/.snapshots/1117/snapshot
                                @/.snapshots/1118/snapshot
                                @/.snapshots/1119/snapshot
                                @/.snapshots/1160/snapshot
                                @/.snapshots/1161/snapshot
                                @/.snapshots/1162/snapshot
                                @/.snapshots/1163/snapshot
        Quota group:            0/265
          Limit referenced:     -
          Limit exclusive:      -
          Usage referenced:     4.00KiB
          Usage exclusive:      16.00KiB

Allerdings wird der betroffene Snapshot 972 (und auch 973) nicht bei snapper gelistet:

# snapper list

    # │ Typ    │ Vorher # │ Datum                        │ Benutzer │ Verwendeter Platz │ Bereinigen │ Beschreibung          │ Benutzerdaten
──────┼────────┼──────────┼──────────────────────────────┼──────────┼───────────────────┼────────────┼───────────────────────┼──────────────
   0  │ single │          │                              │ root     │                   │            │ current               │
   1* │ single │          │ Fr 15 Dez 2023 16:57:57 CET  │ root     │               0 B │            │ first root filesystem │
1092  │ pre    │          │ Mi 07 Aug 2024 16:23:04 CEST │ root     │               0 B │ number     │ zypp(zypper)          │ important=yes
1093  │ post   │     1092 │ Mi 07 Aug 2024 16:23:16 CEST │ root     │               0 B │ number     │                       │ important=yes
1100  │ pre    │          │ So 11 Aug 2024 10:30:27 CEST │ root     │               0 B │ number     │ zypp(packagekitd)     │ important=yes
1101  │ post   │     1100 │ So 11 Aug 2024 10:31:31 CEST │ root     │               0 B │ number     │                       │ important=yes
1104  │ pre    │          │ So 11 Aug 2024 16:31:08 CEST │ root     │               0 B │ number     │ zypp(packagekitd)     │ important=yes
1105  │ post   │     1104 │ So 11 Aug 2024 16:33:31 CEST │ root     │               0 B │ number     │                       │ important=yes
1116  │ pre    │          │ Fr 16 Aug 2024 17:30:11 CEST │ root     │               0 B │ number     │ zypp(packagekitd)     │ important=yes
1117  │ post   │     1116 │ Fr 16 Aug 2024 17:34:45 CEST │ root     │               0 B │ number     │                       │ important=yes
1118  │ pre    │          │ Fr 16 Aug 2024 19:49:59 CEST │ root     │               0 B │ number     │ zypp(zypper)          │ important=yes
1119  │ post   │     1118 │ Fr 16 Aug 2024 19:50:12 CEST │ root     │               0 B │ number     │                       │ important=yes
1160  │ pre    │          │ Sa 17 Aug 2024 21:00:21 CEST │ root     │               0 B │ number     │ zypp(packagekitd)     │ important=no
1161  │ post   │     1160 │ Sa 17 Aug 2024 21:00:56 CEST │ root     │               0 B │ number     │                       │ important=no
1162  │ pre    │          │ So 18 Aug 2024 11:22:54 CEST │ root     │               0 B │ number     │ yast bootloader       │
1163  │ post   │     1162 │ So 18 Aug 2024 11:24:04 CEST │ root     │               0 B │ number     │                       │

Beim Versuch den Snapshot 972 trotzdem zu löschen, erscheint diese Meldung:

# snapper delete 972
Schnappschuss '972' wurde nicht gefunden.

Die btrfs-Partion sieht so aus:

# mount
...
/dev/nvme0n1p4 on /.snapshots type btrfs (rw,relatime,ssd,discard=async,space_cache=v2,subvolid=264,subvol=/@/.snapshots)
/dev/nvme0n1p4 on /boot/grub2/i386-pc type btrfs (rw,relatime,ssd,discard=async,space_cache=v2,subvolid=263,subvol=/@/boot/grub2/i386-pc)
/dev/nvme0n1p4 on /usr/local type btrfs (rw,relatime,ssd,discard=async,space_cache=v2,subvolid=258,subvol=/@/usr/local)
/dev/nvme0n1p4 on /srv type btrfs (rw,relatime,ssd,discard=async,space_cache=v2,subvolid=259,subvol=/@/srv)
/dev/nvme0n1p4 on /root type btrfs (rw,relatime,ssd,discard=async,space_cache=v2,subvolid=260,subvol=/@/root)
/dev/nvme0n1p4 on /opt type btrfs (rw,relatime,ssd,discard=async,space_cache=v2,subvolid=261,subvol=/@/opt)
/dev/nvme0n1p4 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,ssd,discard=async,space_cache=v2,subvolid=262,subvol=/@/boot/grub2/x86_64-efi)
/dev/nvme0n1p4 on /var type btrfs (rw,relatime,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/@/var)
...

Wie kann ich das Problem beheben?

Startest du mit einem Schnappschuss?

Nein, das tue ich nicht.

Dann poste mal komplett:

cat /etc/fstab

In den syslogs gab es beim Hochfahren keine btrfs-Fehler, aber nach dem Aufruf der Bootloader-Konfig (bad tree block) :

# dmesg|grep -i btrfs
[    1.746749] [    T430] Btrfs loaded, assert=on, zoned=yes, fsverity=yes
[    6.522244] [    T665] BTRFS: device fsid 9c4a32a7-7d63-410e-a664-7f05b818965f devid 1 transid 78260 /dev/nvme0n1p4 (259:4) scanned by mount (665)
[    6.522418] [    T665] BTRFS info (device nvme0n1p4): first mount of filesystem 9c4a32a7-7d63-410e-a664-7f05b818965f
[    6.522432] [    T665] BTRFS info (device nvme0n1p4): using crc32c (crc32c-intel) checksum algorithm
[    6.522436] [    T665] BTRFS info (device nvme0n1p4): using free-space-tree
[   48.321780] [    T120] BTRFS error (device nvme0n1p4): bad tree block start, mirror 1 want 49556701184 have 0
[   48.321858] [    T120] BTRFS error (device nvme0n1p4): level verify failed on logical 49556701184 mirror 2 wanted 2 found 0
[   48.365885] [    T120] BTRFS error (device nvme0n1p4): bad tree block start, mirror 1 want 49529143296 have 0
[   48.365908] [    T120] BTRFS error (device nvme0n1p4): bad tree block start, mirror 2 want 49529143296 have 0
[   48.365941] [    T120] BTRFS error (device nvme0n1p4): bad tree block start, mirror 1 want 49529143296 have 0
[   48.365961] [    T120] BTRFS error (device nvme0n1p4): bad tree block start, mirror 2 want 49529143296 have 0
[   48.366002] [    T120] BTRFS error (device nvme0n1p4): bad tree block start, mirror 1 want 49556701184 have 0
[   48.366068] [    T120] BTRFS error (device nvme0n1p4): level verify failed on logical 49556701184 mirror 2 wanted 2 found 0
[   48.366098] [    T120] BTRFS error (device nvme0n1p4): bad tree block start, mirror 1 want 49556701184 have 0
[   48.366164] [    T120] BTRFS error (device nvme0n1p4): level verify failed on logical 49556701184 mirror 2 wanted 2 found 0
[   50.314949] [    T120] BTRFS error (device nvme0n1p4): bad tree block start, mirror 1 want 49529143296 have 0
[   50.314978] [    T120] BTRFS error (device nvme0n1p4): bad tree block start, mirror 2 want 49529143296 have 0
[   56.869199] [    T114] BTRFS error (device nvme0n1p4): bad tree block start, mirror 1 want 49529143296 have 0
[   56.869227] [    T114] BTRFS error (device nvme0n1p4): bad tree block start, mirror 2 want 49529143296 have 0
[   56.869265] [    T114] BTRFS error (device nvme0n1p4): bad tree block start, mirror 1 want 49529143296 have 0
[   56.869286] [    T114] BTRFS error (device nvme0n1p4): bad tree block start, mirror 2 want 49529143296 have 0
[   56.869327] [    T114] BTRFS error (device nvme0n1p4): bad tree block start, mirror 1 want 49556701184 have 0
[   56.869395] [    T114] BTRFS error (device nvme0n1p4): level verify failed on logical 49556701184 mirror 2 wanted 2 found 0
[   56.869430] [    T114] BTRFS error (device nvme0n1p4): bad tree block start, mirror 1 want 49556701184 have 0
[   56.869496] [    T114] BTRFS error (device nvme0n1p4): level verify failed on logical 49556701184 mirror 2 wanted 2 found 0

Ich habe inzwischen Tumbleweed neu installiert und die betroffene Partition dabei formatiert. Nun läuft’s wieder.

Trotzdem vielen Dank für die Hilfe!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.