No grub after fresh installation

Probably i lack the technical terminology to do a proper search, because i didn’t find any useful hint for my issue, sorry in advance.

I’ve installed Manjaro on dual boot with W10, on a GPT table HD… Usually after the installation, i’m able to choose the OS i want to boot (W10 included) but with Manjaro, i’m kicked back to the BIOS… Like there’s no grub at all.

Quite strange, because everything works fine with Kubuntu, Fedora and Linux Mint latest release.

I’ve tried the installation on my second HD, with a MBR partition table. Same.

From the BIOS, any changes to the boot priority/type (like UEFI on-off) seems to solve the issue, like i said, it seems that there any bootloader.

I’ve already checked the page concerning the bootloader reconfiguration from a live, but with no luck.

Even on my laptop with an SSD and Manjaro alone, nothing will work - and yes, the iso i’ve downloaded is ok, because it works on Virtualbox.

I’m out of options, after years of Linux Mint and Cinnamon, i’ve found my perfect desktop with KDE latest releases, and Manjaro seems to be a very good underlying OS for it…

Please help this poor newbie to solve his issue!

Thanks, and sorry for my bad english!

It’s a nice story, but this is a tech support forum. Nothing you said is useful.
Describe what actions you did, what tools you used, what command you ran, what errors you got, specific facts, not general descriptions and feelings.
You may find these helpful:




Good luck!

2 Likes

About a year ago (so, many versions back) after fresh new install (but not dual boot, just Manjaro) there was no boot flag on the boot partition. So computer was acting just like yours. I booted up with live USB, I ran gparted and with it I set the boot flag. After that it worked and booted.

Not sure if your case is the same, but I though to throw this out, can’t hurt checking it out :slight_smile:

You could also find some good idea what to do here:

3 Likes

Nice story you said?

Well, 4 years ago i won a national level competition for a nice story, seems that i’m still good after all :sunglasses:

For real, thanks for your help.

First of all, i’ve checked what AlManja suggested, but with no luck.
The flags “esp” and “boot” were checked.

Then i’ve done all the requested passage to recover the GRUB, and the situation changed… Somehow.

Now in the BIOS boot options an entry with “manjaro” just showed up… But, if i don’t boot from the menu, Windows will show his naughty face as everytime…
The real issue is that the procedure fued up the rest of the BIOS totally, apart from the boot menu, i cannot enter anymore and all i see is a fixed underscore on the left corner.
I’ve flashed the BIOS again and that erased everything apart Windows boot entry, then i’ve done again the procedure and fu
ed BIOS.

efibootmgr -v

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,0000,2001,2002,2003
Boot0000* manjaro       HD(2,GPT,7bcbfdad-8d4b-48bd-9197-5b19c47f4bcc,0xfa000,0x32000)/File(\EFI\Manjaro\grubx64.efi)
Boot0001* Windows Boot Manager  HD(2,GPT,7bcbfdad-8d4b-48bd-9197-5b19c47f4bcc,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.}....................
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC

parted -l

isco /dev/nvme0n1: 256GB
Dimensione del settore (logica/fisica): 512B/512B
Tabella delle partizioni: gpt
Flag del disco: 

Numero  Inizio  Fine   Dimensione  File system  Nome                          Flag
 1      1049kB  524MB  523MB       ntfs         Basic data partition          nascosta, diag
 2      524MB   629MB  105MB       fat32        EFI system partition          avvio, esp
 3      629MB   646MB  16,8MB                   Microsoft reserved partition  msftres
 4      646MB   115GB  115GB       ntfs         Basic data partition          msftdata
 6      115GB   142GB  26,2GB      ext4
 5      142GB   256GB  115GB       ext4

blkid

/dev/nvme0n1: PTUUID="29732672-96f9-4463-9276-72a76db29f2d" PTTYPE="gpt"
/dev/nvme0n1p1: LABEL="Ripristino" UUID="5CE8BBEAE8BBC096" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="f054d4a2-0fe7-48e8-9359-e93b7acaca6c"
/dev/nvme0n1p2: UUID="46BD-8A53" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="7bcbfdad-8d4b-48bd-9197-5b19c47f4bcc"
/dev/nvme0n1p3: PARTLABEL="Microsoft reserved partition" PARTUUID="81bc9a0e-9d14-4857-8b7d-363cf9b702a3"
/dev/nvme0n1p4: UUID="D416CAAF16CA9242" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a1cfd1d2-da26-4cd4-8c4c-c234974da5c8"
/dev/nvme0n1p5: UUID="7c4478e6-4e1a-40b7-a806-2094a0cc9384" TYPE="ext4" PARTUUID="af39be1b-25ae-48c3-912a-d172c940f790"
/dev/nvme0n1p6: UUID="f2ec65c0-b093-4abb-a6a3-3079945f8f91" TYPE="ext4" PARTUUID="65e54698-ead0-47ce-8063-f912ce54fb20"

findmnt -s

TARGET    SOURCE                                    FSTYPE OPTIONS
/boot/efi UUID=46BD-8A53                            vfat   defaults,noatime
/         UUID=f2ec65c0-b093-4abb-a6a3-3079945f8f91 ext4   defaults,noatime
/home     UUID=7c4478e6-4e1a-40b7-a806-2094a0cc9384 ext4   defaults,noatime

What’s the matter and how can i solve it? Thank you

sudo efibootmgr -o 0000,0001

Hi, i’ve already figure this out by myself and tried it, with no luck.

Boot order won’t change on reboot.

Sound like a misbehaviour of the BIOS.
Meanwhile, i managed to get rid of the Manjaro files in the EFI partition and the BIOS is now working again, like nothing ever happened.

It’s so strange! It happens only with Manjaro.

Additional info:

Laptop model: acer swift 3, SF315-50

I’ve noticed that in the EFI partition, there’s a dir called “hynside” too, apart from Windows, boot and (no more) Manjaro.

Secure boot is disabled.

Why?

You need to get it back. Use the 3rd link that petsam provided and do step 6 with the 2 commands in [additional uefi commands]

What’s
ls /boot/efi/EFI/hynside/
ls /sys/firmware/efi/efivars

Check out your bios-setup (F2?) and see if you can make ‘manjaro’ entry (after fixing it back) the default and show us how you did it.

Why?
You need to get it back. Use the 3rd link that petsam provided and do step 6 with the 2 commands in [additional uefi commands]

To see if the unaccessible BIOS was caused by the grub files, and as i stated, BIOS is now working again without issue.

And yes, now that i’m sure i can reverse everything, i’ll proceed with the steps, but…

Is what i’ve done in the first place.

Without these additional commands, no entry in the boot menu (F12) will appear.
With them, a manjaro boot option is available but then, the BIOS (F2) will stuck in a black screen with a fixed underscore.

As said, if i fix back manjaro as entry, i can’t enter the BIOS anymore. Only the boot menu (F12) is available. So this wont be possible.

.

Nothing?

[Swift3 killua]# ls /sys/firmware/efi/efivars/
A01LastSataPortPresent-89cb0e8d-393c-4830-bfff-65d9147e8c3b
A01WindowsMode-89cb0e8d-393c-4830-bfff-65d9147e8c3b
AACV-89cb0e8d-393c-4830-bfff-65d9147e8c3b
ACFB-89cb0e8d-393c-4830-bfff-65d9147e8c3b
ACFT-89cb0e8d-393c-4830-bfff-65d9147e8c3b
AcpiGlobalVariable-c020489e-6db2-4ef2-9aa5-ca06fc11d36a
ActiveVgaDev-59d1c24f-50f1-401a-b101-f33e0daed443
ACUB-89cb0e8d-393c-4830-bfff-65d9147e8c3b
AdministerSecureBoot-59d1c24f-50f1-401a-b101-f33e0daed443
AEBO-89cb0e8d-393c-4830-bfff-65d9147e8c3b
AEBT-89cb0e8d-393c-4830-bfff-65d9147e8c3b
AFBD-89cb0e8d-393c-4830-bfff-65d9147e8c3b
ASSN-89cb0e8d-393c-4830-bfff-65d9147e8c3b
ASTM-89cb0e8d-393c-4830-bfff-65d9147e8c3b
AuthVarKeyDatabase-aaf32c78-947b-439a-a180-2e144ec37792
BiosGuardStatus-9c57c6e2-4c78-42d9-9051-96b9d80c9c92
Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0002-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot2001-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot2002-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot2003-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootDevice-0a4cd120-ea2d-4aef-a4b0-b0c08cbbdbbe
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
BugCheckCode-ba57e015-65b3-4c3c-b274-659192f699e3
BugCheckParameter1-ba57e015-65b3-4c3c-b274-659192f699e3
BugCheckProgress-ba57e015-65b3-4c3c-b274-659192f699e3
certdb-59d1c24f-50f1-401a-b101-f33e0daed443
ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c
ConInCandidateDev-59d1c24f-50f1-401a-b101-f33e0daed443
ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
ConOutCandidateDev-59d1c24f-50f1-401a-b101-f33e0daed443
ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
CpuSetup-b08f97ff-e6e8-4193-a997-5e9e9b0adb32
CpuSetupVolatileData-b08f97ff-e6e8-4193-a997-5e9e9b0adb32
CurrentPolicy-77fa9abd-0359-4d32-bd60-28f4e78f784b
Custom-4570b7f1-ade8-4943-8dc3-406472842384
Custom-5432122d-d034-49d2-a6de-65a829eb4c74
Custom-72c5e28c-7783-43a1-8767-fad73fccafa4
Custom-a04a27f4-df00-4d42-b552-39511302113d
Custom-a41e9236-4d21-43b5-9379-ddd6fafe6603
Custom-b08f97ff-e6e8-4193-a997-5e9e9b0adb32
CustomPlatformLang-59d1c24f-50f1-401a-b101-f33e0daed443
CustomSecurity-59d1c24f-50f1-401a-b101-f33e0daed443
dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c
dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f
dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c
DynamicBar-39473de5-df3b-49a1-9fa6-41b35b36fa39
EPCBIOS-c60aa7f6-e8d6-4956-8ba1-fe26298f5e87
ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
FirstBootAfterFlash-59d1c24f-50f1-401a-b101-f33e0daed443
FixedBar-39473de5-df3b-49a1-9fa6-41b35b36fa39
FullReset-59d1c24f-50f1-401a-b101-f33e0daed443
IrsiInfo-5bce4c83-6a97-444b-63b4-672c014742ff
KEKDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c
Kernel_ATPSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
Kernel_EntRevokeSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
Kernel_RvkSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
Kernel_SiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
Kernel_SkuSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
Kernel_WinSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
Lang-8be4df61-93ca-11d2-aa0d-00e098032b8c
LangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
MemoryOverwriteRequestControl-e20939be-32d4-41be-a150-897f85d49829
MemoryOverwriteRequestControlLock-bb983ccf-151d-40e1-a07b-4a17be168292
MeSetup-5432122d-d034-49d2-a6de-65a829eb4c74
MeSetupStorage-5432122d-d034-49d2-a6de-65a829eb4c74
MTC-eb704011-1402-11d3-8e77-00a0c969723b
NvmeScan-89cb0e8d-393c-4830-bfff-65d9147e8c3b
OfflineUniqueIDEKPubCRC-eaec226f-c9a3-477a-a826-ddc716cdc0e3
OfflineUniqueIDEKPub-eaec226f-c9a3-477a-a826-ddc716cdc0e3
OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
PchSetup-4570b7f1-ade8-4943-8dc3-406472842384
PdtUpdVersion-103fcd92-a4e6-4a07-b458-f78c9db45256
PhysicalBootOrder-59d1c24f-50f1-401a-b101-f33e0daed443
PKDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c
PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
RestoreFactoryDefault-59d1c24f-50f1-401a-b101-f33e0daed443
RstOptaneConfig-4da4f952-2516-4d06-8975-65036403a8c7
RstSataV-193dfefa-a445-4302-99d8-ef3aad1a04c6
S3MemVariable-973218b9-1697-432a-8b34-4884b5dfb359
SaSetup-72c5e28c-7783-43a1-8767-fad73fccafa4
SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
SecureBootEnforce-59d1c24f-50f1-401a-b101-f33e0daed443
SecureFlashInfo-382af2bb-ffff-abcd-aaee-cce099338877
Setup-a04a27f4-df00-4d42-b552-39511302113d
SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
SgxSetupVariable-45b5acb9-0359-49be-adb1-49377bd607f7
SignatureSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
SMAA-89cb0e8d-393c-4830-bfff-65d9147e8c3b
SMAB-89cb0e8d-393c-4830-bfff-65d9147e8c3b
SMAC-89cb0e8d-393c-4830-bfff-65d9147e8c3b
SwitchableGraphicsVariable-b2b7c21f-1786-4a64-be69-16cef7647331
TargetHddDevPath-59d1c24f-50f1-401a-b101-f33e0daed443
Tcg2PhysicalPresence-aeb9c5c1-94f1-4d02-bfd9-4602db2d3c54
Tcg2PhysicalPresenceFlags-aeb9c5c1-94f1-4d02-bfd9-4602db2d3c54
Timeout-8be4df61-93ca-11d2-aa0d-00e098032b8c
TrEEPhysicalPresence-f24643c2-c622-494e-8a0d-4632579c2d5b
TrEEPhysicalPresenceFlags-f24643c2-c622-494e-8a0d-4632579c2d5b
UnlockIDCopy-eaec226f-c9a3-477a-a826-ddc716cdc0e3
VarErrorFlag-04b37fe8-f6ae-480b-bdd5-37d98c5e89aa
VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c
WBMN-89cb0e8d-393c-4830-bfff-65d9147e8c3b
WBOA-89cb0e8d-393c-4830-bfff-65d9147e8c3b
WBSN-89cb0e8d-393c-4830-bfff-65d9147e8c3b

What the heck is this!

Sorry, I’m asking here a quick question.
Will handle the rest much much later. Need sleep.

(When you had it working), You do not have a bootx64.efi in your efi entries.
Have you done the first command in [additional uefi commands] (the bootx64.efi one?) Any error when/if you do that command?

Good night.

Nope, the only thing is that i’m asked to choose if i want to overwrite the bootx64.efi. But not error.

Everything without issue, but then on the boot Windows takes the lead, no grub, no accessible BIOS.
Only boot menu, with an unchangeable boot order.

P.S. this is the first time that i see someone say sorry for a sudden and forced exit, seems that the rumors about the friendly community of Manjaro, are true :open_mouth:
O you’re just way too nice… Well, in any case, i’m the one who’s sorry for taking your time and patience, and i really thank you for your help.

DONE!

history

56  mount /dev/nvme0n1p2 /mnt/
   57  cd /mnt/
   58  rm -rf EFI/manjaro/ //get rid again of the grub files for a fresh grub install
   59  reboot
   60  efibootmgr //checked the situation. No Manjaro.

//from Dolphin i deleted the boot64.efi under EFI/Boot

   61  cp /boot/grub/x86_64-efi/core.efi /boot/efi/EFI/Boot/bootx64.efi
   62  update-grub

//here's the difference. According to the steps, usually i would do update-grub just after the grub-install

   63  efibootmgr //check the current situation. Still no Manjaro. (obviously)
   64  efibootmgr -c -d /dev/nvme0n1 -p 2 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"

//manjaro now is a boot entry as normal.

   65  efibootmgr -o 0,1,2

//i make sure that the boot order is the one i want.

   66  reboot
   67  history 

On the reboot, this time, BIOS was working.
I proceed to change the boot order, strangely, manjaro is still not present or, is not like it should be,

There are 3 entries: windows, the attached usb and a third entry with empty name.
Basically:

  1. windows
  2. usb

The third one, was Manjaro and changing it to the first place, finally kick me to the grub menu and now i’m reporting everything.

So in the end, the only two difference were: the deleted bootx64.efi before the copy.

Maybe the overwrite didn’t work till now? It would be strange. I’ve even used the -f option.
After that, the update-grub.

The issue has been solved, but i would like to know why the entry in the BIOS is empty and why all these problems in the first place, i mean, like i said before, Fedora/Ubuntu/Neon/Mint (well, the latest 3 are basically the same i suppose), didn’t give me this headache.

Morning. Good to hear in my otherwise normal grumpy mornings. :slightly_smiling_face:

That’s what I also guessed at (before I slept).
Your system is booting not the manjaro entry but the device entry (which is bootx64.efi)
And that’s why I asked if the 1st command (bootx64.efi) was performed.

And let’s take a look the latest 'efibootmgr -v ’ output from the terminal.

Your case is somewhat similar to this user who’s also on an Acer system.
At least, you can use and boot from bootx64.efi. Other systems are tied in with Microsoft or have to use its ‘keys’ (Fedora/Ubuntu/Neon/Mint). As a hint, in efibootmgr -v. the bootentry ending with “RC” other than the windows boot can only be selected. Entries without won’t.

Reminder, let’s have a look at your ‘efibootmgr -v’. Thanks.

Cheers, take care, see you around.

1 Like

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