UEFI Windows 8 and OpenSuSE 12.2: no bootable devices found after install

Hi,

I’ve been running various Linux distros for ten years now. I just bought an Acer Aspirve v3 571 pre-installed with Windows 8. I attempted to install openSuSE 12.2: the installation seemed to have succeeded, but now I can’t boot neither on Windows 8 nor on Linux .

Minor installation hiccups:
The first hiccup was that I had to switch the BIOS to “Legacy mode” since the UEFI booting policy didn’t allow me to boot on a CD/DVD drive (close to actual message). Here’s a note to the installation DVD maintainers: the default partition layout wants to remove the windows 8 boot partition (I’m glad I caught that). When creating my partitions, all I did was shrink the windows 8 C drive (didn’t touch any other partition).

Major post-installation problems:
It is now impossible for me to boot on anything. When starting in UEFI mode the message is a nicely displayed “No bootable devices found. Press any key.” When booting in Legacy mode, the message is the same (just without the n-curses like style). Grub is either not installed or the bios isn’t pointing to it. The bios doesn’t point either to the Windows 8 booting system.

Attempted solution (failed):
Since it wasn’t working, I decided to re-install OpenSuSE 12.2 using the same method. This time, I asked to install the grub2-efi package. I still have the exact same problem and message.

Conclusion: help needed:
Any thoughts? The computer did not come with a recovery CD.

Thanks in advance.

My guess is that GPT is the culprit… Windows 8 needs that.

If Windows is installed to a GPT hard disk on a UEFI PC, you must install openSUSE using EFI mode, selected from the PC UEFI setup. Further, if Windows was installed using secure boot, you likely can’t go back and make it work without reinstalling it all. You can convert any Hard disk, usable up to 2.2 TB, to a MBR setup and Windows 8 & openSUSE can exist on the old style setup. You can also use openSUSE and Windows 8 on a GPT disk if Windows 8 is not in secure boot mode and both are installed using EFI. openSUSE 12.3 will support secure boot mode, but I have never tried to make that work yet. You can read more about GPT & MBR disks on my article here:

https://forums.opensuse.org/content/111-partitioning-hard-disk-during-install.html

Thank You,

Please, boot from any live media, run bootinfoscript (https://github.com/arvidjaar/bootinfoscript/raw/master/bootinfoscript) and post results.

Thanks for sharing. Very useful to get all the info at once.

You can use the following terminal command to download the script, mark it executable and run it. If the script already exists, it is removed first to allows for an update:

rm ~/bin/bis ; wget -nc https://raw.github.com/arvidjaar/bootinfoscript/master/bootinfoscript -O ~/bin/bis ; chmod +x ~/bin/bis ; sudo bis

Thank You,

Credits not mine. The upstream is at sourceforge; I maintain local repo with some fixes/enhancements suggested to upstream but not (yet) integrated.

Thank you for your answers. I will provide you the results tomorrow, as I don’t have any live cd. What I might do is copy the script on a USB key, and plug it in once booted on the opensuse installation Dvd, mount it and run the script. I believe that should do the trick.

As far as I know, only the DVD version supports and recognizes the UEFI environment.
https://forums.opensuse.org/content/102-booting-opensuse-uefi-bios-elilo-grub2-linux-only-multi-booting.html

When you install openSUSE from DVD (not from live CD!) on a UEFI system, the preselected (and only advisable) bootmanager is elilo. The other choices, Grub and Lilo, don’t support EFI boot, and Grub2 is not availalble in setup. The boot options are different and the question of writing Grub to MBR does NOT apply here. Furthermore, the live CD doesn’t include UEFI setup. Thus to install openSUSE (such as 12.1) using a GUID partition table on a UEFI motherboard, you have to install from DVD (or net install).

Probably, while installing openSUSE, he has chosen to format the EFI partition … :frowning:

Dear all,

According to the results of the bootinfoscript proposed above, there seems to be some kind of mismatched between partition tables. The results (cf. below) says that the GPT partition table is not used.

There is also a discrepancy between what fdisk -l says and what df shows. I realized that when mounting the partitions and checking what’s in them.

PiElle, as mentioned in my very first message, I did not touch the EFI Booting partition. I can confirm that since I was able to mount it and to check that the Windows booting files where present. There also were some opensuse booting files (probably those of 12.3 which I attempted to install yesterday).

What recovery actions should I do to “say” to the BIOS (or whoever) to use the GUID partition table again?

Thanks again for your help.


                  Boot Info Script 0.61      [1 April 2012]


============================= Boot Info Summary: ===============================

 => SUSE generic MBR is installed in the MBR of /dev/sda.
 => Syslinux MBR (4.04 and higher) is installed in the MBR of /dev/sdb.

sda1: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sda2: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  Windows 7/2008: FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /efi/Boot/bootx64.efi /efi/opensuse/grubx64.efi 
                       /efi/Microsoft/Boot/bootmgfw.efi 
                       /efi/Microsoft/Boot/bootmgr.efi 
                       /efi/Microsoft/Boot/memtest.efi 
                       /efi/OEM/Boot/bootmgfw.efi /efi/OEM/Boot/bootmgr.efi 
                       /efi/OEM/Boot/memtest.efi

sda3: __________________________________________________________________________

    File system:       
    Boot sector type:  -
    Boot sector info: 
    Operating System:  
    Boot files:        

sda4: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  According to the info in the boot sector, sda4 starts 
                       at sector 1697792. But according to the info from 
                       fdisk, sda4 starts at sector 1. The info in boot 
                       sector on the starting sector of the MFT is wrong. The 
                       info in the boot sector on the starting sector of the 
                       MFT Mirror is wrong. According to the info in the boot 
                       sector, sda4 has 409594736 sectors, but according to 
                       the info from fdisk, it has 0 sectors.
    Operating System:  Windows 8
    Boot files:        /Windows/System32/winload.exe

sdb1: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1               2,048       821,247       819,200   7 NTFS / exFAT / HPFS
/dev/sda2    *        821,248     1,435,647       614,400   c W95 FAT32 (LBA)
/dev/sda3           1,435,648     1,697,791       262,144  83 Linux
/dev/sda4                   1             1             1  ee GPT


GUID Partition Table detected, but does not seem to be used.

Partition    Start Sector    End Sector  # of Sectors System
/dev/sda1           2,048       821,247       819,200 Windows Recovery Environment (Windows)
/dev/sda2         821,248     1,435,647       614,400 EFI System partition
/dev/sda3       1,435,648     1,697,791       262,144 Microsoft Reserved Partition (Windows)
/dev/sda4       1,697,792   421,122,811   419,425,020 Data partition (Windows/Linux)
/dev/sda5     937,428,992   976,773,119    39,344,128 Windows Recovery Environment (Windows)
/dev/sda6     421,124,096   903,462,911   482,338,816 Data partition (Windows/Linux)
/dev/sda7     903,462,912   937,408,511    33,945,600 Data partition (Windows/Linux)

Drive: sdb _____________________________________________________________________

Disk /dev/sdb: 8002 MB, 8002732032 bytes
37 heads, 37 sectors/track, 11417 cylinders, total 15630336 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdb1    *          8,064    15,630,335    15,622,272   7 NTFS / exFAT / HPFS


"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/loop0                                              squashfs   
/dev/loop1                                              squashfs   
/dev/loop2                                              squashfs   
/dev/loop3                                              squashfs   
/dev/loop4                                              squashfs   
/dev/sda1        4664415664414A3F                       ntfs       Recovery
/dev/sda2        4A43-A461                              vfat       ESP
/dev/sda4        EAE244C7E24499A9                       ntfs       Root
/dev/sda5        3CDC4656DC460A9A                       ntfs       Push Button Reset
/dev/sda6        892deea1-f688-4f21-beeb-177080e8acaa   ext4       
/dev/sda7        c68afa35-c052-4245-ae40-38217a50a9b1   swap       
/dev/sdb1        5E226F88226F63CD                       ntfs       Lawrence
/dev/sr0                                                iso9660    openSUSE-12.3-DVD-x86_640094

========================= "ls -l /dev/disk/by-id" output: ======================

total 0
lrwxrwxrwx 1 root root  9 Mar  5 13:59 ata-HL-DT-ST_DVDRAM_GT70N_KZSC9IK4738 -> ../../sr0
lrwxrwxrwx 1 root root  9 Mar  5 13:58 ata-TOSHIBA_MQ01ABD050_X28LF2Z3S -> ../../sda
lrwxrwxrwx 1 root root 10 Mar  5 13:59 ata-TOSHIBA_MQ01ABD050_X28LF2Z3S-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Mar  5 13:59 ata-TOSHIBA_MQ01ABD050_X28LF2Z3S-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Mar  5 13:59 ata-TOSHIBA_MQ01ABD050_X28LF2Z3S-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Mar  5 13:59 ata-TOSHIBA_MQ01ABD050_X28LF2Z3S-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Mar  5 13:59 ata-TOSHIBA_MQ01ABD050_X28LF2Z3S-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Mar  5 13:59 ata-TOSHIBA_MQ01ABD050_X28LF2Z3S-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Mar  5 13:59 ata-TOSHIBA_MQ01ABD050_X28LF2Z3S-part7 -> ../../sda7
lrwxrwxrwx 1 root root  9 Mar  5 13:58 scsi-SATA_TOSHIBA_MQ01ABD0_X28LF2Z3S -> ../../sda
lrwxrwxrwx 1 root root 10 Mar  5 13:59 scsi-SATA_TOSHIBA_MQ01ABD0_X28LF2Z3S-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Mar  5 13:59 scsi-SATA_TOSHIBA_MQ01ABD0_X28LF2Z3S-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Mar  5 13:59 scsi-SATA_TOSHIBA_MQ01ABD0_X28LF2Z3S-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Mar  5 13:59 scsi-SATA_TOSHIBA_MQ01ABD0_X28LF2Z3S-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Mar  5 13:59 scsi-SATA_TOSHIBA_MQ01ABD0_X28LF2Z3S-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Mar  5 13:59 scsi-SATA_TOSHIBA_MQ01ABD0_X28LF2Z3S-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Mar  5 13:59 scsi-SATA_TOSHIBA_MQ01ABD0_X28LF2Z3S-part7 -> ../../sda7
lrwxrwxrwx 1 root root  9 Mar  5 13:58 usb-TDKMedia_Trans-It_Drive_07970103C7140203-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Mar  5 13:58 usb-TDKMedia_Trans-It_Drive_07970103C7140203-0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Mar  5 13:58 wwn-0x50000394571811ec -> ../../sda
lrwxrwxrwx 1 root root 10 Mar  5 13:59 wwn-0x50000394571811ec-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Mar  5 13:59 wwn-0x50000394571811ec-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Mar  5 13:59 wwn-0x50000394571811ec-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Mar  5 13:59 wwn-0x50000394571811ec-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Mar  5 13:59 wwn-0x50000394571811ec-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Mar  5 13:59 wwn-0x50000394571811ec-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Mar  5 13:59 wwn-0x50000394571811ec-part7 -> ../../sda7
lrwxrwxrwx 1 root root  9 Mar  5 13:59 wwn-0x5001480000000000 -> ../../sr0

================================ Mount points: =================================

Device           Mount_Point              Type       Options

/dev/loop0       /parts/mp_0000           squashfs   (ro,relatime)
/dev/loop1       /parts/mp_0001           squashfs   (ro,relatime)
/dev/loop2       /mounts/mp_0000          squashfs   (ro,relatime)
/dev/loop3       /mounts/mp_0001          squashfs   (ro,relatime)
/dev/loop4       /mounts/mp_0002          squashfs   (ro,relatime)
/dev/sdb1        /mnt/usb                 fuseblk    (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)


======================== Unknown MBRs/Boot Sectors/etc: ========================

MFT Sector of sda4

00000000  46 49 4c 45 30 00 03 00  ea 08 1e bc 00 00 00 00  |FILE0...........|
00000010  01 00 01 00 38 00 01 00  98 01 00 00 00 04 00 00  |....8...........|
00000020  00 00 00 00 00 00 00 00  06 00 00 00 00 00 00 00  |................|
00000030  20 01 ff ff 00 00 00 00  10 00 00 00 60 00 00 00  | ...........`...|
00000040  00 00 18 00 00 00 00 00  48 00 00 00 18 00 00 00  |........H.......|
00000050  7b f6 18 44 b4 ef cd 01  7b f6 18 44 b4 ef cd 01  |{..D....{..D....|
*
00000070  06 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000080  00 00 00 00 00 01 00 00  00 00 00 00 00 00 00 00  |................|
00000090  00 00 00 00 00 00 00 00  30 00 00 00 68 00 00 00  |........0...h...|
000000a0  00 00 18 00 00 00 03 00  4a 00 00 00 18 00 01 00  |........J.......|
000000b0  05 00 00 00 00 00 05 00  7b f6 18 44 b4 ef cd 01  |........{..D....|
000000c0  7b f6 18 44 b4 ef cd 01  7b f6 18 44 b4 ef cd 01  |{..D....{..D....|
000000d0  7b f6 18 44 b4 ef cd 01  00 40 00 00 00 00 00 00  |{..D.....@......|
000000e0  00 40 00 00 00 00 00 00  06 00 00 00 00 00 00 00  |.@..............|
000000f0  04 03 24 00 4d 00 46 00  54 00 00 00 00 00 00 00  |..$.M.F.T.......|
00000100  80 00 00 00 48 00 00 00  01 00 40 00 00 00 01 00  |....H.....@.....|
00000110  00 00 00 00 00 00 00 00  3f 00 01 00 00 00 00 00  |........?.......|
00000120  40 00 00 00 00 00 00 00  00 00 04 10 00 00 00 00  |@...............|
00000130  00 00 04 10 00 00 00 00  00 00 04 10 00 00 00 00  |................|
00000140  33 40 00 01 00 00 0c 00  b0 00 00 00 48 00 00 00  |3@..........H...|
00000150  01 00 40 00 00 00 05 00  00 00 00 00 00 00 00 00  |..@.............|
00000160  09 00 00 00 00 00 00 00  40 00 00 00 00 00 00 00  |........@.......|
00000170  00 a0 00 00 00 00 00 00  08 90 00 00 00 00 00 00  |................|
00000180  08 90 00 00 00 00 00 00  21 0a 7e 0e 00 f8 ff ff  |........!.~.....|
00000190  ff ff ff ff 00 00 00 00  ff ff ff ff 00 00 00 00  |................|
*
000001b0  ff ff ff ff 00 00 00 00  01 00 40 00 00 00 05 00  |..........@.....|
000001c0  00 00 00 00 00 00 00 00  01 00 00 00 00 00 00 00  |................|
000001d0  40 00 00 00 00 00 00 00  00 20 00 00 00 00 00 00  |@........ ......|
000001e0  08 10 00 00 00 00 00 00  08 10 00 00 00 00 00 00  |................|
000001f0  31 01 ff ff 0b 11 01 ff  00 ee a4 0a 80 fa 20 01  |1............. .|
00000200

=============================== StdErr Messages: ===============================

umount: sda3: not mounted
umount: sda3: not mounted
  No volume groups found
mdadm: No arrays found in config file or automatically



There is a combination of bugs in 12.2 and Windows which results in GPT disk created by Windows being converted into Hybrid-MBR during 12.2 installation. This renders Windows unbootable. There was very long thread about it on this forum.

The fix is to boot using any live media that includes gdisk (12.3 installation DVD should be OK) and write new protective MBR.

Your system cannot be booted using legacy BIOS at all. From your original post it is not clear whether you tried to install/boot in legacy BIOS or UEFI mode. And UEFI Windows boot should now fail with this partition table.

Hmm … bootinfoscript obviously does not expect Hybrid MBR. Something to fix :slight_smile:

Hi

That isn’t that clear to me: in his 1st posting n0x wrote

Which further is nasty (see as well 1st posting) is

and, n0x, you don’t seem to have created one, which at least using windows 7 seems to be possible using just windows tools.

This is the thread mentioned by arvidjaar:
https://forums.opensuse.org/english/get-technical-help-here/install-boot-login/478260-trouble-dual-booting-12-2-windows-7-efi-enabled-system.html
Windows 8 has a tool to make a recovery cd and an image of all the partitions (EFI and Microsoft reserved partition included) which is similar to Windows 7. In fact is called Windows 7 File Recovery (!).
I was able to create a bootable repair disk and an image of those partition by this tool, in the same way I did in Windows 7.
I’m dual booting Fedora 18 and Windows 8 in UEFI mode on a Lenovo notebook (Thinkpad Edge 330, a very Linux friendly machine).
As discussed in the above thread, my advice is to shrunk the Windows partition via its own tool and to make the Linux partitions via gdisk or gparted (this time, I opted to use the first), without using (for this task) yast or anaconda.
I used anaconda only to format the already existing partitions (obviously all the partitions, but the EFI one) …

Yes, good to hear that this works under windows8 as well.

But the OP (n0x) seems to just haven’t created such a recovery CD before installing openSUSE 12.2.

If your windows partitions are intact, have you tried the windows recovery program from the boot menu?

This can be entered, on some machines, by hitting the Esc key immediately after powering on.

Maybe this can get you back to square one.

OK, I overlooked it. But it sounded like OP tried to boot Windows using BIOS which makes no sense - it is obviously installed on UEFI system. And it was not clear to me whether OP tried to boot Windows in UEFI mode.

But that implies secure boot (that is how I interpret “did not allow me to boot DVD”) … there is simply not enough information about this configuration.

YES! That worked! I used gdisk and wrote a new protective MBR.

However, gdisk is not available on the openSuSE 12.3 disk, so I created a bootable USB with Parted Magic.

Thanks a lot for your insight, I was really running out of the options here.