Odd it does not appear to be GPT formatted. That may be where the trouble is.
How do I fix it?
Re do the drive and make it GPT I think you can use gdisk
do
man gdisk for info
A grub prompt is normal on UEFI boot. There should still be a menu with an option to choose “Installation”. Or are you saying that there is no grub2 menu? If there is no grub2 menu, then something is wrong with that flash drive.
After doing the “dd” to copy the iso to the flash drive, try rebooting to make sure that all buffers have been flushed to the devices. Don’t unplug the USB until you see the boot splash screen. This should not be necessary, but you could try it.
I think an EFI install on a non GPT drive may be the problem ie hi i’m install EFI mode where is the GPT partition table oops is none drop to prompt
That’s normal. The opensuse install isos are using legacy MBR hybrid partition, with a partition type code of “ef” to indicate an EFI partition. That seems to work.
As I recall, they used “GPT” for the 12.3 Beta, then changed to the current format after that. I think I know why. Once you use GPT partitioning on a drive, it leaves traces behind that makes it hard to use that drive for anything else.
Not the install media the hard drive target. It is not GPT but has EFI partition. My supposition is that the installer thinking it is installing to a GPT drive looks for the GPT partition table and does not find it and chocks. The OP says that booting the installer in legacy mode gets him to the menu. Booting in EFI mode and noda. But the Drive does have an EFI boot partition but fdisk does not say it is GPT
I just did what you told me. Using ImageWriter from openSUSE.
sudo fdisk -l /dev/sdb
[sudo] password for paludo:
Disk /dev/sdb: 8019 MB, 8019509248 bytes
64 heads, 32 sectors/track, 7648 cylinders, total 15663104 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x10ce3e4f
Device Boot Start End Blocks Id System
/dev/sdb1 3584 11647 4032 ef EFI (FAT-12/16/32)
/dev/sdb2 * 11648 9138175 4563264 17 Hidden HPFS/NTFS
Same thing as before, if it is an issue is with ImageWriter, right?
$ sudo gdisk /dev/sdb
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
typing 'q' if you don't want to convert your MBR partitions
to GPT format!
***************************************************************
Command (? for help): r
Recovery/transformation command (? for help): g
Warning: 0xEE partition doesn't start on sector 1. This can cause problems
in some OSes.
MBR command (? for help): w
Converted 2 partitions. Finalize and exit? (Y/N): Y
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.
Warning: 0xEE partition doesn't start on sector 1. This can cause problems
in some OSes.
After using gdisk. No luck at all.
$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 8019 MB, 8019509248 bytes
247 heads, 62 sectors/track, 1022 cylinders, total 15663104 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 3584 11647 4032 ef EFI (FAT-12/16/32)
/dev/sdb2 11648 9138175 4563264 7 HPFS/NTFS/exFAT
I don’t know what else to do. I just want to install openSUSE using UEFI boot mode.
I’m kind of stubborn, I’ll keep trying till I got this thing working.
no no no no
Want to se the info from the drive you are installing to. I thought that is what you gave me but you gave me the USB info not the HD info. Arg
Re image the USB it was OK it is the HD that is of interest not the USB
What I see is this: http://imgur.com/p5aqJvL
Generally I do “dd” and “sync” command after.
sudo fdisk -l /dev/sda
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 234441647 117220823+ ee GPT
ok what is in that one partition? Here there is no EFI boot but that should not matter.
Ubuntu?? and no swap???
I’m stumped
On Wed 18 Feb 2015 05:56:01 PM CST, nrickert wrote:
gogalthorp;2695620 Wrote:
> Odd it does not appear to be GPT formatted. That may be where the
> trouble is.
That’s normal. The opensuse install isos are using legacy MBR hybrid
partition, with a partition type code of “ef” to indicate an EFI
partition. That seems to work.
As I recall, they used “GPT” for the 12.3 Beta, then changed to the
current format after that. I think I know why. Once you use GPT
partitioning on a drive, it leaves traces behind that makes it hard to
use that drive for anything else.
Hi
No, with gdisk you use the option x (expert mode) then z for zap to
turn it back. This removes the gpt and cleans out the mbr so fdisk can
be used.
I also note that users with trying to recover the usb
devices can use wipefs -a (MAKE SURE YOU PICK THE CORRECT
DEVICE!!!) /dev/sdX to clear out the pesky bit’s left over as well,
this will recover it back to normal.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.36-38-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Actually the “fdisk” didn’t show the partition table.
Here is what “gdisk” shows:
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/sda: 234441648 sectors, 111.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 177031A6-3DD3-461F-8979-C9F39A3323DD
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 234441614
Partitions will be aligned on 2048-sector boundaries
Total free space is 2925 sectors (1.4 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 1050623 512.0 MiB EF00
2 1050624 217860095 103.4 GiB 8300
3 217860096 234440703 7.9 GiB 8200
Command (? for help):
Got no clue. There is no reason that the USB would not boot in EFI mode that I can see. Did you try on another machine?? Something funky about the BIOS maybe but I have never seen this. It usually is that the poster has added some boot help to to iso which does not work with openSUSE.
I just make it work by booting manually.
On the grub terminal I did:
grub>set prefix=(hd0,1)/efi/boot/
grub>set root=(hd0,1)
grub>insmod normal
grub>normal
And the installation screen just popped up.
I don’t know whats the problem is, but the usb stick was ok for sure.
Thanks anyway.
Your grub already loaded normal but for some reasons it did not find grub.cfg. Looks like prefix was wrong. Could you boot from USB stick and post output of “set” command? If it exceeds one screen, use “set pager=1” to make it pause at each full screen. It may need bug report.
I’ve got the same problem as OP with booting. I’d like to install openSUSE on Lenovo Miix2 which requires GPT partitioning and EFI boot. openSUSE ISOs (13.2 or the latest daily Tumbleweed) written to USB stick does not fulfill these requirements and I can’t boot as far as to grub with openSUSE USB sticks.
Earlier (last summer) I managed to boot GPT/EFI (secure boot disabled) with some Ubuntu images after changing the EFI bootloader following instructions from here and here to the point where live image was running and provided me with an option to install but did not recognize the internal mmc to finish the install so I gave up back then.
Given the latest Lenovo news I could not care less for the Windows install on that machine anymore and I’d like to give openSUSE a go. What I’m going to do next is I’ll try Rufus with openSUSE image(s) and update the EFI bootloader is required. I’ll let you know how it goes.
With openSUSE Tumbleweed image written using Rufus and “GPT Partition scheme for UEFI computer” and placing paperWastage’s bootia32.efi to /EFI/BOOT/ I get Lenovo Miix2 10" to boot to Grub shell. openSUSE 13.2 image failed with Rufus. Without /EFI/BOOT/bootia32.efi it fails to boot from USB stick and proceeds to Windows.
GNU GRUB version 2.00
Minimal BASH-like editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file options.
grub > ls
(hd0) (hd0, gpt1) (hd1, gpt4) (hd1, gpt3) (hd1, gpt2) (hd1, gpt1)
grub > ls (hd0, gpt1)
archives.gz System Volume Information/ autorun.inf boot/ Changelog content content.asc content.key control.xml directory.yast docu/ efi/ gpg-pubkey-3dbdc284-53674dd4.asc gpg-pubkey-307e3d54-4be01a65.asc GPLv2.txt GPLv3.txt images/ index.gz license.tar.gz ls-lR.gz media.1/ openSUSE13_2_NET.exe openSUSE13_2_LOCAL.exe readme suse/ SuSEgo.ico syslinux.cfg
grub > set root=(hd0, gpt1)
If you can help with boot parameters for openSUSE from grub shell it is highly appreciated. What I’m looking for is something like (or other way to boot openSUSE from grub shell):
grub > linux /path/to/vmlinuz-x.y.z <kernel cmd_line params>
grub > initrd /path/to/initrd/initrd.img-x.y.z
grub > boot
I tried
grub > linux /boot/x86_64/vmlinuz-xen
grub > initrd /boot/x86_64/vmlinuz-xen
grub > boot
but it just got stuck without any errors.
Thanks!
It is generally better to start your own thread. Often the problem turns out to be different.
Opensuse 13.2 does support GPT partitioning and EFI boot. I’ve been installing that way on newer hardware (including a Lenovo TS140).
Some ways of preparing USB sticks break the EFI boot support. Make sure you follow the method in the opensuse Wiki.
I don’t know much about Lenovo Miix2. A google search shows that it is a tablet. At least some tablets use 32-bit EFI. If that applies to your tablet, then you will have problems. Opensuse does not currently support 32-bit EFI. Nor do most other linux distros. There are some web pages on do-it-yourself workarounds. Note that if you can get your system installed and booting, it will be fine. What’s missing for 32-bit EFI is adequate boot support. (There is a feature request for such support to be provided in the future).