Re: Dangerous installation of bullseye: What shall i do next?
Am 26.03.2022 um 23:45 schrieb Andrew M.A. Cater:
>> 3. Furthermore, it installed a grub2 version, that is buggy and which
>> cannot boot the bootentries, i was used to resort to in case of trouble
>> (a.k.a. booting straight from an ISO image as an emergency system. The
>> version installed was known to fail to boot on my kind of hardwae since
>> several years, and i assumed (my mistake), that a stable debian would
>> have been fixing the issue by now. (I refer to the links at the bottom).
>>
> I've just spent an evening testing media: grub2 works well. UEFI would
> install grub-efi which also works. Grub-efi with secure boot also works
> for both Buster and Bullseye.
>
After more than six months, i am coming to revisit this issue. in the
meantime, i had prevented (with apt-mark hold) any more updates to any
grub package. But i felt, now would be the time to check it again, so i
permitted (while still on buster) to upgrade grub from 2.02 to
2.06-3+deb10u1 and immediately, my ISO files stopped booting (yet
again!), thus killing my emergency safeguard. :-(
This time, there is no refind anymore, as i went back to relying on
grub2 only. (When i say grub2, i mean grub-efi and all the related
packages.)
And since time advanced, i was able to use a virtualbox machine to
recreate the problem and take a screenshot of the error message. It
states: "Out of memory. No server. Load kernel first." (in german, though)
But that points to my old issue being still present.
(https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311) for reference
To recreate: use UEFI boot and a boot stanza like this:
> ### BEGIN /etc/grub.d/39_myISO_SOS ###
> menuentry "Ubuntu 20.04 Desktop ISO (interne hd0 disk, die ZFS kann)" {
> insmod part_gpt
> insmod ext2
> # vielleicht noch nicht nötig, weil noch grub 2.02 im Einsatz ist? :
> #grub_platform
> if test "" = "efi"; then
> rmmod tpm
> fi
>
> search --no-floppy --fs-uuid --set=root 1a4db22f-65e4-476a-b7e3-8f9f91cf0b8b
> # search -n -l --set=root
> # set root='(hd0,gpt3)'
>
> insmod part_gpt
> insmod ext2
> if test "" = "efi"; then
> rmmod tpm
> fi
> set isofile="/mnt/Ubuntu-NotSystem.iso"
> # set isofile="ubuntu-mate-21.10-desktop-amd64.iso"
>
> loopback loop ($root)$isofile
> linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile noprompt noeject toram noswap locale=de_DE.UTF-8 setkmap=de console-setup/layoutcode=de --
> initrd (loop)/casper/initrd
> # linux (loop)/casper/vmlinuz boot=casper iso-scan/filename= quiet splash
> # initrd (loop)/casper/initrd
> }
This exact stanza used to work on grub 2.02 without any issues!
Now, i would like to learn from you, how are you booting ISO files on
bullseye (or buster) with current grub2? I seem to be unable to ...
... although RAM cannot be the problem, there are 128GB of ECC-RAM,
which is more than enough to copy-to-RAM an ISO. ... methinks
DdB
Reply to: