You might try
apt-get update -f
or
apt-get upgrade -f
Otherwise, if it has been reported , just wait.
2 Likes
Good advice.
I would also look at the following
Reconfiguring the dpkg Database
sudo dpkg --configure -a
sudo apt clean
command tells dpkg to configure all packages that are unpacked but not yet configured cleaning any issues
Another suggestion for you instead of dual booting
https://www.xda-developers.com/reasons-embrace-virtual-machines-instead-dual-booting/
I know several on this site do just that. But as I have no need or want for windows not my thing
Neville,
Here is the part of the /boot/grb/grub.cfg file of interest:
menuentry 'LMDE 6 Faye' --class linuxmint --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-ff1ed265-9
90e-4173-8ed6-06bba4771c20' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd3,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd3,gpt3 --hint-efi=hd3,gpt3 --hint-baremetal=ahci3,gpt3 ff1ed265-99
0e-4173-8ed6-06bba4771c20
else
search --no-floppy --fs-uuid --set=root ff1ed265-990e-4173-8ed6-06bba4771c20
fi
echo 'Loading Linux 6.1.0-31-amd64 ...'
linux /boot/vmlinuz-6.1.0-31-amd64 root=UUID=ff1ed265-990e-4173-8ed6-06bba4771c20 ro quiet splash
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.1.0-31-amd64
}
It shows: set root=‘hd3,gpt3’ which is correct. The root partition is on the 4th drive, partition 3 (sdd3), with partition 1 (sdd1) as /boot/efi and partition 2 (sdd2) as swap. I’m assuming the values listed are using a 0-based numbering. So my 1st disk (0) is my Windows system disk (sda2).
I’ll try your 2nd suggestion next (press ‘e’ at the grub screen.
I tried sudo apt-get upgrade -f and got the same error messages as before. The -f swithc is not valid with apt-get update.
1 Like
I verified the UUID in this line is correct. It is sdd3, by linux /root partition.
1 Like
Paul,
I tried these suggestions. It didn’t change anything.
The log includes this:
update-initramfs: Generating /boot/initrd.img-6.1.0-32-amd64
I: The initramfs will attempt to resume from /dev/sdd2
I: (UUID=e3747d5c-a8a2-4d5f-ac04-52cd93139b7a)
I: Set the RESUME variable to override this.
The UUID is my swap partition. Should it be looking elsewhere to “resume”?
1 Like
Yes, nothing wrong there
You will get the same there.
That is OK too, assuming the UUID is correct.
What do you have in /etc/fstab?
Thanks I could not remember whether to use update or upgrade with - f.
Is that correct?
I am not sure about that.
It is possible that the boot process uses swap for temporary storage. Will see if I can find out?.. no the boot process does not use swap. … I think your initramfs may need updating? There is a command for that… I will have to look it up.
Use update-initramfs -u … that is safe
Also
you might try doing
update-grub
as root of course.
I am running out of ideas.
That boot failure is a kernel panic… it could not find something?
Does it always boot properly if you boot straight into !inux from poweron?
If it is only a problem when you come from booting Windows first then we must think about what Windows is doing to your BIOS?
1 Like
I am out of ideas totally, sorry, but read with interest the replies of Neville
Would changing the boot order make a difference ?
Linux first then windows ?
Or running a VM inside linux ?
1 Like
Linux is the 1st entry in the Grub men. Windows is 3rd.
Don’t want to go the VM route. I’ve always had problems with VMs behaving badly, and they don’t (easily, if at all) have access to my data drives which are outside of the VM.
1 Like
Neville, I tried your suggestion update-initramfs -u. System boots OK, whether allowing Grub to default to LMDE or if I select it. But this has been inconsistent in the past, so I’m not sure yet whether this fixed that problem.
However, I still get the same “not yet configured” errors when running apt-get autoremove or apt-get upgrade.
Following some of the suggestions from your link to the askubuntu.com item, i find this:
ken@LMDE:~$ kernelver=$(uname -r | sed -r 's/-[a-z]+//')
ken@LMDE:~$ echo $[kernelserver]
0
ken@LMDE:~$ dpkg -l linux-{image,headers}-"[0-9]*" | awk '/ii/{print $2}' | grep -ve $kernelver
linux-headers-6.1.0-12-amd64
linux-headers-6.1.0-12-common
linux-headers-6.1.0-31-amd64
linux-headers-6.1.0-31-common
linux-headers-6.1.0-32-amd64
linux-headers-6.1.0-32-common
linux-image-6.1.0-12-amd64
linux-image-6.1.0-31-amd64
ken@LMDE:~$ uname -r
6.1.0-31-amd64
So it looks like I have 3 kernel versions installed (12, 31 & 32). Version 32 is the one that the error messages say is not yet configured, and 31 is the active version. Should I purge the headers & images for versions 12 & 32, followed by
sudo apt-get auto-remove && sudo apt-get clean && sudo apt-get update && sudo apt-get upgrade
as described in that article? Would that also re-install version 32?
1 Like
I would keep version 12.
You need at least 2 working kernels
So purge 32 , and try those commands
It will probably reinstall 32… but no harm done… it will just repeat the error, unless they have fixed it.
I think you have to wait a while
The may be a way of blacklisting 32, so you can wait for 33.
2 Likes
I tried:
$ sudo update-grub
/usr/sbin/grub-mkconfig: 1: /etc/default/grub: #: not found
The file /etc/default/grub does exist. I don’t know what isn’t being found but it seems to be complaining about the # at the beginning of line 1. I previously made a 1-line change to set the default timeout from 5 to 15 seconds. For context, here are the 1st 12 lines of the file:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
# KL change grub timeout from 5 to 10
#GRUB_TIMEOUT=5
GRUB_TIMEOUT=15
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
1 Like
I think I found the update-grub error problem here:
https://ubuntuforums.org/archive/index.php/t-2154325.html
It seems that line 1 doesn’t start with #, but with an invisible and 0-length character before the #. I edited the file by pressing the Delete key at the beginning of the file. The # was still there, and the first line then changed to blue (comment line). The update-grub worked without generating an error.
ken@LMDE:~$ sudoedit /etc/default/grub
ken@LMDE:~$ sudo update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/linuxmint/theme.txt
Found linux image: /boot/vmlinuz-6.1.0-31-amd64
Found initrd image: /boot/initrd.img-6.1.0-31-amd64
Found linux image: /boot/vmlinuz-6.1.0-12-amd64
Found initrd image: /boot/initrd.img-6.1.0-12-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
ken@LMDE:~$
Then I did this:
sudo apt-get auto-remove && sudo apt-get clean
and
ken@LMDE:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
linux-image-6.1.0-32-amd64
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 409 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 550759 files and directories currently installed.)
Removing linux-image-6.1.0-32-amd64 (6.1.129-1) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-32-amd64
/etc/kernel/postrm.d/zz-update-grub:
Generating grub configuration file ...
Found theme: /boot/grub/themes/linuxmint/theme.txt
Found linux image: /boot/vmlinuz-6.1.0-31-amd64
Found initrd image: /boot/initrd.img-6.1.0-31-amd64
Found linux image: /boot/vmlinuz-6.1.0-12-amd64
Found initrd image: /boot/initrd.img-6.1.0-12-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
No more “unitialized” error!
And i found that I’m now using kernel version 31
ken@LMDE:~$ uname -r
6.1.0-31-amd64
Hopefully this fixes everything!
Thanks everybody for your helpful suggestions!
4 Likes
I wonder how that invisible character got into /etc/default/grub?.. maybe an editing mistake?
So it autoremoved kernel 32.
Wait a while before you do an update, or it may try to put 32 back, and fail again.
Well done
2 Likes
Bravo for your efforts on such a minor detail not easy to spot.
2 Likes