Testing new Mageia 6 sta1 isos on virtualbox. After installation, the reboot failed with "No bootable medium found". Iso uses stage2 from drakx-installer-stage2-17.33-3.mga6.i586.rpm. Packages installed: grub-0.97-43 (no grub2 packages installed) in ddebug.log file I can see: grub> setup --stage2=/boot/grub/stage2 (hd0) checking if "/boot/grub/stage1" existes... no checking if "/grub/stage1" existes... no Error 14: Filesystem compatibility error, cannot read whole file Same error when trying to reinstall grub. menu.lst looks ok, no error inside I tried then using boot.iso and network install and got the same result. Rindolf and papoteur did test it also and got the same result.
Assignee: bugsquad => zen25000
What filesystem on /boot (or / if you dont have separate boot)
CC: (none) => tmb
CC: (none) => thierry.vignaud
Severity: normal => critical
It's a default install so ext4 (no separate /boot).
Looks like a fallout of the new e2fsprogs, but I dont have time to debug it until tomorrow or so...
CC: (none) => wilcal.int
I just did a USB EFI install of Mageia-6-sta1-x86_64-DVD.iso. The install was done to a harddisk on which I had already created and formatted the partitions to be used. part table gpt /boot/EFI fat32 / reiserfs /home reiserfs All the install had to do was mount the partitions The only issue I had during the install was the need to manually initiate stage2. Upon re-booting after the completed install diskcheck was run. The check took roughly 2 mins but the boot was able to complete to a working desktop. On subsequent re-boots diskcheck was not run.
CC: (none) => cae
Indeed. I checked this yesterday with Barjac. Legacy grub is installed when no EFI required. Otherwise grub2 is installed, which is your case. It seems only installing grub legacy is broken. I've read many things about inode size which is 256 at the moment. This size was max 128 for grub legacy. Still it works on Mageia 5 using grub legacy and 256 inode size.
Assignee: zen25000 => tmb
I'm suspecting this from release-notes Mke2fs will now create file systems with the metadata_csum and 64bit features enabled by default. it seems the metadata_csum was reverted just before the new release, but not the 64bit part
We can always patch /etc/mke2fs.conf but grub is no more maintained and one it just won't be able to cope anymore with upstream kernel/e2fsprogs...
Source RPM: (none) => grub
Source RPM: grub => grub, e2fsprogs
And confirmed. grub legacy trips over the 64bit feature. I guess we should start phasing out grub legacy that leaves the bloated grub2, but I'm not sure we have any choice for now... I dont want to disable the features in e2fsrpogs / new kernels as they improve performance and scalability. I'd suggest for mga6 we dont offer grub legacy anymore att install time, so only people upgrading with urpmi can get it, and we drop it from repos when cauldron re-opens after mga6 is released... That should give people enough transition time
(s/one it/one day it/ in comment #7) OK, I'll adapt drakx to default to grub2. I'll just wait for people to confirm the fixes I restored did bring back update-grub2 (really os-prober) to run under 10mn when there's a couple OSes on other partitions (see bug #16010 and bug #18538)
(In reply to Thomas Backlund from comment #8) > I guess we should start phasing out grub legacy I support that. I haven't used grub legacy for quite some time.
I'm all for it to avoid such problem in coming releases.
Presumed fixed
Status: NEW => RESOLVEDResolution: (none) => FIXED
Blocks: (none) => 416
oops wrong bug
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Blocks: 416 => (none)
CC: cae => (none)
When could we get those modifications. sta1 cannot be released while we do not have it Thanks !
I'll try to get some times tonight. Else I'll have time tomorrow in the evening. In the meantime, you can try this:
Created attachment 7888 [details] disallow grub with ext4 (mga#18583) (untested)
Created attachment 7889 [details] alternative: stop offering grub legacy on new installs (untested)
I've just tested the second patch (stop offering grub legacy on new installs). All the installation is ok. Still I get the error message when rebooting: "GRUB Loading stage1.5 GRUB loading, please wait... internal error: the second sector of Stage2 is unknwn"
Did you perform an update or a new install? The aim was to fix the later. For the former: 1) either you're updating mga5 and it should work as is (keeping grub legacy if you didn't change anything, or offering grub2 if you try to configure the bootloader in the summary stage). 2) or you try to update your previously broken install (ext4 formated with latest e2fsprogs) and booting will still be broken if you didn't configure bootloader at summary step
I did a new install but just did it without modifying summary step. On 2d test I entered summary step about booloader and chose GRUB2 graphical. Reboot was ok
Humm so it still defaulted to grub-legacy... :-(
Not here in Gnome VM net-install just now. I accepted defaults all the way and was offered grub2 which installed fine.
CC: (none) => zen25000
Looking at drakboot in the running system, legacy grub is still offered as options 3 and 4 and / is ext4.
CC: (none) => paiiou
If course as drakxtools hasn't been patched yet...
I'll commit a different patch that only disallow grub legacy on new install, still enabling to alter grub legacy config on already installed systems
Status: REOPENED => ASSIGNEDSummary: Cannot boot after new install: no bootable medium found => Cannot boot after new install: no bootable medium found (grub not supporting newly formated ext4 fs)
commit 6a805889e8d177cee40a4b435195eb56233aa87a Author: Thierry Vignaud <thierry.vignaud@...> Date: Sat Jun 4 15:10:12 2016 +0200 stop offering grub legacy & lilo on new installs rationale: - lilo is no more supported upstream and has been replaced by grub legacy a long time ago - grub-legacy does not support ext4 fses formatted with e2fsprogs-1.43 (mga#18583) --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=6a805889e8d177cee40a4b435195eb56233aa87a
Fixed in git, we now default to grub2
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXEDAssignee: tmb => thierry.vignaud
Attachment 7889 is obsolete: 0 => 1
Just as a side note, I got the same problem with XFS /boot or / (without separated /boot). So if not done already default on grub2 for XFS partitions.
Status: RESOLVED => REOPENEDCC: (none) => mageiaResolution: FIXED => (none)
See : https://bugs.mageia.org/show_bug.cgi?id=18472
Please stop reopening this bug
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
*** Bug 18472 has been marked as a duplicate of this bug. ***
CC: (none) => cbsite01