It may be UEFI
Some of the known x86_64 UEFI 2.x firmwares are Phoenix SecureCore Tiano, AMI Aptio, Insyde H2O.
For more info on UEFI boot install & repair - Regularly Updated :
Please use Thread Tools above first post to change to [Solved] when/if answered completely.
=================== PARTITIONS & DISKS:
sda1 : sda, maybesepboot, no-grubenv nogrub, no-docgrub, no-update-grub, 32, no-boot, no-os, is-correct-EFI, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, no-grldr, no-b-bcd, nopakmgr, nogrubinstall, /mnt/boot-sav/sda1.
sda2 : sda, not-sepboot, grubenv-ok grub2, grub-efi, update-grub, 64, with-boot, is-os, gpt-but-not-EFI, fstab-has-bad-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, no-grldr, no-b-bcd, apt-get, grub-install, /mnt/boot-sav/sda2.
sda3 : sda, maybesepboot, no-grubenv nogrub, no-docgrub, no-update-grub, 32, no-boot, no-os, gpt-but-not-EFI, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, no-grldr, no-b-bcd, nopakmgr, nogrubinstall, /mnt/boot-sav/sda3.
sda : GPT-BIS, GPT, no-BIOS_boot, has-correctEFI, 34 sectors * 512 bytes
which suggests that sda is EFI. However, this may be a consequence of the partitioning rather than a reflection on the system. I did try boot-repair with the bios option, but it did not seem to help. I can't be sure that the partitioning was appropriate though.
In response to Yannbuntu, USB FDD I guess is the option to boot from an external floppy disk drive, perhaps for DOS?
Anyway, it is all a bit strange, and above my head.
@oldfred: thanks (first time i see such an "old-looking" EFI BIOS ). I am worried because i see no way to set up EFI mode, nor to select the grub64amd.efi file.
@frncz: i updated the PPA. Please could you boot on a Ubuntu live-CD ("Try Ubuntu"), then connect internet, then open a terminal (Ctrl+Alt+T), then type the following commands (indicate if you see something strange):
Code:sudo apt-get updateCode:sudo apt-get install -y boot-repair boot-savthen click the "Recommended repair", and indicate the new URL that will appear.Code:boot-repair
Then in boot-repair, I chose the boot/efi option
and finally ran boot-repair.
It took a long time on dpkg-configure -a sda2. It seems to be stuck there. I waited 30 minutes, then cancelled. I will try again.
Ignoring the option boot/efi option, boot-repair ran until I got the message:
Please close all your package managers (Software Center, Update Manager, Synaptic, ...). Then try again.
Try again with 'boot-repair', or reboot? Message not clear.
I'll try boot-repair again after hutting down Firefox etc.
Well, I'm in a loop. After a few minute I get the same message again (Please close all your package managers (Software Center, Update Manager, Synaptic, ...). Then try again.)
It seems to be independent of the ticks in the boot-repair options.
Last edited by frncz; May 10th, 2012 at 09:32 AM.
I rebooted and tried again. Boot-repair definitely gets stuck at:
dpkg-configure -a sda2. I waited more than 1 hour.
There may be a dpkg problem blocking the process.
From a live-cd, please connect internet, then type in a terminal:
Immediately, in the #chroot invite, type:Code:sudo mount /dev/sda2 /mnt sudo mount /dev/sda1 /mnt/boot/efi for w in dev dev/pts proc sys; do sudo mount -B /$w /mnt/$w ; done sudo cp /etc/resolv.conf /mnt/etc/resolv.conf sudo chroot /mnt
Please indicate their outputs, and if any window appears.Code:apt-get update dpkg --configure -a apt-get install -f grub-setup grub-install update-grub
Then wait for all packages to be green here, run Boot-Repair, update it, and indicate the new URL that will appear.
Last edited by YannBuntu; May 10th, 2012 at 01:38 PM.
Is this line correct? is single " OK?Code:for w in dev dev/pts proc sys; do sudo mount -B /mnt/$w" ; done
the commands ends with the > prompt instead of $?
you're right, sorry. I fixed my last message.
Prompts must end by #. When then end by >, that generally means that the last command was incorrect, you need to cancel by Ctrl+C or Ctrl+Z.
Please reboot, then retry.
Last edited by YannBuntu; May 10th, 2012 at 01:22 PM.