Yay system update made boot/efi's vfat an unknown type of file system, unmountable esp

Sounds fine. By “partition”, do you mean the defective original partition, or do you hint at the awry duplication without a partition table?

testdisk can help restore the original partition.

this is an advanced tool so use at ones own risk

1 Like


What you need learn first is to make solid backups. Everything you mentioned customizing can be protected by making backups. Each OS is prone to failures, not having a strategy to be prepared for this is not the fault of the OS.

Yes, I know, getting this kind of advice stinks in your situation and totally doesn’t help you now, but whining about the allegedly unreliable OS doesn’t help you either.

I very doubt yay had anything to do with your problems, and do not use grub-customizer.


Again I do not understand what you want to say with your very short post.


Yes, fully correct.

I did not do that. You made that up. I do not say EOS is any more unreliable than other operating systems. I agree with your: Each OS is prone to failures.


If you had read at least the most important passages, you would know the fateful PC session consisted of only that yay system update. Nothing was done before or after yay completion. So what else could have been the problem’s trigger/catalyst at least? (I do not speak about a possible deeper root cause.)

I think I never used it on or inside EOS, only installed it prophylactically. I had got used to install it on every Linux distri I use. But while I used it on other ones on other PCs, EOS’ grub-customizer probably was not applied. The bare reason for that is grub-customizer was just my tool for repairing a “distri B” via a “distri A”, but none of the distris on that PC has had boot failures yet. On that PC, EOS is the first child of sorrow regarding boot failures.

And I already learned my lession: Never use or install grub-customizer under any circumstances. Okay, I got that and will respect it. I already removed grub-customizer from my other partitions. No need to repeat this same lecture endlessly.

Unfortunately just because you don’t speak it doesn’t mean its wasn’t the actual cause and the update only triggered it.

This is like keeping a water balloon in your back pocket to keep you dry if it rains.

It sounds like you never used it, but be careful: uninstalling Grub Customizer does not undo the damage it has caused. Further intervention is needed, see here: [FAQ] Why you should NOT use grub-customizer

I think it is not accurate to implicate yay in this mess. If this thread has revealed anything, it is that your system has been recklessly misconfigured in multiple ways. With so many bootloaders and conflicting initramfs generation methods in use, it’s no wonder an issue has finally been encountered.



That’s exactly what I wanted to express with my words. Of course I cannot fully exclude such. I think you got me wrong on that. Nevermind.
But like I wrote: I think I never used (only installed) grub-customizer app on or under EOS.


As I still do not know what grub-customizer does, does not, can do and cannot do, I cannot judge that. What its installation was intended to achieve was keeping a bottle of stale water in the back pocket for battling thirst a bit even if there is no water around for a long period.

I already explained that stand more than once.

How do you even know that was before the yay update? How do you know the visible mess was not created by Ubuntu’s boot-repair app first used after that boot failure occured first – or by any other amateurish repair effort?

Do I get it right that rEFInd is also outcast or yikes or similar?

:man_shrugging: I don’t know what you are trying to say.

Because I know what yay does. :face_with_hand_over_mouth:

Not at all! rEFInd is awesome. I was more referring to this whole mess of a situation:

Nevermind, unimportant.

I did not imply that was done by yay. I asked


rEFInd was installed wittingly. systemd-boot was probably added by the Ubuntu-based distri.
Is the rest outlandish for a multi-boot system?

As mentioned before: by lack of knowledge/mistake – my fault. I understood dalto it is not bad, no actual problem. Correct?

I don’t have a clue. Is this bad? How could they have been created?

I can understand if english isn’t your first language which is some of the confusion here. You actually do imply that it was done by yay.

If you didn’t understand it why did you install it?

Honestly seeing your threads here I would say you need to learn a lot. You need to go back to the basics because you need to learn how to do things. You obviously have no real experience using a real Linux System. Arch and those based on arch maybe more than you can handle right now. Maybe learn more about the system before making judgment calls of what could be wrong?

They are automatically created. How long have you been using Linux? This is common knowledge to us around here. The fact you don’t know says your trying to be more advanced that you are. Slow down who you racing against?

Maybe learn to drive before buying a car.

1 Like

Yay system update made boot/efi’s vfat an unknown type of file system, unmountable esp

@Tako is this issue even still present?

resolved rebuilding initramfs to correspondent with installed kernels?
system is fully up to date?

1 Like

It’s just a lot going on is all. It is clear you are experimenting.

Just to clarify my original comment: I am not critical of the fact that you have misconfigured this or that in the course of your experimentation. It’s your computer; you should feel free to tinker as much as you like. Install Grub Customizer, add one hundred bootloaders, hack around with your initramfs generation routine–whatever! You should feel empowered to do whatever you want. Break it, learn to fix it, break it again.

What I took issue with was how you were openly claiming Yay borked your install, like it is some broken or untrustworthy tool. You even chimed in on other people’s threads to link back to this one and announce the danger of using Yay, because at any time it could mysteriously break your system for no reason. I was just saying I think that stance is unfair to Yay.

:man_shrugging: I have never had any issues with Yay, ever. Do you think I am just lucky?

Like I said: I think it is good to tinker, experiment with your system, and learn. But when something becomes broken, your first instinct should not be to deny responsibility and blame one of the tools you are using. A better–or at least more humble–place to start would be “I’m not sure if I made a mistake somewhere, but something went wrong after my last update.”


It isn’t outlandish but it makes it much harder to troubleshoot a problem like this one. Especially when most of those changes were made after the problem already existed.

Yes, it is not a problem.

It isn’t bad but it means your grub config has been modified. If this change was made, it is likely/possible that other changes were made as well.

Probably by enabling it in the grub config.

There are two things I should probably point out.

The first is that this problem probably would have been easy for us to help you fix if you had not made all these other changes. At this point, it is very difficult to follow the breadcrumbs back and figure out all the things that are wrong. Don’t take this the wrong way, trying to troubleshoot a problem on your own is an admirable quality and I am not criticizing you for it. However, it also has probably led to a situation that is difficult to resolve without access to your physical machine.

The second is something that most people hate hearing so I don’t usually bring it up in these situation. However, I think it is relevant in this case. A system update causing breakage on Arch is rare.(Although it does happen) The vast majority of the time when someone perceives an update has caused breakage, it caused by some action taken by the user or their hardware. Some of the common ones include:

  • They have removed packages needed by the system update process
  • They are holding some packages back causing a partial update scenario
  • They have changed some configuration files and the update caused that configuration to take affect
  • They are dual-booting Windows and have not disabled “Fast-startup”
  • They have installed grub-customizer
  • They have failing hardware
  • They have added third party repos and those packages are disrupting the process. For example, the ALHP repos.
  • The system is broken in some way but this was not brought to light until the boot images were rebuilt by the update process.

This is why so many people are becoming frustrated by you claiming that yay has broken your system in various topics.