Surface Pro 4 Manjaro and Windows Boot

Have Manjaro set-up but cannot get it to boot. Have followed the instructions in Using livecd v17.0.1 as grub to boot OS with broken bootloader

Outputs from requested information:

efibootmgr -v
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0004,0005,0001,0002,0000
Boot0000* Internal Storage	FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(50670071-478f-4be7-ad13-8754f379c62f)SDD.
Boot0001* USB Storage	FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(50670071-478f-4be7-ad13-8754f379c62f)USB.
Boot0002* PXE Network	FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(50670071-478f-4be7-ad13-8754f379c62f)PXE.
Boot0003* MsTemp	PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(2,MBR,0xa23925a6,0x409390,0x2000)
Boot0004* Windows Boot Manager	HD(2,GPT,f799c18b-8e80-4a89-bbfb-f8e40292d147,0xfa000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0005* Manjaro	HD(1,GPT,2fde7361-8cfd-4df8-8b2f-e14372c50d71,0x1001,0x96001)/File(\EFI\Manjaro\grubx64.efi)
sudo parted -l
Model: SanDisk Cruzer Blade (scsi)
Disk /dev/sda: 8003MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      32.8kB  2167MB  2167MB  primary               boot
 2      2167MB  2171MB  4194kB  primary               esp


Model: Generic- USB3.0 CRW -SD (scsi)
Disk /dev/sdb: 63.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      2098kB  317MB   315MB   fat32                 boot, esp
 2      317MB   34.5GB  34.2GB  ext4
 3      34.5GB  42.9GB  8388MB  linux-swap(v1)
 4      42.9GB  63.9GB  21.0GB  fat32                 msftdata


Model: Unknown (unknown)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  524MB  523MB   ntfs         Basic data partition          hidden, diag
 2      524MB   629MB  105MB   fat32        EFI system partition          boot, esp
 3      629MB   646MB  16.8MB               Microsoft reserved partition  msftres
 4      646MB   256GB  255GB                Basic data partition          msftdata
sudo blkid
/dev/nvme0n1p1: LABEL="Recovery" UUID="2080B0F180B0CE92" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="004c8550-6816-419f-95ac-6e7044108dad"
/dev/nvme0n1p2: UUID="32B2-4F76" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="f799c18b-8e80-4a89-bbfb-f8e40292d147"
/dev/sda1: UUID="2018-07-01-09-34-20-00" LABEL="MJR17111" TYPE="iso9660" PARTUUID="a23925a6-01"
/dev/sda2: SEC_TYPE="msdos" LABEL="MISO_EFI" UUID="64C8-8DA6" TYPE="vfat" PARTUUID="a23925a6-02"
/dev/sdb1: UUID="0C35-45DB" TYPE="vfat" PARTUUID="2fde7361-8cfd-4df8-8b2f-e14372c50d71"
/dev/sdb2: UUID="422d6399-716d-43d9-a87f-52db59fa4c37" TYPE="ext4" PARTUUID="715bb6fa-2e1d-4934-9102-f6c39d4f5792"
/dev/sdb3: UUID="7450112d-b4ab-4bf5-9643-ae2d3759db6c" TYPE="swap" PARTUUID="9fa68f64-00ae-48eb-8e35-e3e311e6f359"
/dev/sdb4: UUID="0D66-0B32" TYPE="vfat" PARTUUID="c98821a5-ed83-4736-9118-78df5f71cb0a"
/dev/nvme0n1: PTUUID="b2feab1b-b907-429b-a812-f83c1a9f823c" PTTYPE="gpt"
/dev/nvme0n1p3: PARTLABEL="Microsoft reserved partition" PARTUUID="9e6400ed-4795-45cb-a4bd-aa9f77e92d35"
/dev/nvme0n1p4: PARTLABEL="Basic data partition" PARTUUID="8e1f034c-7a4c-4ff9-b0cd-37f4b1c82f30"
findmnt -s
TARGET    SOURCE                                    FSTYPE OPTIONS
/boot/efi UUID=0C35-45DB                            vfat   defaults,noatime
/         UUID=422d6399-716d-43d9-a87f-52db59fa4c37 ext4   defaults,noatime
swap      UUID=7450112d-b4ab-4bf5-9643-ae2d3759db6c swap   defaults,noatime
findmnt /boot/efi
TARGET    SOURCE    FSTYPE OPTIONS
/boot/efi /dev/sdb1 vfat   rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro

Also wireless seems to be flakey when I do manage to boot into the installed version via the grub instructions at the beginning of Using livecd v17.0.1 as grub to boot OS with broken bootloader

Guidance would be much appreciated.

So, can you boot into the installed Manjaro OS or not?

Is the issue that GRUB installed to /dev/sdb doesn't work or isn't found?

What error message (or otherwise) appears when you're not using a LiveCD as a boot loader?

Have you run through https://wiki.manjaro.org/index.php/Restore_the_GRUB_Bootloader ?

I see a mixture of MSDOS and GPT. You will probably want to use one or the other, but not both.

1 Like

You made $esp sdb1
With a nvme disk, the $esp must be in nvme partition, namely nvme0n1p2 in your case.

Boot up again to manjaro installed partition.
change fstab /boot/efi to nvme0n1p2
unmount /boot/efi
mount nvme0n1p2 to /boot/efi
And redo the complete step 6 as per the link you use.
This time use

sudo efibootmgr -c -d /dev/nvme0n1 -p 2 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"

for the last command in that step 6.

Good luck.

ps: you might end up with 2 efibootentries for 'manjaro', don't worry about it for the moment.
We'll fix it later on.

2 Likes

Hi - sorry it was getting a bit late when I posted.

I can boot from live USB and then hit 'c' and use
grub> search.file /etc/manjaro-release root
grub> configfile /boot/grub/grub.cfg

and can then access the installed system. When I use the two commands above I get a grub menu with Manjaro and Windows on it - which is really what I am looking for without having to do the live usb and grub commands.

I hope this helps.

Many thanks

Will also try this approach and let you know. Many thanks!

Progress! I can now boot into my Manjaro installation without the need for the liveusb.

That having been said it is still an interesting experience.
Windows will not boot without BIOS Security enabled - I receive a BitLocker message otherwise. Manjaro will only boot with no security. Once in Manjaro networking will not work if there is a saved wireless network. I have to remove the network the reboot.

As I said - some progress - thank you for the assistance to get this far.

Also I tried to install surface-linux4 but it won't complete as follows:

Verifying source file signatures with gpg...
linux-4.14.15.tar ... FAILED (unknown public key 38DBBDC86092693E)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build linux-surface4.

I presume it would be beneficial to be able to install this and so I would appreciate assistance with this too.

Looking forward to further updates :slight_smile:

Read the AUR comments & read the side bar: Flagged out-of-date (2018-02-04)

Do you have any thoughts on this?.....

Windows will not boot without BIOS Security enabled - I receive a BitLocker message otherwise. Manjaro will only boot with no security. Once in Manjaro networking will not work if there is a saved wireless network. I have to remove the network the reboot.

Many thanks

Bitlocker shouldn't require secureboot. It should just need tpm.

Is that a setting you can change in bitlocker?

Can you open a new topic on this?
I'm sure lots others here would be able to help you out on it.
Good luck.

Latest update - tried to fix up BitLocker Error that was occurring when trying to boot Windows 10 when not in Secure mode and ended up having to re-install Windows 10 :frowning:
Since then though I can boot to the BIOS with Security disabled and then access either Windows or Manjaro :slight_smile:
I am now using wired networking but will update and start a new topic if I have further experiences on the subject. Thanks for help :smiley:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by