[RESOLVED] Kubuntu, dual boot, stuck on grub that constantly scrolls grub> down the screen

[Gazzer]

Hi,
I have Kubuntu & Windows 10.
Yesterday my CPU went to 100% so I rebooted and now I get black screen, with grub> scrolling down the screen.
If I go into UEFI motherboard screen and directly select Kubuntu, i see the normal grub screen and I can boot into Kubuntu successfully.

What is the solution please, I did try " boot-repair-disk" but that did not solve the problem.
I have added zip file with "boot-repair" full info about boot etc.

Thanks

[Schwarzer Kater]

Hm, I only know this effect when you hold down the [Esc] key during boot…

Can you type something in? Then

• type in: normal and hit [Return]
• immediatly press [Esc] - you should be in the GRUB boot menu now…

After you have booted the system try reinstalling GRUB to the boot drive. Open the Konsole terminal emulator and

• enter sudo update-grub
• enter lsblk -f to see on which drive /boot/efi is located
• enter sudo grub-install /dev/[path to the drive], e.g. /dev/sda or /dev/nvme0n1
• reboot and test if the problem still occurs

[Gazzer]

Hi,

I have tried to enter text and each letter scrolls up the screen, if I hold down escape it flashes screen and some more normal grub text is behind, but as it is flashing very fast I cannot see it !

Like you say its almost as if I am holding down enter key or something like that.

Basically I need to know where grub goes to find the data to boot with.

I think the reason I have this problem is my Kubuntu system disk was almost full and CPU at 100% and I got to terminal and did shutdown.

Not sure if any of that helps

Did lsblk - f

lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 0 100% /snap/bare/5
loop1 0 100% /snap/core18/2812
loop2 0 100% /snap/core18/2796
loop3 0 100% /snap/core20/2105
loop4 0 100% /snap/core20/2182
loop5 0 100% /snap/firefox/3836
loop6 0 100% /snap/firefox/3779
loop7 0 100% /snap/gnome-3-38-2004/140
loop8 0 100% /snap/core22/1033
loop9 0 100% /snap/core22/1122
loop10 0 100% /snap/gnome-3-38-2004/143
loop11 0 100% /snap/gnome-42-2204/141
loop12 0 100% /snap/gtk-common-themes/1535
loop13 0 100% /snap/gutenprint-printer-app/702
loop14 0 100% /snap/snapd/20290
loop15 0 100% /snap/gnome-42-2204/132
loop16 0 100% /snap/snapd/20671
sda
├─sda1 ntfs Recovery 7288E7AD88E76DD3
├─sda2 vfat FAT32 7AE8-3325 60M 37% /boot/efi
├─sda3
├─sda4 ntfs Windows 10 Home 680AEC9A0AEC6692
├─sda5 ext4 1.0 Kubuntu 21 Sys 23affd00-616e-4c62-ab3d-7c81f26d3be9
├─sda6 ext4 1.0 Kubuntu 21 Home a3235df3-bfb5-42c3-93fe-f99b0d184d4a
├─sda7 ext4 1.0 Kubuntu 22 Sys bfb60022-0d3e-42d0-87c6-9d349bbc9922 3.4G 83% /var/snap/firefox/common/host-hunspell
│ /
└─sda8 ext4 1.0 Kubuntu 22 Home 1ab7fee0-293a-4d25-bb8d-32bde9358b2d 3.3G 57% /home
sdb
├─sdb1 ext4 1.0 EXT4 d35a3853-ab3c-4e5c-b266-64d1769bf2d6 158.3G 76% /media/gb/EXT4

I did reinstall grub earlier today and still the same problem.

sda 3 in partiton manager. is this normal ?

[Schwarzer Kater]

I sometimes forget that there are people that use Snaps - for a better output you should have used lsblk -f -e7 .
But your partitions seem to be a bit all over the place anyhow…

How full are the partitions - what does df -h say?

PS: This may be far-fetched, but have you tried another keyboard?

[Gazzer]

Hi,

I have no idea how Snap is on there, but I have looked at another PC i have and that also has the same strange snap ... etc.

Filesystem Size Used Avail Use% Mounted on
tmpfs 759M 1.9M 757M 1% /run
/dev/sda7 29G 25G 3.4G 88% /
tmpfs 3.8G 50M 3.7G 2% /dev/shm
tmpfs 5.0M 8.0K 5.0M 1% /run/lock
tmpfs 3.8G 0 3.8G 0% /run/qemu
/dev/sda8 8.8G 5.0G 3.3G 61% /home
/dev/sda2 95M 36M 60M 37% /boot/efi
tmpfs 759M 100K 758M 1% /run/user/1000
/dev/sdb1 836G 635G 159G 81% /media/gb/EXT4
/dev/sdb2 82G 6.6G 76G 8% /media/gb/NTFS

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1
│ ntfs Recovery 7288E7AD88E76DD3
├─sda2
│ vfat FAT32 7AE8-3325 60M 37% /boot/efi
├─sda3
│
├─sda4
│ ntfs Windows 10 Home
│ 680AEC9A0AEC6692
├─sda5
│ ext4 1.0 Kubuntu 21 Sys
│ 23affd00-616e-4c62-ab3d-7c81f26d3be9
├─sda6
│ ext4 1.0 Kubuntu 21 Home
│ a3235df3-bfb5-42c3-93fe-f99b0d184d4a
├─sda7
│ ext4 1.0 Kubuntu 22 Sys
│ bfb60022-0d3e-42d0-87c6-9d349bbc9922 3.4G 83% /var/snap/firefox/common/host-hunspell
│ /
└─sda8
ext4 1.0 Kubuntu 22 Home
1ab7fee0-293a-4d25-bb8d-32bde9358b2d 3.3G 57% /home
sdb
├─sdb1
│ ext4 1.0 EXT4 d35a3853-ab3c-4e5c-b266-64d1769bf2d6 158.3G 76% /media/gb/EXT4
└─sdb2
ntfs NTFS 08A9E242794B8CA0 75G 8% /media/gb/NTFS
sdc
​

[Gazzer]

should the @ be there ?

sudo os-prober

/dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/sda5:Ubuntu 21.04 (21.04):Ubuntu:linux

[Gazzer]

Hi,

I have solved the problem, i have 2 keyboards attached to my PC, I use a white one most of the time and the other black keyboard, if I have dirty hands.

Guess what ... the other black keyboard was resting … very … very slightly against a cable .
There was a key being pressed on that one, not sure which key, but one on the extreme left of the keyboard.

Strange thing is that the key didn’t affect any typing I did on screen, so it was a key that had nothing to do with text on the screen !

At least Linux hadn’t let me down as I thought it was corrupted by my PC CPU going to 100% and I shutdown via terminal, then the problem occurred.

ALL coincidence !

Thanks

[Schwarzer Kater]

Sometimes it's just the odd hardware "bug".