for f in $(find . -maxdepth 1 -type f -name 'dmesg*.log'); do echo "${f}"; printf '%s\n\n' "$(<"${f}")"; done
bash: ./dmesg_20240811102955.log: Permission denied
sudo for f in $(find . -maxdepth 1 -type f -name 'dmesg*.log'); do echo "${f}"; printf '%s\n\n' "$(<"${f}")"; done
sudo: ./dmesg_20240811102955.log: command not found
Additional Information (if applicable)
Software title | (E.g. Nextcloud)
Software version | (E.g. softwarename -V)
Was the software title installed freshly or updated/migrated?
Steps to reproduce
Attempted to upgrade to Mint 22 with the ‘mintupgrade’ command
Now when selecting Linux Mint 22 from GRUB menu, booting stops with a black screen.
In GRUB advanced options, selecting recovery boot, a Kernel panic is reported after:
/dev/root: Can’t open blockdev
VFS: Cannot open root device “/dev/nvmc0n1p1” or unknown-block(0,0): error 6
Please append a correct “root=” boot option; here are the available partitions:
ext3
ext2
ext4
squashfs
vfat
fuseblk
Kernel panic - not syncing; VFS: Unable to mount root fs on unknnown-block(0,0)
Expected behaviour
It should be booting to the new Linux Mint 22 and kernel 6.8.0-40-generic
Actual behaviour
Booting stops at a black screen. But I can use the GRUB advance options and boot the the previous Linux Mint 21.3 and kernel 6.8.0-39-generic
Extra details
I have 2 drives, 1 drive has Linux, 1 drive has Windows
gtrevels:~$ hostnamectl
Static hostname: ASUS-TUF-A15-FA506IV
Icon name: computer-laptop
Chassis: laptop
Machine ID: *********************
Boot ID: **********************
Operating System: Linux Mint 21.3
Kernel: Linux 6.8.0-39-generic
Architecture: x86-64
Hardware Vendor: ASUSTeK COMPUTER INC.
Hardware Model: ASUS TUF Gaming A15 FA506IV_TUF506IV
Firmware Version: FA506IV.316
Firmware Date: Fri 2021-03-12
Firmware Age: 3y 5month
gtrevels:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Linuxmint
Description: Linux Mint 21.3
Release: 21.3
Codename: virginia
gtrevels:~$ cat /etc/linuxmint/info
RELEASE=22
CODENAME=wilma
EDITION=“Cinnamon”
DESCRIPTION=“Linux Mint 22 Wilma”
DESKTOP=Gnome
TOOLKIT=GTK
GRUB_TITLE=Linux Mint 22 Cinnamon
gtrevels:~$ cat /etc/os-release
NAME=“Linux Mint”
VERSION=“21.3 (Virginia)”
ID=linuxmint
ID_LIKE=“ubuntu debian”
PRETTY_NAME=“Linux Mint 21.3”
VERSION_ID=“21.3”
<–snip out urls–>
VERSION_CODENAME=virginia
UBUNTU_CODENAME=jammy
Try creating a new boot usb key and test to see if it will boot direct to that, if that functions correctly then re install from that key
I had a similar expérience earlier this year with lmde (linux mint debian edition) upgrade, ran that for several hours only for it to fail towards the end so clean new install was the only answer.
Thanks for your reply. Fortunately I can still boot to the previous version and modify files. I am interested in learning to fix the GRUB, fstab, or whatever needs to be modified to allow a proper boot up.
When comparing the GRUB entries between ‘Linux Mint 22 Cinnamon, with Linux 6.8.0-39-generic’ (this one boots fine) and ‘Linux Mint 22 Cinnamon, with Linux 6.8.0-40-generic’ (fails), ‘Linux Mint 22 Cinnamon, with Linux 6.8.0-39-generic’ has this entry
search --no-floppy --fs-uuid --set=root b0b682fa-d6ee-4da3-8c60-ae2a9ab88695
echo ‘Loading Linux 6.8.0-39-generic …’
linux /boot/vmlinuz-6.8.0-39-generic root=UUID=b0b682fa-d6ee-4da3-8c60-ae2a9ab88695 ro quiet iommu=off
echo ‘Loading initial ramdisk …’
initrd /boot/initrd.img-6.8.0-39-generic
But the entry for ‘Linux Mint 22 Cinnamon, with Linux 6.8.0-40-generic’ has this entry
search --no-floppy --fs-uuid --set=root b0b682fa-d6ee-4da3-8c60-ae2a9ab88695
echo ‘Loading Linux 6.8.0-40-generic …’
linux /boot/vmlinuz-6.8.0-40-generic root=/dev/nvme1n1p1 ro quiet iommu=off
Is this a problem I can solve by changing root=/dev/nvme1n1p1 to root=UUID=b0b682fa-d6ee-4da3-8c60-ae2a9ab88695 ?
If so, how would I change it?
Also is there something in the fstab that needs to be changed?
gtrevels:~$ 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).
Your copy of fstab has been altered by discourse… I am not sure if some of those lines are comments.
Could you do it again like this
Put three backquote characters on a line (```)
Go to the next line and copy in your cat fstab
Put another three backquote characters on a separate line at the end
That will ensure it copies the material literally
The three backquotes are a markdown instruction which protects the copied material from being interpreted as instructions.
$ 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/nvme0n1p1 during installation
UUID=b0b682fa-d6ee-4da3-8c60-ae2a9ab88695 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme1n1p1 during installation
UUID=3493-AF4F /boot/efi vfat umask=0077 0 1
# /home was on /dev/nvme0n1p2 during installation
UUID=a7f2d42b-2cc2-43ea-9891-260919ce4377 /home ext4 defaults 0 2
/swapfile none swap sw 0 0
Right.
It seems to have the correct UUID bo…95 for /
Never seen that /swapfile none line before. It is probably OK
I think fstab is not the problem
That seems likely
You can change it temporarily as follows
boot to the grub menu
navigate to the correct line
hit ‘e’
you will get an editor
go down to the line that starts with linux and edit the root= bit . Carefully type in the uuid.
hit F10 and it will boot
Now , if that works, you want to change it permanently
Edit the file /etc/default/grub
Find the line
GRUB_CMDLINE_LINUX_DEFAULT=
and add UUID=bo…95 there
When you finish editing do update-grub
that will remake the /boot/grub/grub.cfg file
It says
VFS: Cannot open root device UUID=bo…
It has booted the initramfs and is trying to find the root filesystem so it can boot linux
Assuming you typed the UUiD without errror that means
you may have the wrong partition… check that really is the root filesystem
the partition may be unreadable … is it ext4? Can you boot some linux from a USB drive and mount that partition and look at it.?
there may be a problem accessing the disk during boot. I think I saw somewhere it was an nvme disk… they are rather new… there may be a problem with the driver not being there at boot time when needed … not sure how to deal with that… maybe update the initramfs, but that seems a bit drastic for a new install?
PS
I just noticed it is a Mintupgrade… not a fresh install.
Well maybe the upgrade procedure is faulty. You might indeed need to update the initramfs… you need to boot into it to do that… can you boot it in single user (recovery) mode?
If it is all too messy, save your home directory and do a fresh install
Attached GRUB Adv Boot options picture to show the boot choices. I have performed a few upgrades on this laptop without any issues. This Mint 22 upgrade with the new 6.8.0-40 kernel is the only one that has given me problems. I cannot boot either 6.8.0-40 kernel option. The previous post includes a picture of where the 6.8.0-40 Recovery boot fails. But I can boot the 6.8.0-39 kernel option.
Thanks for the help.
It may be time for a fresh install.
You dont need a fresh install.
Just use the 6.8.0-39 kernel. You can set grub to push 6.8.0-39 to the top of the boot menu.
Does Mint have a facility to delete kernels? If so get rid of it… it seems to have a kernel regression error.
A new kernel should soon appear with updates.
I used Update Manager to remove the 6.8.0-40 kernel and rebooted. Now it boots without hanging.
I took another look at Update Manager and 6.8.0-40 is still listed but 6.8.0-39 shows as Active.
This is good for now. I’ll research the upgrade more thoroughly and wait a few weeks before trying to perform another mintupgrade
I also remove the older 6.5xxx kernels with Update Manager.
Thanks, I really appreciate the help from the community.
Yours looks normal.
You actually have a swap partition.
I think @GTR 's means he has a device called /swapfile in /dev, but I am not sure if that is mounted to a file, or is a partition?
