(ZFS) After Update: Unable to mount root fs on unknown block

[Rick St. George]

UbuntuStudio v20.04 ... latest upgrade, and on Reboot got the message.

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Not tainted 5.15.0-94-lowlatency

Tried - boot with Live CD and ran ;

sudo dpkg --configure -a

Then it did Boot. Ran Update and Upgrade, and Reboot. Same Error!
Any suggestions? Running with SSD and 32 GB Ram and 8 core CPU.

Thanks!

[1fallen]

Please see this the post by Tomeu Roig: https://askubuntu.com/questions/4193...known-block0-0

Follow all the steps shown

[Rick St. George]

That's where I got my info. Moreover, there are 12 answers. I chose to boot to LiveCD and (see my first post). Also, as posted on that page;

It's now 11 years later, and 22.04 fails to automatically fix this problem and/or give decent clues of what steps to take !! –
Rick James May 16, 2022

In addition, Boot Repair may not fix the problem if the problem lies in the Fix being to upgrade to Grub to 2.12!

So, I guess the real question is ... How do Upgrade Grub if I can't boot the computer???

[guiverc]

Ubuntu Studio 20.04 LTS is end of life - https://ubuntustudio.org/2023/04/ubu...d-end-of-life/

Have you performed file-system checks from the live media, and don't forget commands executed (eg. `sudo dpkg --configure -a`) in a live environment will impact the live environment itself, and not your installed system (unless you've chroot'd across to the installed system).

I would still explore your system from the live disk, starting with file-system checks, then quick exploration of file-system table (/etc/fstab on the installed system & NOT the live system you're running, thus don't forget locations will differ) etc. If a file-system check detected & fixed any issue; I'd expect normal boot on next try. Also note the command to perform file-system check varies on file-system involved (ie. `fsck` will just exit for many as per documentation when you attempt to run it on a file-system its not intended to handle; use the appropriate command for your unstated file-system(s))

[Rick St. George]

Did the Intel Microcode corrupt Grub? because I'm running on a AMD FX-8320 Vishera, and have Grub 2.04.

According to Symantec .... No Broken Files. And End of Life ... but, 22.04 still has problems - been watching posts.

[Rick St. George]

Ran the following;

$ sudo fdisk -l
Disk /dev/sda: 232.91 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 840 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf8d469ad

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sda1  *       2048   1050623   1048576   512M  b W95 FAT32
/dev/sda2       1052670 488396799 487344130 232.4G  5 Extended
/dev/sda5       1052672 488396799 487344128 232.4G 83 Linux


$ sudo dpkg --configure -a

$ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.0-94-lowlatency
Found initrd image: /boot/initrd.img-5.15.0-94-lowlatency
Found linux image: /boot/vmlinuz-5.15.0-94-lowlatency
Found initrd image: /boot/initrd.img-5.15.0-94-lowlatency
Found linux image: /boot/vmlinuz-5.15.0-92-lowlatency
Found initrd image: /boot/initrd.img-5.15.0-92-lowlatency
Found linux image: /boot/vmlinuz-5.15.0-88-lowlatency
Found initrd image: /boot/initrd.img-5.15.0-88-lowlatency
Found linux image: /boot/vmlinuz-5.11.0-27-lowlatency
Found initrd image: /boot/initrd.img-5.11.0-27-lowlatency
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done

Contents of init-select.cfg

# Work around a bug in the obsolete init-select package which broke
# grub-mkconfig when init-select was removed but not purged.  This file does
# nothing and will be removed in a later release.
#
# See:
#   https://bugs.debian.org/858528
#   https://bugs.debian.org/863801

Contents of 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=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
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,0xefefefef"

# 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"

Any suggestions, because what is in Grub isn't working?!?!?

[1fallen]

Did the Intel Microcode corrupt Grub? because I'm running on a AMD FX-8320 Vishera, and have Grub 2.04.

According to Symantec .... No Broken Files. And End of Life ... but, 22.04 still has problems - been watching posts.

Not here, I thought we have already covered this in previous post.

 apt policy intel-microcode
intel-microcode:
  Installed: 3.20231114.1
  Candidate: 3.20231114.1
  Version table:
 *** 3.20231114.1 500
        500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
        100 /var/lib/dpkg/status
┌───────────────────>
│~ 
└─> apt policy amd64-microcode
amd64-microcode:
  Installed: 3.20231019.1ubuntu1
  Candidate: 3.20231019.1ubuntu1
  Version table:
 *** 3.20231019.1ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
        100 /var/lib/dpkg/status

but, 22.04 still has problems - been watching posts.

What kind of problems are you referring to, If you list those, or better yet search what you think impacts you...then maybe we can debunk or find a work-around.

Right now your at a semi-vulnerable state. Unless you have ESM in place.

ubuntu-security-status

[Rick St. George]

What is ESM? Are you referring to Enterprise Service Management? No I do not. I'm a lone survivor.

And after Booting Computer this morning ... same problem.
Did my SSD drive go bad???

[Rick St. George]

Got computer up by going back down Grub 3rd previous version (recovery mode).

lsblk shows sda1 (mount pt) as mounted /mnt/A00D-96E4
blkid shows sda5 UUID (and ID No.)

SDA5 is extended partition on SSD drive. Not sure what to do next?

[1fallen]

What is ESM? Are you referring to Enterprise Service Management? No I do not. I'm a lone survivor.

Expanded Security Maintenance (ESM)
Extra security patching for Ubuntu LTS
https://ubuntu.com/security/esm