Announcement

**barkingbandicoot** · Nov 21, 2023, 05:04 AM

**shouldknowbetter** · Nov 21, 2023, 05:27 AM

Well I created an account because I have problems booting anything beyond 6.2.0-36 myself. From the pic you posted in the interim I am not sure it is the same root cause, I don't have access to my machine right at the moment, but I do remember I don't see anything after loading initial ramdisk with later kernels. It will boot if I enter recovery and simply select continue. It will also boot if I add the dis_ucode_ldr parameter to grub to inhibit loading of the intel microcode but I would not want to run like this. I have also tried 6.6 and 6.7RC kernels from Ubuntu mainline to no avail. There is also an issue with nvidia-drivers (any available version.) If I change nvidia drivers using the recommended gui driver installer, nothing will boot all the way into a working desktop. I have to use apt to purge all things nvidia and re-install nvidia drivers using apt.

I even thought I would try a fresh install instead of an upgrade, but I cant boot the installation usb at all. It works just fine in another machine.

**shouldknowbetter** · Nov 21, 2023, 06:57 AM

Well as I wrote my last post I remembered there was an UEFI option on my system related to microcode update. It was already set to "Auto" and after changing it to other available options (2D and C2) it still would not boot, but when I put it back to "Auto" kernel 6.5 boots up just fine now. Must be a bug in my firmware. At least it's working for now. Unfortunately this system is getting a bit old and the last update from the motherboard manufacturer was 5 years ago.

**Schwarzer Kater** · Nov 21, 2023, 07:50 AM

barkingbandicoot:
Near the bottom of your screenshot there is a line "ALERT! UUID=6e519b5b-[…] does not exist. Dropping to a shell!"

What is on the partition with this UUID / what is it used for?

The output of cat /etc/fstab and cat /etc/default/grub from the affected system could also be helpful (please use CODE tags if you post this).

**claydoh** · Nov 21, 2023, 08:46 AM

And to add to the above, some more information about your file system setup could be useful here- mdadm is for RAID, so you may need to look at hardware/drive issues.
Running a live session will be helpful to investigate, as well as being able to (hopefully) access your files and logs.

**barkingbandicoot** · Nov 21, 2023, 07:49 PM

Originally posted by Schwarzer Kater View Post

barkingbandicoot:
Near the bottom of your screenshot there is a line "ALERT! UUID=6e519b5b-[…] does not exist. Dropping to a shell!"

What is on the partition with this UUID / what is it used for?

The output of cat /etc/fstab and cat /etc/default/grub from the affected system could also be helpful (please use CODE tags if you post this).

cat /etc/fstab
# /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>
# / was on /dev/nvme0n1p2 during installation
UUID=6e519b5b-716d-49f0-bc4c-eabfd5e7fd39 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=B796-B113 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
#UUID=b8f17b3d-52ec-4b44-881f-19038165cc3d /media/backup ext4 defaults 0 0

cat /etc/default/grub
# 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="Advanced options for Ubuntu>Ubuntu, with Linux 6.2.0-36-generic"
GRUB_TIMEOUT_STYLE="hidden"
GRUB_TIMEOUT="0"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xe fefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE="640x480"

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

GRUB_SAVEDEFAULT="false"

**barkingbandicoot** · Nov 21, 2023, 08:06 PM

Originally posted by shouldknowbetter View Post

Well as I wrote my last post I remembered there was an UEFI option on my system related to microcode update. It was already set to "Auto" and after changing it to other available options (2D and C2) it still would not boot, but when I put it back to "Auto" kernel 6.5 boots up just fine now. Must be a bug in my firmware. At least it's working for now. Unfortunately this system is getting a bit old and the last update from the motherboard manufacturer was 5 years ago.

Interesting. I also cannot update the Nvidia drivers.
I also had a firmware update. I cannot find those settings you mentioned in my Dell UEFI boot though.

**jglen490** · Nov 22, 2023, 06:38 AM

So the UUID for your / partition on /dev/nvme0n1p2 has changed. Somehow.

The next time you boot the machine and are dropped to the shell, run blkid and note the UUID for /dev/nvme0n1p2. Then use nano or use favorite editor to apply the correct UUID to /etc/fstab.

**barkingbandicoot** · Nov 22, 2023, 04:35 PM

Originally posted by jglen490 View Post

So the UUID for your / partition on /dev/nvme0n1p2 has changed. Somehow.

The next time you boot the machine and are dropped to the shell, run blkid and note the UUID for /dev/nvme0n1p2. Then use nano or use favorite editor to apply the correct UUID to /etc/fstab.

Thanks for the advice. I will give this a go. I will do a redo rescue clone this weekend first. Interesting that the UUID would change with the kernel and but stay the same with the current one.

**barkingbandicoot** · Nov 22, 2023, 05:54 PM

I just quickly had a go with blkid but it would not print anything. I suppose I will have to try it on a live disk.
I also tried sudo initramfs-update 5.0.13-generic and it made no difference either.

While logged into kernel 6.2 blkid works:

$blkid
/dev/nvme0n1p1: UUID="B796-B113" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI Syste
m Partition" PARTUUID="af229ecb-47ce-4cd6-bb13-a5b716b6545c"
/dev/nvme0n1p2: UUID="6e519b5b-716d-49f0-bc4c-eabfd5e7fd39" BLOCK_SIZE="4096" TYPE
="ext4" PARTUUID="ffe9d3ad-ca7e-4a8b-8c28-fcdf1bfe57e8"

Is there a way to make 6.5 see it while logged in on 6.2?

**Schwarzer Kater** · Nov 22, 2023, 07:56 PM

Try purging the 6.5.x kernels and reinstall the latest one (including the headers to be able to install your GPU drivers) - it sounds like something got corrupted during the creation of the boot-loader when you installed the 6.5.x kernels…
If this doesn't help, it won't make anything worse neither normally.

If I were mean I would blame Nvidia - but perhaps they are innocent this time…

**jglen490** · Nov 23, 2023, 01:22 PM

The bklid UUID result form kernel 6.2 matches the UUID entry in your /etc/fstab, so booting under the 6.2 kernel should work. The fact that 6.5 returns nothing is indicative of a failed kernel update. Removing the 6.5 kernel files, as Schwarzer Kater is an excellent start. It would not hurt to check your 6.2 after a reboot and make sure it's still good. Then proceed on to whatever you need to do.

Best of luck to you!

**barkingbandicoot** · Nov 23, 2023, 07:57 PM

I had a lot of kernels to purge but am having trouble with 6.5.0-13.
I purge it but it still shows up in the terminal.
I then tried purging from Muon and it said there was a dependency problem - but appeared to remove in Muon!
It is also removed in Grub Customizer, but still shows up in the terminal!

sudo apt purge linux-image-unsigned-6.5.0-13-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'linux-image-unsigned-6.5.0-13-generic' is not installed, so not removed
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
anarcho@LuNoHo:~$sudo dpkg --list | egrep 'linux-image|linux-headers'
ii linux-headers-6.2.0-36 6.2.0-36.37 a
ll Header files related to Linux kernel version 6.2.0
ii linux-headers-6.2.0-36-generic 6.2.0-36.37 a
md64 Linux kernel headers for version 6.2.0 on 64 bit x86 SMP
ic linux-image-6.2.0-1003-lowlatency 6.2.0-1003.3 a
md64 Signed kernel image lowlatency
ic linux-image-6.2.0-1003-oracle 6.2.0-1003.3 a
md64 Signed kernel image oracle
ic linux-image-6.2.0-20-generic 6.2.0-20.20 a
md64 Signed kernel image generic
ic linux-image-6.2.0-23-generic 6.2.0-23.23 a
md64 Signed kernel image generic
ic linux-image-6.2.0-24-generic 6.2.0-24.24 a
md64 Signed kernel image generic
ic linux-image-6.2.0-25-generic 6.2.0-25.25 a
md64 Signed kernel image generic
ic linux-image-6.2.0-26-generic 6.2.0-26.26 a
md64 Signed kernel image generic
ic linux-image-6.2.0-27-generic 6.2.0-27.28 a
md64 Signed kernel image generic
ic linux-image-6.2.0-31-generic 6.2.0-31.31 a
md64 Signed kernel image generic
ic linux-image-6.2.0-32-generic 6.2.0-32.32 a
md64 Signed kernel image generic
ic linux-image-6.2.0-33-generic 6.2.0-33.33+1 a
md64 Signed kernel image generic
ic linux-image-6.2.0-34-generic 6.2.0-34.34 a
md64 Signed kernel image generic
ic linux-image-6.2.0-35-generic 6.2.0-35.35 a
md64 Signed kernel image generic
ii linux-image-6.2.0-36-generic 6.2.0-36.37 a
md64 Signed kernel image generic
ic linux-image-6.5.0-13-generic 6.5.0-13.13 a

UPDATE: Going back into Muon I clicked into 6.5.0-13 and saw both install AND purge! So, I tried purge again and it also removed an Nvidia component. 6.5 no longer shows up in the terminal!

After reinstalling 6.5.0-13 I still have the same issue.

At this point what should I do?
1. Wait for a new kernel release and see if will work?
2. Re-install - but with KDE Neon this time. I have just rolled an iso for btrfs as default filesytem with btrfs-grub and snapper. Can I simply install my backed up home directory to Neon or is that problematic?

Announcement

Boot fail - kernel 6.5.0-13

Boot fail - kernel 6.5.0-13

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment