I’m getting the above two errors messages showing on boot up,
I’v taken the lines out of my grub and run the sudo grub-mkconfig -o /boot/grub/grub.cfg (many times)
To no affect. As if I have a second grub somewhere and the deafult one is being used, as also I have no ‘quiet’ in my grub config but am not seeing the ‘boot up lines’ showing while booting, (as I do on my other Arch system)
This is my Grub config
so what am I missing ?
Can we see the contents of /boot/grub/grub.cfg and sudo efibootmgr
Here’s the /boot/grub/grub.cfg
[trevor@trevor-endeavour ~]$ sudo efibootmgr
EFI variables are not supported on this system.
That file doesn’t match the config file you posted in the first post. Was that from /etc/default/grub?
If so, please paste the full output from:
sudo grub-mkconfig -o /boot/grub/grub.cfg
findmnt --real
It does seem that ceratin updates have not been taken into account, I saw Windows boot in this file , it was on a second HD) but no longer have that, (wiped it for a debian , as wanted to trydebian )
That file doesn’t match the config file you posted in the first post. Was that from /etc/default/grub ?
Yes it was
OK, I have good news and bad news.
The good news is that the generated file you just posted is updated and correct.
The bad news is I typo’d the command and missed the -o so it was only displayed to the screen.
Try this:
sudo grub-mkconfig -o /boot/grub/grub.cfg
Then look at that file and ensure it is correct. It should be easy to tell if you search for the linux line. It should look like this:
linux /boot/vmlinuz-linux root=UUID=2c11fcb8-08c3-4172-9f8e-23b1b1266b4c rw loglevel=3 nowatchdog
As you can see, quiet has been removed.
Sadly no
What I noticed is that the Grub cfg dates from Decemeber
There’s a new on dated today, and Linux is Quiet
Stupid question, Can I just replace the grub.cfg by the grub.cfg.new ?(renaming it of course)
Can try deleting the old grub.cfg and then running it again.
I am not sure why it is failing to overwrite it.
Sill no luck, I deleted the grub.cfg and reran the sudo grub-mkconfig -o /boot/grub/grub.cfg
It just updates the grub.cfg.new and does not create a grub.cfg file
Does sudo mv /boot/grub/grub.cfg.new /boot/grub/grub.cfg work?
Yes that works though I have a X (cros) on the file which I didn’t have on the ‘old’ grub.cfg
Then ran sudo grub-mkconfig -o /boot/grub/grub.cfg just to test
It just creates a grub.cfg.new file again
ls -l /boot/grubls -l /boot/grub
total 72
drwxr-xr-x 2 root root 4096 26 sept. 2021 fonts
-rw------- 1 root root 15254 20 janv. 17:57 grub.cfg
-rw------- 1 root root 15254 20 janv. 18:03 grub.cfg.new
-rw-r–r-- 1 root root 1024 26 sept. 2021 grubenv
drwxr-xr-x 2 root root 20480 22 déc. 17:28 i386-pc
drwxr-xr-x 2 root root 4096 22 déc. 17:28 locale
drwxr-xr-x 3 root root 4096 21 déc. 13:58 themes
-rw-r–r-- 1 root root 150 29 oct. 2021 unicode.pf2
lsblk -fm
Please surround the output with lines of 3 backticks (```) before and after the output.
Makes it easier to read.
It looks like it creating a .new file because there is an error in /etc/grub.d/proxifiedScripts/linux.bak
Hope this is readable
Not sure what you mean by backticks (```) before and after the output
I read that a cfg.new is created when a default grub is wrong, but cannot see any errors
Have you used grub-customizer ?
For info
no
Or if I did I do not remember
It is not on my system now
That file isn’t something that would normally be present.