Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: Repetetive corruption of /boot partition

  1. #11

    Default Re: Repetetive corruption of /boot partition

    It just happened again, and of course it was only the boot partition that got corrupted. I am pretty sure that this is not a hardware problem, by the predictable pattern of this.

    I am really grateful to any suggestions; anyway I will now monitor FS changes in /boot and try to analyze it myself.

  2. #12
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    4,296
    Blog Entries
    1

    Default Re: Repetetive corruption of /boot partition

    ISTR reading somewhere on one of the mailing lists, or maybe here, that a separate /boot/ filesystem in conjunction with BTRFS on / can be a problem, likely having to do with kernels and /lib/modules being on separate filesystems, in conjunction with snapshotting. You might try searching opensuse.org for such a subject.
    Reg. Linux User 211409 *** multibooting since 1992
    Primary: 15.4, TW, 15.1 & 13.1 on Haswell @earthlink.net
    Secondary: eComStation (OS/2) &15.4 on i965P/Radeon
    Tertiary: Debian, Fedora, Mageia, more on Rocket Lake & older Intel, AMD, NVidia....

  3. #13
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    16,126
    Blog Entries
    3

    Default Re: Repetetive corruption of /boot partition

    Quote Originally Posted by mrmazda View Post
    ISTR reading somewhere on one of the mailing lists, or maybe here, that a separate /boot/ filesystem in conjunction with BTRFS on / can be a problem, likely having to do with kernels and /lib/modules being on separate filesystems, in conjunction with snapshotting.
    Yes, that can be a problem. If you do a rollback, then it might rollback the modules but not the kernel itself. That can cause booting problems. But it should not cause file system corruption.
    openSUSE Leap 15.4; KDE Plasma 5.24.4;
    testing Tumbleweed.

  4. #14
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    4,371
    Blog Entries
    5

    Default Re: Repetetive corruption of /boot partition

    Quote Originally Posted by rfactormo View Post
    It just happened again, and of course it was only the boot partition that got corrupted. I am pretty sure that this is not a hardware problem, by the predictable pattern of this. I am really grateful to any suggestions; anyway I will now monitor FS changes in /boot and try to analyze it myself.
    I use this Partitioning. No monitoring required. What is yours?
    openSUSE Tumbleweed, KDE Plasma, Blogs/KeepItSimple, i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X, 5700U (2022)

  5. #15
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    4,371
    Blog Entries
    5

    Default Re: Repetetive corruption of /boot partition

    Quote Originally Posted by nrickert View Post
    Yes, that can be a problem. If you do a rollback, then it might rollback the modules but not the kernel itself. That can cause booting problems. But it should not cause file system corruption.
    Latest Tumbleweed has been canonified:
    Code:
    erlangen:~ # ll /boot 
    total 127672 
    lrwxrwxrwx 1 root root       50 Jul 20 21:09 .vmlinuz-5.18.11-1-default.hmac -> ../usr/lib/modules/5.18.11-1-default/.vmlinuz.hmac 
    lrwxrwxrwx 1 root root       50 Sep 25 20:31 .vmlinuz-5.19.10-1-default.hmac -> ../usr/lib/modules/5.19.10-1-default/.vmlinuz.hmac 
    lrwxrwxrwx 1 root root       49 Sep 12 07:27 .vmlinuz-5.19.8-1-default.hmac -> ../usr/lib/modules/5.19.8-1-default/.vmlinuz.hmac 
    lrwxrwxrwx 1 root root       47 Jul 20 21:09 System.map-5.18.11-1-default -> ../usr/lib/modules/5.18.11-1-default/System.map 
    lrwxrwxrwx 1 root root       47 Sep 25 20:31 System.map-5.19.10-1-default -> ../usr/lib/modules/5.19.10-1-default/System.map 
    lrwxrwxrwx 1 root root       46 Sep 12 07:27 System.map-5.19.8-1-default -> ../usr/lib/modules/5.19.8-1-default/System.map 
    lrwxrwxrwx 1 root root       43 Jul 20 21:09 config-5.18.11-1-default -> ../usr/lib/modules/5.18.11-1-default/config 
    lrwxrwxrwx 1 root root       43 Sep 25 20:31 config-5.19.10-1-default -> ../usr/lib/modules/5.19.10-1-default/config 
    lrwxrwxrwx 1 root root       42 Sep 12 07:27 config-5.19.8-1-default -> ../usr/lib/modules/5.19.8-1-default/config 
    drwxr-xr-x 3 root root     4096 Jan  1  1970 efi
    drwxr-xr-x 1 root root       98 Sep 27 02:20 grub2
    lrwxrwxrwx 1 root root       24 Sep 25 20:31 initrd -> initrd-5.19.10-1-default 
    -rw------- 1 root root 43384726 Sep 25 20:31 initrd-5.18.11-1-default 
    -rw------- 1 root root 43635777 Sep 25 20:31 initrd-5.19.10-1-default 
    -rw------- 1 root root 43638533 Sep 25 20:32 initrd-5.19.8-1-default 
    lrwxrwxrwx 1 root root       48 Jul 20 21:09 sysctl.conf-5.18.11-1-default -> ../usr/lib/modules/5.18.11-1-default/sysctl.conf 
    lrwxrwxrwx 1 root root       48 Sep 25 20:31 sysctl.conf-5.19.10-1-default -> ../usr/lib/modules/5.19.10-1-default/sysctl.conf 
    lrwxrwxrwx 1 root root       47 Sep 12 07:27 sysctl.conf-5.19.8-1-default -> ../usr/lib/modules/5.19.8-1-default/sysctl.conf 
    lrwxrwxrwx 1 root root       25 Sep 25 20:31 vmlinuz -> vmlinuz-5.19.10-1-default 
    lrwxrwxrwx 1 root root       44 Jul 20 21:09 vmlinuz-5.18.11-1-default -> ../usr/lib/modules/5.18.11-1-default/vmlinuz 
    lrwxrwxrwx 1 root root       44 Sep 25 20:31 vmlinuz-5.19.10-1-default -> ../usr/lib/modules/5.19.10-1-default/vmlinuz 
    lrwxrwxrwx 1 root root       43 Sep 12 07:27 vmlinuz-5.19.8-1-default -> ../usr/lib/modules/5.19.8-1-default/vmlinuz 
    erlangen:~ #
    Modules and kernels belong to the same package installed in subvolume of @/.snapshots.
    openSUSE Tumbleweed, KDE Plasma, Blogs/KeepItSimple, i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X, 5700U (2022)

  6. #16
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    4,371
    Blog Entries
    5

    Default Re: Repetetive corruption of /boot partition

    Quote Originally Posted by rfactormo View Post
    It just happened again, and of course it was only the boot partition that got corrupted.
    Substantiate this claim by running a file system check:
    Code:
    erlangen:~ # btrfs check --force /dev/nvme0n1p2 
    Opening filesystem to check... 
    WARNING: filesystem mounted, continuing because of --force 
    Checking filesystem on /dev/nvme0n1p2 
    UUID: 0e58bbe5-eff7-4884-bb5d-a0aac3d8a344 
    [1/7] checking root items 
    [2/7] checking extents 
    [3/7] checking free space tree 
    [4/7] checking fs roots 
    [5/7] checking only csums items (without verifying data) 
    [6/7] checking root refs 
    [7/7] checking quota groups skipped (not enabled on this FS) 
    found 484195385344 bytes used, no error found 
    total csum bytes: 465784716 
    total tree bytes: 2198863872 
    total fs tree bytes: 1505411072 
    total extent tree bytes: 128335872 
    btree space waste bytes: 460178833 
    file data blocks allocated: 1207237996544 
     referenced 529045770240 
    erlangen:~ #
    openSUSE Tumbleweed, KDE Plasma, Blogs/KeepItSimple, i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X, 5700U (2022)

  7. #17
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    16,126
    Blog Entries
    3

    Default Re: Repetetive corruption of /boot partition

    Quote Originally Posted by karlmistelberger View Post
    Modules and kernels belong to the same package installed in subvolume of @/.snapshots.
    Yes. But booting still uses then from "/boot". And the "initrd" is still only on "/boot".

    If you know what you are doing, then after a rollback you could copy the needed kernels to "/boot" and remake the "initrd". That would allow you to still boot.

    This won't help with the file system corruption that the OP is seeing.
    openSUSE Leap 15.4; KDE Plasma 5.24.4;
    testing Tumbleweed.

  8. #18

    Default Re: Repetetive corruption of /boot partition

    Quote Originally Posted by rfactormo View Post
    It just happened again, and of course it was only the boot partition that got corrupted. I am pretty sure that this is not a hardware problem, by the predictable pattern of this.

    I am really grateful to any suggestions; anyway I will now monitor FS changes in /boot and try to analyze it myself.
    @rfactormo:

    A couple of people, myself included, pointed to the issue of the formatting of the /boot/efi partition as a potential source of "corruption" . . . . Looks like karlmistelberger's set up also uses "vfat"???

    I mentioned "FAT32" . . . another poster mentioned "ext2" . . . those are "suggestions" . . . .

  9. #19
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    31,777

    Default Re: Repetetive corruption of /boot partition

    Quote Originally Posted by non_space View Post
    @rfactormo:

    A couple of people, myself included, pointed to the issue of the formatting of the /boot/efi partition as a potential source of "corruption" . . . . Looks like karlmistelberger's set up also uses "vfat"???

    I mentioned "FAT32" . . . another poster mentioned "ext2" . . . those are "suggestions" . . . .
    Aren't you confusing /boot with /boot/efi? Please re-read all those posts carefully.
    Henk van Velden

  10. #20

    Default Re: Repetetive corruption of /boot partition

    Quote Originally Posted by hcvv View Post
    Aren't you confusing /boot with /boot/efi? Please re-read all those posts carefully.
    @hcvv:

    The OP is "experienced user" . . . but my recent post was essentially a re-post on the data, as a courtesy to the OP . . . . It's possible that the formatting of the EFI partition has nothing to do with their issue . . . but it is/was the most obvious problem of possible error, and it was "suggested" . . . but OP didn't seem to respond to those several suggestions on that detail.

    Too busy to re-read the whole thread. I still think there was a formatting issue that grub isn't handling too well . . . hence "the corruption" . . . O . . . the corruption that continues to corrupt the proceedings.

Page 2 of 3 FirstFirst 123 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •