@Brandon,

I was able to successfully boot into 12.04.  The trick, I think, is that
you need two sets of driver disks in order to pull this off.

I tested this on a PowerEdge C8000 series server, which allowed me to
boot trouble-free into an EFI shell to load the Fusion-io.efi module.

The reason is because there are two kernels involved on this daily image
of 12.04.  The installer kernel is running 3.8.0-29 while the final
kernel that gets installed is 3.8.0-35.   Since the kernel modules are
built for a specific kernel, I'm guessing what happened to you was that
you had 3.8.0-29 drivers but didn't have any for the 3.8.0-35 kernel,
thus, when the OS tried to boot it fell down on you.

Here's what I did:

1) Because of this situation, I had to create kernel modules for both
3.8.0-29 and 3.8.0-35, create packages,  and put the respective packages
on my driver disk USB stick.

2) Once those were in place, I booted up with the kernel command line
"anna/choose_modules=driver-injection-disk-detect"

3) I verified both sets of kernel modules were installed.  The installer
picked up the fioa device and I  could install without trouble..grub
gave me no problems.

4) Once that was done, I rebooted into an EFI shell, loaded the Fusion-
IO module, then booted from grubx64.efi on the FIO device.

5) From the grub prompt I saw an "efidisk write error".  This can be
safely ignored and after a few seconds the Operating Sytem booted up
just fine from the fioa disk partitions.

So, 12.04.4's daily builds are indeed good to go from the testing I was
able to do.

I'll send along the packages I used along with the steps I used to boot
this machine up successfully.

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

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

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to