The latest update to the stable branch print a warning during boot that it could not resume from a specific UUID number, then it prints “Starting Manjaro” and proceeds normally.
I am still new to Manjaro and found a new file called “/etc/default/grub.pacnew” which has this line:
So it looks like the pacnew file wants users to remove the resume=UUID=FOO part. I did that manually in /etc/default/grub, and ran sudo update-grub, then restarted. I left out the “quiet” keyword like before.
This time, there is a bootup message like “Resume device not found”, then it prints “Starting Manjaro” and proceeds normally.
How to prevent that warning?
I read somewhere that specifying UUID is good for boot security, though I don’t know details. Should I put the UUID line back? If so, what is the correct format to prevent that warning?
Where can I read boot log messages from grub before the “Starting Manjaro” message? I looked in journalctl -b but there was nothing like that message and there is no file called /var/log/boot.log like my previous distros. Where are those messages logged on Manjaro?
A .pacnew is only a suggestion, based upon upstream defaults. If you use suspend-to-disk, then you do need that “resume” line, and the UUID should be that of your swap device.
When I run sudo dmesg | grep -i resume I get no results at all. Same also with sudo dmesg | grep -i uuid. But those messages go past at the start of boot before “Starting Manjaro” and they go by so quickly I cannot write them down.
Does dmesg store grub messages as well as kernel messages? The messages I get are before “Starting Manjaro” so I did not think they were coming from the kernel but I could be wrong.
No, it only starts running when the kernel boots. It’s the kernel’s ring buffer.
If it’s really coming from grub — which I doubt, because I think it would rather be coming from the initramfs — then you can try removing the resume hook in your /etc/mkinitcpio.conf — it’s in the lower part of the file — and rebuild your initramfs with…
That fixed it. Thanks! Now on booting it said “mounting UUID (something) on real root” and proceeded with “Starting Manjaro”.
Interestingly, still nothing shows up for sudo dmesg | grep -i "real root" so I don’t know where that message gets logged for my own reference, but the main problem of that boot warning is solved now.
Note that you will not be able to hibernate without the resume hook, if you are using the classic hooks in the mkinit. If you do not use hibernation it is ok, if you use it you may want to check if you are on the newer systemd hooks (which are now the defaults and you have another pacnew for the mkinitcpio.conf file).
Similar discussion here
Your hooks can probably look like this, if you do not use encryption
