Windows nuked my EFI partition

Please post the output of the commands asked for above (x2 :innocent:) from your live usb.

Therein lies the problem. Windows has access to the drive as it is FAT32. Is there a way to block that?
And I will post the command output momentarily.

Yes, but what did Windows did to nuke your Manjaro EFI? Or how? I've got several multi-boot systems with Windows and other GNU/Linux operative systems. All installed in UEFI mode with their own ESP. I have never experienced nuked ESP:s for my GNU/Linux OS:s, not even after Windows' feature upgrades every sixth months or so.

Well, if you did that you'd just be struggling with Windows not booting instead of Manjaro. And fixing a broken Windows bootloader is way more of a ballache than reinstalling grub.

If you create a second EFI partition for Manjaro to use, install grub on it, and amend your fstab that would probably stop this from happening again.

I haven't tried doing that post install myself so I'd suggest doing some digging to make sure their aren't more steps to it that I'm missing.

I think that's the issue, they're currently sharing the ESP between Windows and Manjaro.

1 Like

I took it that OP has installed Manjaro's Bootloader in it's own ESP. But perhaps not.

Commad Output
Model: ATA ST1000LX015-1U71 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  274MB   273MB   fat32        EFI system partition          boot, esp
 2      274MB   290MB   16.8MB               Microsoft reserved partition  msftres
 3      290MB   528GB   528GB   ntfs         Basic data partition          msftdata
 5      528GB   999GB   471GB   ext4
 4      999GB   1000GB  839MB   ntfs         Basic data partition          hidden, diag


Model: General USB Flash Disk (scsi)
Disk /dev/sdb: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 2      2960MB  2964MB  4194kB  primary               esp


Model: Micron_2200V_MTFDHBA512TCK (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name                          Flags
 1      1049kB  274MB  273MB   fat32           EFI system partition          boot, esp
 2      274MB   290MB  16.8MB                  Microsoft reserved partition  msftres
 3      290MB   354GB  354GB   ntfs            Basic data partition          msftdata
 5      354GB   355GB  538MB   fat32                                         boot, esp
 6      355GB   388GB  33.6GB  linux-swap(v1)                                swap
 7      388GB   455GB  67.1GB  ext4
 8      455GB   511GB  56.1GB  ext4
 4      511GB   512GB  682MB   ntfs            Basic data partition          hidden, diag


I followed the instructions under [HowTo] Dual-boot Manjaro - Windows 10 - Step by Step , so however it decides to install GRUB. Continue with the instructions as normal?

Interesting, two EFI partitions.

And ext4 partitions on both disks.

What is /dev/sda used for?

Dev/sda is just a mass storage disk. It doesn't have any OSes on it, and the efi partitions on it can be removed. I just... have never gotten around to it. Both OSes are on the NVMe drive

Fair enough. I'd shrink down that last ntfs partition on the nvme drive by a few hundred mb and turn it into a second ESP to use for Manjaro. How to do that step by step I can't tell you because I haven't done it before.

(or don't and just fix your boot every 6 months)

EFI PARTITION
Select the unpartitioned space → Create
a. Size → input 512
b. Filesystem → select FAT32
c. Mountpoint → select /boot/efi
d. Flags → check boot and espOK

The above is point 6 from the instructions you have linked to. Did you perform the step c for the Manjaro's bootloader to get installed to its own ESP?

Yes, I did.

But why? @MSS has got already two Fat32 partitions on the nvme disk. One for Windows and one for Manjaro. Perhaps re-installing the bootloader could resolve the issue:
https://wiki.manjaro.org/index.php?title=Restore_the_GRUB_Bootloader

I'm skeptical :smile:

It would have detected that there was already an EFI partition if you was installing Manjaro after Windows and asked if you wanted to use it.

I'm curious about that EFI partition on your storage drive though, did that disk originally have Windows on it? It must have had an OS on it at some point if you created an ESP for it. You said before, sorry it's like 3 am.

I'm under the impression that both OS's are using the ESP on the second disk, and that the ESP on sda is just a relic from past adventures. Maybe install grub on the ESP on sda if it isn't being used for anything else?

Oh so there are two on the nvme disk, now I'm well and truly confused. See earlier point about it being 3am.

Yes, the drive once had Win10 on it. The EFI partition is completely unused. I'm unsure of what you're saying-Do you mean go forward with fixing the bootloader in instructionset one (Using livecd v17.0.1 (and above) as grub to boot OS with broken bootloader)? Or go by instructionset two, (https://wiki.manjaro.org/index.php?title=Restore_the_GRUB_Bootloader)?

Don't worry about it. Ask what you need, and I'll try my best to provide.

They got two ESPs on the second disk, partition 1 and partition 5. I thought perhaps partition 5 could be a good candidate for installing Manjaro's bootloader.

Model: Micron_2200V_MTFDHBA512TCK (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name                          Flags
 1      1049kB  274MB  273MB   fat32           EFI system partition          boot, esp
 2      274MB   290MB  16.8MB                  Microsoft reserved partition  msftres
 3      290MB   354GB  354GB   ntfs            Basic data partition          msftdata
 5      354GB   355GB  538MB   fat32                                         boot, esp
 6      355GB   388GB  33.6GB  linux-swap(v1)                                swap
 7      388GB   455GB  67.1GB  ext4
 8      455GB   511GB  56.1GB  ext4
 4      511GB   512GB  682MB   ntfs            Basic data partition          hidden, diag


Both of those links contain instructions for reinstalling the bootloader, they're just written by different people (or possibly not)

Yes, I see that now and I agree.

So to conclude, we suggest that OP go ahead and reinstall grub on nvme5?

1 Like

Partition 5 is the EFI made when I installed Manjaro originally. GRUB, if my understanding is correct, would have already been installed there. I would prefer to not have any system-critical components on sda, as a note. So go forward with the replacement reinstall of GRUB?

It should have at the first place.

By the way, after installation of Manjaro, did you go to the bios settings to put Manjaro at the top of the boot devices?

Yes. That was the first thing I checked-"Oh, I must have moved it by mistake!"
Moving Manjaro to the top of the list does nothing, leading to now. I tried to check the bootloader in Win10 after resetting ESP and boot, along with my mountpoint, but got the generic "You must be an admin to open this drive".

Oh you know what I bet that's what it is, It's the only explanation that makes any sense if they actually do have their own ESP's.

It wouldn't be unusual for Windows to move itself back to the top after a feature update. In any case, yeah if moving Manjaro back to the top of the list doesn't work or the entry is missing, then go ahead and reinstall grub.

This is weird.

Forum kindly sponsored by