I’m also facing issues on update. Something seems broken on initfrs. I’m completely clueless.
in my opinion, there is no way this should have been labeled as a “stable” update
i agree with purplemunchies - the grub check should have been handled much better than it was, at least with a script to check the config before rebooting or something
i use EFI and followed the instructions in the announcement, running the following…
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
sudo grub-mkconfig -o /boot/grub/grub.cfg
and the system wouldn’t boot until i messed with the boot order in setup
it was always set to UEFI OS on the SSD, but this now fails, so i changed it to the only other option “manjaro” and that works, but i came across this fix largely by dumb luck
this should not have happened
4 Likes
I did the update with MBR (UEFI/Secure Boot disabled) on both of my systems and no problems, im not even manually updated my grub bootloader as @philm suggest in know issue, because i updated 40min after Philm uploaded the stable update and at this time the know issue was empty.
But i still have no idea if i still should force this reinstall now…
At the endof the day its not a requirement to manually update…
its only advised.
I do the easy Linux way and just created a simply timeshift backup on a external hdd and have a Manjaro USB Stick ready if anything goes wrong… its not this hard to be prepare.
On the vote for this update, I chose:
The issue could be much more severe but I was lucky this time so the issue ended up basically a mental shock and some extra effort on investigation. What do I mean?
For the past some updates, I normally just re-book at the prompt after installing the update. But this time something told me to check about the known issues post on this update. Thanks for the note on grub update! So if I re-booted as usual, I might have ended up with trouble.
But the instruction plus the so-called details on grub update were not too clear. Do I have BIOS/GPT (or chatGPT?) or do I have EFI? Sure, I knew that long ago when I installed Manjaro, but now I totally forgot, and I don’t even remember on how to find out. After some searching and reading, I found out with:
$ sudo fdisk -l
Device Start End Sectors Size Type
/dev/sda1 34 2050047 2050014 1001M EFI System
/dev/sda2 104450048 124930047 20480000 9.8G Linux swap
/dev/sda3 2050048 104450047 102400000 48.8G Linux filesystem
/dev/sda4 124930048 490234718 365304671 174.2G Linux filesystem
After seeing “EFI System” above, I made a bet (yes!) to go with EFI approach. But the problem is hardly solved. The detailed info page says:
EFI System
Info You need to be in chroot for this procedure.
Reinstall grub
root # grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck COPY TO CLIPBOARD
Update the grub configuration
root # grub-mkconfig -o /boot/grub/grub.cfg COPY TO CLIPBOARD
First question was: how to be in chroot? After some checking, it turns out I could just use sudo. But then there are two things listed above. Should I do one or the other, or should I do both? Again some further searching and reading.
So I did both. Then rebooted. There is no problem so far. But you see this is not a smooth update.
7 Likes
Copying a file in Thunar (in Xfce) to a cifs-mounted Windows location fails.
Dating the problem: 1. As of the “2023-12-13” update, the problem did not exist. 2. After the “2023-12-15” update, the problem does exist. 3. The “2023-12-23” update does not fix the problem.
I posted to support: Copying in Thunar to cifs-mounted Windows locations fails (after update)
Sorry if this reply duplicates anything or is not in proper format. First time replying to a Stable Update post.
There have been a number of updates recently so I do not know precisely when my my menubar disappeared from the application launcher button (Manjaro start button) and I can’t identify the place/app/setting to turn it back on.
6.1.69-1-MANJARO (64-bit) Kernel / KDE Plasma 5.27.10
Hi @Nicomo
Try right-clicking and selecting ‘Show Alternatives’; Choose another menu layout, and confirm it. Using this same procedure to again select your original menu layout may (or may not) fix that. It’s worth trying, anyway. Cheers.
Thank you very much for your quick response, the alternatives are interesting but they also seem to have an issue in list view - in that there is no highlighting menubar to show which application(menu_item) your mouse is hovering over.
The whole grub thing is actually strongly recommended to avoid future problems and not really necessary right now. If you are up to date, your grub should be at 2.12rc and the update bumps it to 2.12 final. There seem not to be any breaking changes…because i honestly forgot to update the first stage and rebooted just fine.
And BTW, if you update the grub efi part using chroot/usb live session, make sure to use the 2023-12-23 iso from yesterday, because it is the first to use that version.
Also, to check the grub first stage version, on the grub menu, hit c for command prompt - the version appears at the top. Then hit esc to go back.
5 Likes
Interestingly, that’s not the case with my (just updated) KDE (wayland). What you describe might not be a result of the update, despite the apparent timing.
How come this isn’t mentioned in the devs release information then?
I browsed through the documentation and official announcements and I didn’t find any such recommendation for simply updating to a newer version.
The Arch wiki says:
Warning: Update/reinstall the boot loader (see #UEFI systems or #BIOS systems) if a new GRUB version changes the syntax of the configuration file: mismatching configuration can result in an unbootable system.
The own Manjaro wiki says it’s only necessary if you suffer an “unfinished update”.
Everything I’ve read suggests you just need to make sure the config file gets newly generated, which already happens automatically with the normal update. If something goes wrong with the grub update, the log would say so and inform the user to maybe investigate the problem.
And since the previous version of the package was apparently “2.12rc1” I fail to see how this recommendation applies here anyway. Maybe if you are on a very old version, but then this should be mentioned in the post accordingly.
Personally I updated without any additional intervention.
Edit:// Looks like some additional information was just added to the post which at least explains the concerns.
4 Likes
Had this same GRUB boot failure after updating, had to set boot order in BIOS again to resolve this boot issue here as well and system booted up as normal.
I think it should be noted in the “known issues and solution” post regarding this grub update.
Thank you for the updated Known Issues entry.
I’m stuck with grub unable to find initrd. I have been seeking for help here:
Moderator edit: Removed duplicate embedded photo
Atleast in Pamac GUI it will automatically update your Grub… everything explained here already, just read the comments.
Do you have a lot of apps and widgets on the menubar ? If yes, did you try to unzoom with ‘’-‘’ when you right click and edit the menubar?
1 Like
But Pamac will made the manual changes?
At least on my understanding, the recommendation still to manual update the grub…
Pamac updates only the package. It does not reinstall the first stage on the mbr or efi.
It should be, its always the same… prepare yourself if something goes wrong,
this update is no big differend than others.
Create timeshift on a external HDD/SSD and prepare a Manjaro USB Bootstick (just in case).
So even if we don’t have any problems after the update, we still should reinstall Grub?
If this is the case… why Philm doesn’t make this clear?
The wording in the announcement is “may need” and “recommended” not obligatory/must. I personally have done it to avoid future problems. At some point pamac will update again the package/second stage and it may be then incompatible with a ver old first stage and the system will not boot. It is probably more important for older installations (mine is from this year).
I guess the process could be automated with pamac hook but for now it is manual.