[Bug 1918265] Re: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2

[ben]

Forgot to add the part about data corruption, kernel images and initrd
used by grub and systemd-boot are absolutly identicals:

4188eea45cdb76ebe2b313aef0ac9d7d3f2772cdcf536798b2eeef64fd33a810  vmlinuz-5.8.0-44-generic
4188eea45cdb76ebe2b313aef0ac9d7d3f2772cdcf536798b2eeef64fd33a810  efi/1c1f1f7eb0df44baa7b6399299ee251a/5.8.0-44-generic/linux

4fba2fb3cf0a46cfb839687d5431850473bcc702a1334ffc9dfb7aa06bd76694  initrd.img-5.8.0-44-generic
4fba2fb3cf0a46cfb839687d5431850473bcc702a1334ffc9dfb7aa06bd76694  efi/1c1f1f7eb0df44baa7b6399299ee251a/5.8.0-44-generic/initrd


And the file-systems seems clean

root at ubuntu-template:/# e2fsck /dev/disk/by-uuid/94ebc17e-6aca-4e42-b489-b3eaa8a32d90 
e2fsck 1.45.5 (07-Jan-2020)
/dev/disk/by-uuid/94ebc17e-6aca-4e42-b489-b3eaa8a32d90: clean, 313/65536 files, 63289/262144 blocks

root at ubuntu-template:/# fsck.vfat /dev/disk/by-uuid/3AA9-F317 
fsck.fat 4.1 (2017-01-24)
/dev/disk/by-uuid/3AA9-F317: 34 files, 69881/130812 clusters


Also the issue is happening on another 2012R2 cluster, but on this one i cannot even start the installation process, this is very weird

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1918265

Title:
  Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2

Status in grub2 package in Ubuntu:
  New

Bug description:
  Hi,

  We are experiencing some weird boot issues with Ubuntu 20.04 and
  Hyper-V 2012r2.

  In two cases the installation started successfully, as did the VM
  initial boot and then issues started to arise, where the boot process
  started to fail.

  grub start, the menu pop-up and then just after loading kernel and
  initrd (tried to put some echo(es) in the config the VM somehow reset
  and the menu pop-up back again.

  After a few of thoses either the VM shut-down or the boot is
  successfull, It seems completly random..

  Here it is captured on video:
    https://www.youtube.com/watch?v=5Bk3S-YGDZk

  If i setup a direct EFI-STUB boot of the kernel+initrd the boot
  process works every times.

  I suspected the "save_env/load_env" for a while but a stripped down
  grub.cfg give the same result..

  > insmod gzio
  > insmod part_gpt
  > insmod ext2
  > set root='hd0,gpt2'
  > if [ x$feature_platform_search_hint = xy ]; then
  >  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  94ebc17e-6aca-4e42-b489-b3eaa8a32d90
  > else
  >  search --no-floppy --fs-uuid --set=root 94ebc17e-6aca-4e42-b489-b3eaa8a32d90
  > fi
  > linux	/vmlinuz-5.8.0-44-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro nosplash elevator=noop 
  > initrd	/initrd.img-5.8.0-44-generic
  > boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265/+subscriptions