aims team mailing list archive

[wangyu <1229738@xxxxxxxxxxxxxxxxxx>]

hello mkukri. 
 yes i can post a install config here, but the vmware workstation pro is freely accessed product in case if you don't know, so you can easily reproduce this,i guess.
 and i think this maybe a different case after today's use in that configure. becasue i have see multiple entry in refind bootloader or grub2, any of them can lead me into system. just need manualy chosen one of them every bootup time.
let's start with creat VM. everything is normal.
  ISO version is 24.04.5, 
  processer num 2, 2 core per cpu.
  16 GB RAM.
  bridge network.
  LSI logic I/O. 20GB SCSI driver.
 click create, add two scsi driver as big as before one. change firemware to UEFI. that's all about VM configure.
 then boot and select "Ubuntu Server with the HWE kernel", normally proceed until "storage configuration", select "custom storage layout".
 select sda as "Use as boot device",select sdb & sdc as "Add as another boot device". 
 on every hard driver's free space, select "Add GPT Partition", chang format to "Leave unformatted".the move to "create" and hit enter.
 after everything is done, select "Create software RAID (md)".
 change RAID level to 5. use all 3 partitions. hit "create".
 select new created md0, hit "Add GPT Partition", hit "create".
 now we should have two path setted. the root "/", and "/boot/efi" which located on very first "bootdevice", i.e. sda. "available device " should has nothing left in it. then we hit "done" at very bottom part.
 then proceed to install system, wait till installer tell you to reboot. just reboot.
 we should get into Ubuntu smoothly, fresh installed system, everything looks fine. then we type reboot and hit enter.
 Boom. we get into GRUB rescure mode.
 if typeing "ls", onyl 6 items comming up as (proc) (memdisk) (md/0) (hd0) (hd0,gpt2) (hd0,gpt1).
 that's it. cyber magic.

-- 
You received this bug notification because you are a member of AIMS,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1229738

Title:
  grub doesn't boot with efi and md raid root

Status in grub2 package in Ubuntu:
  Incomplete

Bug description:
  dick@reordberend:/tmp$ lsb_release -rd
  Description:	Ubuntu 12.04.3 LTS
  Release:	12.04

  dick@reordberend:/tmp$ apt-cache policy grub-efi-amd64
  grub-efi-amd64:
    Installed: 1.99-21ubuntu3.10
    Candidate: 1.99-21ubuntu3.10

  
  Installed 12.04.3 LTS Server using md raid1 for root partition on x86-64 box using EFI boot.

  
  Grub installs its EFI app correctly, and it launches at boot.  However, grub can't find the root partition.  Inspecting grub's config shows that it has prefix and root set to the EFI boot partition.  Manually setting those to the raid1 root partition at the grub prompt and running normal allows booting to proceed correctly (ie following the instructions at http://www.gnu.org/software/grub/manual/html_node/GRUB-only-offers-a-rescue-shell.html works).

  
  In EFI mode, grub seems to expect its grub.cfg and modules to be in the EFI partition.  However, they are all installed in the root filesystem.  The problem can be solved in the grub-install script by giving an embedded config to grub-mkimage (http://www.gnu.org/software/grub/manual/html_node/Embedded-configuration.html).  grub-install already has support for this, but it fails if the root partition is raided.

  Inside grub-install, if devabstraction_module is set (and with md as
  the root partition it will be) then config_opt_file is never set.  The
  attached patch solves the bug for me but will doubtless require
  refining to be generally applicable.

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