Possible Grub or encryption problem?

[Fordy]

Hello!,
Iḿ using 20.04 with Plasma 5.18.8

I set up a dual boot, with Win7, on this machine a couple of years ago and then had to leave it completely alone for personal reasons. The dual boot option was running ok at that time. Recently I thought i would give it another go.
Now on boot up I don get the OS choice menu, which is one problem. The other problem is, once booted into Kubuntu I cannot access an encrypted drive, when I try I see this error

"An error occurred while accessing '464.5 GiB Encrypted Drive', the system responded: An unspecified error has occurred: No such interface “org.freedesktop.UDisks2.Filesystem” on object at path /org/freedesktop/UDisks2/block_devices/dm_2d0"

I thought these 2 problems might be related. Which one should I tackle first? The Grub/ boot issue or the encryption/ drive issue?

Any tips on how to approach either problem is appreciated as Im still a newbie really!

Thanks very much!
Fordy

[Fordy]

Just to add to this.... I opened the case to remind myself what drives are installed and there is only one 500gig SSD drive. So I guess that means that I never had the multi boot setup on this machine at all! The only FAT partition is Fat 32 of 512mb so there couldnt have been a Windows install as well. So it can be a Grub issue then. Í must have set this up on another box I have in storage.

There doesnt seem to be a problem accessing the main drive and the machine seems to be running ok. On boot I have to unlock the encrypted drive - sd3 - which works fine and the OS loads. Itś just in Dolphin that I see 2 drives listed. One is shown as encrypted, 464gig, which gives the above error when I try to access it and the other shows as 463gig and can be browsed just fine. Confusing for sure but perhaps I don even have a problem here_ Can anyone confirm please?

Partition manager is also showing 2 devices. Not sure what is going on here or if anything needs to be fixed at all

[Snowhog]

What does your /etc/fstab contain?

[Fordy]

Hi Snowhog and thanks for your reply. Here it is

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/vgkubuntu-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda2 during installation
UUID=77c82598-9ce7-531b-843h-8dw26k8l41b8 /boot ext4 defaults 0 2
# /boot/efi was on /dev/sda1 during installation
UUID=E7C9-E4E7 /boot/efi vfat umask=0077 0 1
/dev/mapper/vgkubuntu-swap_1 none swap sw 0 0

This seems like it might point to another problem Im having, that when I try to upgrade 20.04 to 22.04 the installer reports that /boot does not have enough free space. Not sure if that is relevant though.
Thank you!

[skyfishgoo]

when I try to upgrade 20.04 to 22.04 the installer reports that /boot does not have enough free space.

it means your boot partition is full because you have too many kernels saved in there.... if you can't make the partition bigger then you just need to uninstall some of your old kernels

normally your system should keep you at 3 (your current and two older backups for recovery)... if your grub shows a long list of other kernels under recover options, then that is why.