[Bug 1237519] Re: Grub2 fails to install to non-standard device path

[Kent Baxley]

Attaching a full log from an installation.  Right now, we're having to
base things on 13.04 because we're having problems getting a working
kernel module for the fusionio device on the 3.11-based kernels in 13.10
and higher.

Steps taken:

1) Copy driver packages to a USB stick with the OEMDRV driver disk format. 
2) Insert the driver disk and installation media.
3) add "anna/choose_modules=driver-injection-disk-detect" to the boot command line so drivers will load and we have a device available in step #4
4) Auto-partition the resulting fioa device. 
5) Also copy the updated grub-installer script in comment #13 to /usr/bin/ inside the installer environment so grub-install dummy doesn't crash at the end. 
6) Reboot the server and drop to an efi shell.  The fusion-io.efi drivers must be loaded in by hand at this point. 
7) Once the device is present in the efi firmware, navigate to the EFI\ubuntu directory and attempt to execute grubx64.efi.   

At that point we are presented with an error message that states "no
such device xxxxx-xxxxx-xxxx", where xxx is the uuid of the disk.  From
there we are dropped to a grub rescue prompt.  Running 'ls' in grub
rescue gives is (hd0) (hd1) (hd2) with no partitons available.



** Attachment added: "logs.tar.gz"
   https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1237519/+attachment/3888966/+files/logs.tar.gz

-- 
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/1237519

Title:
  Grub2 fails to install to non-standard device path

Status in “grub2” package in Ubuntu:
  Incomplete

Bug description:
  Running the Ubuntu Server installer in UEFI mode fails to install the
  Grub bootloader.  Attached is the syslog output that shows grub-
  installer failed with error code 1.  I have seen this on Ubuntu 12.04,
  12.10, and 13.04.  I believe the problem is that Grub is looking for
  device paths that match something like '/dev/sdX' or '/dev/hdX' but
  the device I am installing to does not follow that convention.

  The reason I believe it is looking for specific devices paths is if,
  during installation after my device has been partitioned, I escape
  into the shell (using alt+f2) and create a hard link from my device
  name and its partitions, to a device name that matches 'sdX', then
  Grub begins to install.  For example, if my device name is /dev/fioa
  and has partitions /dev/fioa1, /dev/fioa2, and /dev/fioa3, I map those
  partitions to something like /dev/sdc, /dev/sdc1, /dev/sdc2, and
  /dev/sdc3 and continue with the installation onto /dev/sdc.  By doing
  this, Grub will begin to install on the device.

  Possibly useful background information:

  - The operating system and all files install just fine without
  problem, it is the last step of installing the bootloader that fails.

  - In order to have the device recognized during installation, I either
  need to run 'insmod' from a terminal or we have to manually modify
  initrd to include our .ko file because it is not a standard disk
  driver.  Using either method does not affect the outcome of Grub2
  failing to install.

  - Even though grub begins to install after creating the hard links
  mentioned above, it does not finish successfully due to the linked
  paths (e.g. /dev/sdc) not being in the device map.  That is a separate
  issue, but may be expected behavior and would likely need a separate
  ticket if it needed to be reported at all.

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