bugGNU GRUB - Bugs: bug #61233, grub 2.06 (fedora 34) grub-core...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #61233: grub 2.06 (fedora 34) grub-core kern disk_common.c:47 attempt to read or write outside of disk

Submitter:  czipis <czipis>
Submitted:  Mon 27 Sep 2021 11:45:02 AM UTC
   
 
Category:  Booting Severity:  Major
Priority:  5 - Normal Item Group:  Software Error
Status:  None Privacy:  Public
Assigned to:  None Originator Name: 
Open/Closed:  Open Release:  other
Release:  Reproducibility:  Every Time
Planned Release:  None

Thu 30 Sep 2021 06:29:51 PM UTC, comment #4: 

issue can be closed. fedora already built new version containing the xfs patch.

thank you for pointing me to right direction.

czipis <czipis>
Wed 29 Sep 2021 09:24:34 AM UTC, comment #3: 

Thank you guys for your help.

I've opened a bug for it here https://bugzilla.redhat.com/show_bug.cgi?id=2008819

czipis <czipis>
Wed 29 Sep 2021 03:36:57 AM UTC, comment #2: 

Upstream GRUB doesn't stop for keypress by default after showing the full screen ("paging"). Fedora tried to upstream this change but we refused exactly for the reasons like this.

Vladimir Serbinenko <phcoder>
Group administrator
Wed 29 Sep 2021 12:05:46 AM UTC, comment #1: 

It looks like vgDATA-data has an XFS filesystem. XFS was recently broken and I believe that's the cause of your issue. Since you're not booting of vgDATA-data it doesn't cause your boot to fail.

If this is indeed the XFS bug, its been fixed in master. You can check this by making sure that the xfs module is not loaded in your grub config and see if the issue persists. And then you may want to check in with Fedora to prompt them to include the XFS fix in their GRUB build.

g10
Mon 27 Sep 2021 11:45:02 AM UTC, original submission:  

After upgrading from fedora 33 (grub 2.04-31.fc33) to fedora 34 (grub 2.06-2.fc34) there is a problem with booting.
even before grub menu appears 2 pages with errors are shown

> grub-core kern disk_common.c:47 attempt to read or write outside of disk 'vgDATA/data'


it stops booting and waits with "--- more ---" for confirmation.
When SPACE is pressed it prints second page of (same) errors and then it displays boot menu and then boots normally.

It is annoying for unattended reboots.


after downgrading to grub 2.04 there is no problem.


my system is UEFI


# efibootmgr -v
BootCurrent: 0002
Timeout: 3 seconds
BootOrder: 0002,0003,0000,0001
Boot0000* fedora        HD(2,GPT,9e678c91-3cb0-45b5-ab32-b5e20273ea2b,0x1000,0x64000)/File(\EFI\FEDORA\GRUBX64.EFI)
Boot0001* fedora        VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0002* Fedora        HD(2,GPT,9e678c91-3cb0-45b5-ab32-b5e20273ea2b,0x1000,0x64000)/File(\EFI\FEDORA\SHIM.EFI)..BO
Boot0003* Fedora        HD(2,GPT,dd87a1a0-b777-4b0e-a530-961b6d1cff5d,0x1000,0x64000)/File(\EFI\FEDORA\SHIM.EFI)..BO



# lsblk -f
NAME              FSTYPE            FSVER    LABEL            UUID                                   FSAVAIL FSUSE% MOUNTPOINT
sda
└─sda1            linux_raid_member 1.2      htpc:pv00        ed9d6557-404a-245e-e3b4-e7f5df3f2f77
  └─md127         LVM2_member       LVM2 001                  b2MQUA-pP2f-a88t-fDPe-RPEJ-6LZ1-qQUfHl
    └─vgDATA-data xfs                        data             8485f753-6164-4f64-b910-e536b92a819a      231G    92% /data
sdb
└─sdb1            linux_raid_member 1.2      htpc:pv00        ed9d6557-404a-245e-e3b4-e7f5df3f2f77
  └─md127         LVM2_member       LVM2 001                  b2MQUA-pP2f-a88t-fDPe-RPEJ-6LZ1-qQUfHl
    └─vgDATA-data xfs                        data             8485f753-6164-4f64-b910-e536b92a819a      231G    92% /data
sdc
├─sdc1
├─sdc2            vfat              FAT16    EFI_SSD          0CF8-2CFC                               193.8M     3% /boot/efi
└─sdc3            linux_raid_member 1.2      htpc.mydomain.:0 d6429df4-3bbb-2319-16ea-23ac007a5cef
  └─md0           LVM2_member       LVM2 001                  ptLTWI-3z1B-66nO-JsMr-4W68-XMxq-PdWv9d
    ├─vg00-root   ext4              1.0                       f57c2086-54ab-4336-a25b-6dc2d4f23af2     44.1G    55% /
    └─vg00-swap   swap              1                         5bbe40af-3967-4a8c-917a-869784dab23e                  [SWAP]
sdd
├─sdd1
├─sdd2            vfat              FAT16    EFI_SSD2         B69E-2E20                               193.8M     3% /boot/efi-sync2
└─sdd3            linux_raid_member 1.2      htpc.mydomain.:0 d6429df4-3bbb-2319-16ea-23ac007a5cef
  └─md0           LVM2_member       LVM2 001                  ptLTWI-3z1B-66nO-JsMr-4W68-XMxq-PdWv9d
    ├─vg00-root   ext4              1.0                       f57c2086-54ab-4336-a25b-6dc2d4f23af2     44.1G    55% /
    └─vg00-swap   swap              1                         5bbe40af-3967-4a8c-917a-869784dab23e                  [SWAP]



# gdisk -l /dev/sdc
GPT fdisk (gdisk) version 1.0.8

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 500118192 sectors, 238.5 GiB
Model: SAMSUNG SSD PM85
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): DB229221-4542-4E45-B1DA-5A00C0D24995
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 500118158
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048            4095   1024.0 KiB  EF02  BIOS boot partition
   2            4096          413695   200.0 MiB   EF00  EFI System
   3          413696       500118158   238.3 GiB   FD00  Linux RAID



# blkid
/dev/mapper/vg00-root: UUID="f57c2086-54ab-4336-a25b-6dc2d4f23af2" BLOCK_SIZE="4096" TYPE="ext4"
/dev/md0: UUID="ptLTWI-3z1B-66nO-JsMr-4W68-XMxq-PdWv9d" TYPE="LVM2_member"
/dev/sdc3: UUID="d6429df4-3bbb-2319-16ea-23ac007a5cef" UUID_SUB="1ccfa6fd-162b-7629-6558-ae3402eeb980" LABEL="htpc.mydomain.com:0" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="5e44ecaf-a3a9-46d1-a32d-7b9d4ed04680"
/dev/sdd3: UUID="d6429df4-3bbb-2319-16ea-23ac007a5cef" UUID_SUB="8e10a8bd-9ad4-912a-13ff-59d81632920e" LABEL="htpc.mydomain.com:0" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="496d14e8-7b55-4160-a58c-a0a8965fc749"
/dev/sda1: UUID="ed9d6557-404a-245e-e3b4-e7f5df3f2f77" UUID_SUB="2b85087e-4d2f-3cee-52b7-6143b74e001f" LABEL="htpc:pv00" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="aa60058f-28b5-44d7-b2db-ad24f68ae084"
/dev/sdb1: UUID="ed9d6557-404a-245e-e3b4-e7f5df3f2f77" UUID_SUB="725a8c07-e75a-b3da-8fc3-f4173fc92e5a" LABEL="htpc:pv00" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="a1bf480b-5941-4ac7-8feb-621cb1dc74a3"
/dev/sdc1: PARTLABEL="BIOS boot partition" PARTUUID="0dfe30af-d4e3-4ef5-a515-c5d0bb4eb1e7"
/dev/sdc2: SEC_TYPE="msdos" LABEL_FATBOOT="EFI_SSD" LABEL="EFI_SSD" UUID="0CF8-2CFC" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System" PARTUUID="9e678c91-3cb0-45b5-ab32-b5e20273ea2b"
/dev/sdd1: PARTLABEL="BIOS boot partition" PARTUUID="be582e0d-b2a0-4829-819f-cb10fe9e4ae2"
/dev/sdd2: SEC_TYPE="msdos" LABEL_FATBOOT="EFI_SSD2" LABEL="EFI_SSD2" UUID="B69E-2E20" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="dd87a1a0-b777-4b0e-a530-961b6d1cff5d"
/dev/md127: UUID="b2MQUA-pP2f-a88t-fDPe-RPEJ-6LZ1-qQUfHl" TYPE="LVM2_member"
/dev/mapper/vg00-swap: UUID="5bbe40af-3967-4a8c-917a-869784dab23e" TYPE="swap"
/dev/mapper/vgDATA-data: LABEL="data" UUID="8485f753-6164-4f64-b910-e536b92a819a" BLOCK_SIZE="512" TYPE="xfs"


czipis <czipis>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by phcoder (Posted a comment)
  • -email is unavailable- added by g10 (Posted a comment)
  • -email is unavailable- added by czipis (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code