Arch Linux

kalle

Member

Registered: 2016-04-09

Posts: 22

No boot device, (GUID Partition Table Header is wrong)

Hi there, I am lost now. After having a kubuntu 14.04 successfully running on my laptop (giving up on Arch at the first trial), I have made another try to get Arch running (Since I was successfully on my desktop).

So I installed Arch on my laptop with a Samsung SM951-NVMe SSD, identified as /dev/nvme0n1, with the following setup:
-UEFI boot
-gpt partition
-1 partition efi boot (/dev/nvme0n1p1)
-2 partiton encrypted boot1 (/dev/nvme0n1p2), with file system ext2
-3 partition encrypted boot2 (/dev/nvme0n1p3), with file system ext2
-4 partition lvm (/dev/nvme0n1p4)
-inside lvm: swap, tmp, encrypted root1 (filesystem ext4), encrypted root2 (filesystem ext4)

boot2 and root2 are planned for a second operation system, so they were not used

During installation I mounted the following (after decryption if necessary):
/dev/mapper/root1 at /mnt
/dev/mapper/boot1 at /mnt/boot
/dev/nvme0n1p1 at /mnt/boot/efi

I installed the system into mnt, and made the necessary changes to fstab and crypttab.
I made the necessary changes to mkinitcpio.conf (encrypt lvm2) and run mkinitcpio -p linux.
Then I installed grub and efibootmgr and made the necessary changes to /etc/default/grub (enable_cryptodisk and the cmd_line adjustment)

Then I made grub-config and got some warnings about lvmetad, which according to the grub manpage can be ignored (I found some workarounds to get rid of the warnings but that did not help)
Then I made "grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub --recheck" and got this messages:

GUID Partition Table Header signature is wrong: 41615252 != 5452415020494645
GUID Partition Table Header signature is wrong: 0 != 5452415020494645

*********************************************************************
Warning! This MBR disk does not have a unique signature
If this is not the first disk found by EFI, you may not be able to boot from it without a unique signature.
Run efibootmgr with the -w flag to write a unique signature to disk.
********************************************************************

This message is repeated 3 times.

Then comes:

Installation finished. No error reported.

Then the command promt reappears.

Rebooting the system resulted in the message "reboot and select a boot device or insert a bootable media".

The bios does not show any bootable media.

The output of efibootmgr -v when booting from usb, mounting all necessary partitions and executing arch-chroot /mnt /bin/bash, executing the above grub-install command and runnig efibootmgr -w and afterwards efibootmgr -v is:

BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0000,0001
Boot0000* grub HD(1,MBR,0x0,0x0,0x0)/File(\EFI\grub\grubx64.efi)
Boot0001* UEFI: USB DISK 2.0 PMAP, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(4,0)/HD(1,MBR,0x23,0xac,0x14000)..BO

However. After rebooting into usb the output of efibootmgr -v is:

BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0000,0001
Boot0000* grub VenHw(99e275e7-75a0-4b37-a2ef-c5385e6c00cb)
Boot0001* UEFI: USB DISK 2.0 PMAP, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(4,0)/HD(1,MBR,0x23,0xac,0x14000)..BO

Note that I did successfully the same setup on my desktop (which I using to write this post). I am lost at this point. I reinstalled the whole system several times, zeroed the SSD (dd if=/dev/zero of=/dev/nvmen1 bs=1), recreated the partition table with fresh MBR, but nothing helped!!!!

Does anyone has any idea how to overcome this problem???

Thanks a lot.

Karl

Parker8283

Member

Registered: 2016-06-26

Posts: 1

Re: No boot device, (GUID Partition Table Header is wrong)

Bump! I am having almost literally the exact same problem, although mine is on two M.2 SSDs, windows on one arch on the other. I have tried SOOOO many things, and can't seem to get it to work, so it makes me think it's a Linux and M.2 issue. It'd be great if someone could help us, thank you so much!

Onyx_Monster

Member

Registered: 2016-06-26

Posts: 1

Re: No boot device, (GUID Partition Table Header is wrong)

I had the same problem. I followed the pages below and used systemd as my bootloader. Hope this helps!

Define MODULES="i915 nvme" in /etc/mkinitcpio.conf because Linux 4.4 needs the nvme module in /etc/mkinitcpio.conf to boot.  https://bbs.archlinux.org/viewtopic.php?id=213075

Grub will not work with NVMe and UEFI so use a different bootloader. https://bbs.archlinux.org/viewtopic.php?id=209653

kalle

Member

Registered: 2016-04-09

Posts: 22

Re: No boot device, (GUID Partition Table Header is wrong)

Hi,

thanks for the hints.

I gave it another try, included MODULES="nvme" in mkinitcpio.conf (probably the wrong spelling) and compiled grub from AUR.

Everything boots now.

Cheers

Head_on_a_Stick

Member

From: London

Registered: 2014-02-20

Posts: 7,732

Website

Re: No boot device, (GUID Partition Table Header is wrong)

Grub will not work with NVMe and UEFI

It should do, the NVMe bug was fixed in the Arch package in March 2016:
https://bugs.archlinux.org/task/47447

---

Are you infected with Wetiko?

Galmax

Member

Registered: 2016-08-01

Posts: 2

Re: No boot device, (GUID Partition Table Header is wrong)

I can confirm NVMe and UEFI with grub currently only works with the latest version from git (ie. from the grub-git AUR package). After regenerating the config and doing grub-install again (without any warnings), the system now boots from my Samsung 950 Pro successfully.