I'm pretty sure that the "Oct 24 03:33:28 grub-installer: invalid
numeric value" error comes from grub-install running efibootmgr against
the Fusion-IO device. The naming scheme, of course, for that adapter
is /dev/fioa1...the grub-install script, however, runs the following at
around line 892:
efidir_part="$(echo "$efidir_drive" | sed 's/^([^,]*,[^0-9]*//; s/[^0-9].*//')"
efibootmgr $efi_quiet -c -d "efidir_disk" -p "$efidir_part" -w\
-L "$bootloader_id" -l "\\EFI\\$efi_distributor\\$efi_file"
It looks like the regex search is returning basically a null value for
efidir_part, thus, the "-p" parameter in efibootmgr isn't valid. The
regex seems to be tailored for traditional devices such as /dev/sda1,
which does return a sane value.
Ultimately, though, this isn't the total cause of efibootmgr not working
properly...if I go in and 'hard code' the -p value to 1 then re-run grub
install against the fusion IO card, efibootmgr still doesn't seem to
want to add the device to its list. Even just running efibootmgr by
hand also produces the same result.
--
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/grub2/+bug/1237519/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
