FS#63656 - [grub] unable to grub-install (2.04) on btrfs partitionless disk
Attached to Project:
Arch Linux
Opened by christophe yayon (cyayon) - Wednesday, 04 September 2019, 14:23 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 29 March 2022, 23:08 GMT
Opened by christophe yayon (cyayon) - Wednesday, 04 September 2019, 14:23 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 29 March 2022, 23:08 GMT
|
Details
Description:
unable to grub-install (2.04) on btrfs partitionless disk # grub-install /dev/sda Installing for i386-pc platform. grub-install: warning: your core.img is unusually large. It won't fit in the embedding area. grub-install: error: filesystem `btrfs' doesn't support blocklists. The system could be potentially unbootable ! no issue with previous grub 2.02. If i create a /dev/sda1 partition, no problem. Additional info: * package version(s) : grub 2.04 * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: just grub-install on a partitionless btrfs disk |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Tuesday, 29 March 2022, 23:08 GMT
Reason for closing: Fixed
Additional comments about closing: grub 2:2.06-5
Tuesday, 29 March 2022, 23:08 GMT
Reason for closing: Fixed
Additional comments about closing: grub 2:2.06-5
https://wiki.archlinux.org/index.php/Btrfs#Partitionless_Btrfs_disk
> grub-install: warning: your core.img is unusually large. It won't fit in the embedding area.
This comes from https://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/fs/btrfs.c?id=386128648606a3aa6ae7108d1c9af52258202279#n2143, and indicates that core.img grew in size beyond what is assumed to be a reasonable maximum; This should also break other non-btrfs related embeds where the embedding area is small - some targets are even smaller than btrfs' embedding area.
The i386-pc core is a heavily size restricted core in grub, per its docs, and shall not be this large.
I can also reproduce this on other distros, however, so this must be an upstream bug.
I plan to bisect grub to figure out what caused core.img to grow by a non-negligible amount, and then file an upstream bug report if nobody beats me to it. I couldn't find a detailed existing report about this specifically.
I am almost convinced it would be a good idea to roll back this grub version until this is fixed upstream, this is literally broken software breaking people's actual boot *right now*.
Anyway... downgrading to 2.02 and sticking with that forever is not an option.
[0] https://wiki.archlinux.org/index.php/Btrfs#Partitionless_Btrfs_disk
As far as i can tell, upstream is thinking about this and may or may not do something about this - until then, people upgrading are automatically left with unbootable systems.
SAD :(