Re: Bug#695328: [testing/wheezy] UEFI installed system fails to boot
Kenyon Ralph wrote:
>
>Boot method: USB memory stick
>
>Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
>dated 2012-12-07T04:21
>
>Date: 2012-12-07T22:00-08:00
>
>Machine: Intel DH77EB motherboard, latest firmware, version 0097 (dated 2012-10-31)
>Processor: Intel Core i7-3770
>Memory: 32 GB
>Partitions: the installer's "use the whole disk" default (efi boot
>partition, ext4 root, swap)
...
>Base System Installation Checklist:
>[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
>Initial boot: [O]
>Detect network card: [O]
>Configure network: [O]
>Detect CD: [ ]
>Load installer modules: [O]
>Detect hard drives: [O]
>Partition hard drives: [O]
>Install base system: [O]
>Clock/timezone setup: [O]
>User/password setup: [O]
>Install tasks: [O]
>Install boot loader: [O]
>Overall install: [E]
>
>Comments/Problems:
>
>Installer booted into EFI bootloader, and I used the graphical
>installer. Installation goes fine, but the resulting system does not
>boot. The computer acts as if there is no bootable disk ("please
>insert boot disk").
>
>Ubuntu 12.10 installs and boots using UEFI fine. I suspect a problem
>with the EFI NVRAM boot entry that the Debian Installer creates, as
>reported by efibootmgr. It looked quite different from what Ubuntu
>created (unfortunately I didn't save the output), but I think the
>Ubuntu entry had a /boot/efi path in it.
>
>The motherboard is set to the default of "try EFI booting first, and
>fall back to legacy BIOS".
>
>Booting into rescue mode and running modprobe efivars ; efibootmgr
>--verbose gives this output:
>
>BootCurrent: 0003
>Timeout: 1 seconds
>BootOrder: 0000,0003,0001,0002
>Boot0000* debian Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
>Boot0001* SATA : PORT 6G 0 : INTEL SSDSC2CW120A3 : PART 0 : Boot Drive BIOS(2,0,00)AMBO
>Boot0002* USB : 0.00 : PART 0 : Boot Drive BIOS(2,0,00)AMBO
>Boot0003* UEFI : USB : 0.00 : PART 1 : OS Bootloader ACPI(a0341d0,0)PCI(1d,0)USB(1,0)USB(1,0)HD(2,6f000,380,73bb6f1a)AMBO
>
>How can I help debug this further?
Hi,
Hmmm, that looks very different from what I see in my own testing. In
a VM here I've got:
BootCurrent: 0000
BootOrder: 0005,0000,0001,0002,0003,0004
Boot0000* EFI DVD/CDROM ACPI(a0341d0,0)PCI(1,1)ATAPI(1,0,0)
Boot0001* EFI Floppy ACPI(a0341d0,0)PCI(1,0)ACPI(60441d0,0)
Boot0002* EFI Floppy 1 ACPI(a0341d0,0)PCI(1,0)ACPI(60441d0,1)
Boot0003* EFI Hard Drive ACPI(a0341d0,0)PCI(1,1)ATAPI(0,0,0)
Boot0004* EFI Internal Shell MM(b,3facf000,3ffbefff)
Boot0005* debian HD(1,800,f3800,97bffec2-8f3a-4189-87f4-b77080076fb2)File(\EFI\debian\grubx64.efi)
This is booted from a rescue CD image (as a CD, not via USB). From
your rescue boot shell, could you try:
# mount -av
# grub-install /dev/sda
and see how that affects things please? I'm curious what's happening
here...
--
Steve McIntyre, Cambridge, UK. steve@einval.com
"We're the technical experts. We were hired so that management could
ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Reply to: