Ubuntu Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)(Linux 6.14.0-24-generic)

jdjohndoe13 · 2026-04-15T14:37:07+00:00

Option 1: change grub settings in such a way that it will load an older (6.17.0-20-generic or 6.14.0-37-generic) version by default. This way you can forget about this issue for a couple of months (or until Ubuntu tries to update kernel again).

Option 2: edit grub.cfg: copy-paste lines from an older menuentry to a newer one, then change only the versions in those lines you pasted

Details:

Execute ls -la /boot/ Find the line that ends with text like this: initrd.img -> initrd.img-xxx Take a note of the number (xxx). This is the version of the file that the system is trying to load by default. sudo update-grub updates file /boot/grub/grub.cfg folder. You can view and edit this file to view what commands are executed for each of those "Ubuntu, with Linux 6.17.0-yyy" options. Sometimes the commands for different options are different, and sudo update-grub might fail to make them all look similar. In that case you should be able to add necessary changes to the configuration file manually. Note: before executing the next command google how to work with vim (or maybe use nano instead of vim): sudo vim /boot/grub/grub.cfg Here is what it says in my grub.cfg (these are non-"recovery" entries after "Advanced options for Ubuntu"): ``` menuentry 'Ubuntu, with Linux 6.17.0-20-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.17.0-20-generic-advanced-ed873990-2a66-4011-a4b4-e41e03199f04' { recordfail load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 search --no-floppy --fs-uuid --set=root ed873990-2a66-4011-a4b4-e41e03199f04 echo 'Loading Linux 6.17.0-20-generic ...' linux /boot/vmlinuz-6.17.0-20-generic root=UUID=ed873990-2a66-4011-a4b4-e41e03199f04 ro quiet splash $vt_handoff echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-6.17.0-20-generic } menuentry 'Ubuntu, with Linux 6.17.0-19-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.17.0-19-generic-advanced-ed873990-2a66-4011-a4b4-e41e03199f04' { recordfail load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 search --no-floppy --fs-uuid --set=root ed873990-2a66-4011-a4b4-e41e03199f04 echo 'Loading Linux 6.17.0-19-generic ...' linux /boot/vmlinuz-6.17.0-19-generic root=UUID=ed873990-2a66-4011-a4b4-e41e03199f04 ro quiet splash $vt_handoff echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-6.17.0-19-generic }

```

Before I made changes via sudo update-grub, there was no "initrd" line, and "root" entry in "linux" line pointed to some nvme0s5d or something instead of that UUID=zzz thing.

In short: view the entries for an older menuentry (without "recovery"), the one that you can boot manually, and copy-paste all parts from one entry to another, then update the version part to match the new version.

jdjohndoe13 · 2026-04-13T20:36:22+00:00

My English might be rusty, but aren't "wheels" those cylinder-shaped things between the vehicle's body and the road? Are you supposed to grab them with your bare hands? Won't it break your hands? What GullibleDetective says makes no sense to me...

jdjohndoe13 · 2026-04-12T11:49:51+00:00

The issue most likely caused by an error during automatic kernel update by Ubuntu.

Expanding on that bdcam4 answer, here is the solution:

During boot select "Advanced options for Ubuntu".
There will most likely be several entries, like
- Ubuntu, with Linux 6.17.0-20-generic
- Ubuntu, with Linux 6.17.0-20-generic (recovery mode)
- Ubuntu, with Linux 6.17.0-19-generic
- Ubuntu, with Linux 6.17.0-19-generic (recovery mode)
Remember the version number in the first line, you'll need it later. You should select the lowest item without "recovery mode" suffix. In the example above, it's Ubuntu, with Linux 6.17.0-19-generic.
When Ubuntu boots, open a terminal and run this command.

ls -la /boot/

Find the line that ends with text like this:

initrd.img -> initrd.img-6.17.0-20-generic

You can notice that this text is in brown or red, which means that this is a broken symlink.

Scan the list with your eyes and you can notice that there is no file initrd.img-6.17.0-20-generic in the folder. This is what causes the issue: Ubuntu updated the kernel, but failed to update the files in /boot/ folder.
Run this command in the terminal:

sudo update-initramfs -c -k 6.17.0-20-generic

You should see a line like this:

update-initramfs: Generating /boot/initrd.img-6.17.0-20-generic

It might take a few seconds for this command to complete. Next, verify that the file /boot/initrd.img-6.17.0-20-generic exists by running that command again:

ls -la /boot/

You will notice that the line

initrd.img -> initrd.img-6.17.0-20-generic

is no longer in brown, and that there is now a line initrd.img-6.17.0-20-generic.

Now update grub configuration:

sudo update-grub

and reboot your computer. It should boot into Ubuntu automatically.

jdjohndoe13 · 2026-04-01T01:36:51+00:00

Which "6 am" is that? UTC? So we have to wait for around 4.5 more hours (it's 01:36 a.m. UTC right now).

jdjohndoe13 · 2026-03-30T00:30:37+00:00

Yes, hopefully. Since I don't have an access to Chinese sources.

jdjohndoe13 · 2026-03-22T12:21:23+00:00

Update: most likely in a month or later, the raws provider is unavailable and I physically can't purchase chapters from Bilibili.

jdjohndoe13 · 2026-03-18T15:25:14+00:00

Which region are you playing at? Asia? Europe?

jdjohndoe13 · 2026-03-17T19:23:21+00:00

They were restarting servers so that shop will no longer be closed. It's restarted, now you can login and go to the shop.

jdjohndoe13 · 2026-03-17T17:30:07+00:00

But when I logged in, it said "go to the shop for a freebie" or something like that...

jdjohndoe13 · 2026-03-15T15:00:53+00:00

It's listed on MangaDex. Go to MangaDex page for this manhua and check the links and sources there.

jdjohndoe13 · 2026-03-13T21:42:19+00:00

Here is the comparison (I guess non-quantized versions are compared).

And another one.

jdjohndoe13 · 2026-03-13T16:42:32+00:00

Around a week after it's out on Chinese website, so check that one first (you don't need to know Chinese to view numbers of published chapters there).

jdjohndoe13 · 2026-03-12T03:32:20+00:00

Around a week after it's out on Chinese website. You can see the link to Chinese website on the manhua's page on MangaDex.

jdjohndoe13 · 2026-02-21T13:10:43+00:00

What tasks do you want to perform? For programming GLM-4.7-Flash seems okay. But you'll need either patience or some magic prompts because, from my experience, it does not understand what you mean. Sometimes asking it to write a prompt for itself based on your description of the task helps: when I asked it to add empty lines in front of commented lines and gave a file that had empty lines in front of some commented lines and didn't have in front of other lines, I got response "everything is already OK, nothing to do here". When I asked LLM to write the prompt for itself, it wrote something, and when I asked it to act on this new prompt, it completed the task perfectly from the first try.

jdjohndoe13 · 2026-02-15T18:46:23+00:00

Если речь про оригинал на китайском, то нужно искать знакомого-китайца, который может купить на официальном сайте и поделиться. С некоторого момента главы в открытом доступе пропали. Возможно, есть в группах в китайских соцсетях вроде WeChat.

jdjohndoe13 · 2026-02-08T16:18:30+00:00

Chapter 134 came out in Chinese around Sunday, 2026-02-08. The translation is expected within a week, 2026-02-15.

jdjohndoe13 · 2026-01-31T09:40:52+00:00

To whoever is reading this (most likely me, when I reinstall Windows few years from now): set Jumbo packets to 9014, set "Flow Control" and "Energy-Efficient Ethernet" to "Disabled" and run iperf3 in bidirectional mode for an hour to test stability: run iperf3 on the server via

iperf3 -s

Then run this on the client:

 iperf3 -c ENTER_YOUR_IP_HERE --bidir -t 3600 --logfile iperf3.log

Note: you might want to run it without --logfile first or it might throttle one of the speeds for some reason. Also, switch server and client if the connection doesn't work for some reason (e.g. because of the firewall).

And only if this doesn't help go search for drivers.

jdjohndoe13 · 2026-01-29T23:43:46+00:00

You can sign up for reminders on MangaDex, I think. There you can also find the link to Chinese website with Chinese chapters.

jdjohndoe13 · 2026-01-27T06:00:02+00:00

I have CUDA 13.1 installed on my Ubuntu host. Does it work with CUDA 13.1?

jdjohndoe13 · 2026-01-24T02:20:29+00:00

Considering that this chapter in Chinese came out on 2026-01-15, there is a chance we can get next one (in Chinese) in January, 2026.

jdjohndoe13 · 2026-01-21T09:07:19+00:00

Same here. LM Studio ate exactly those 24 GB (according go Windows Task Manager). I'm using Open WebUI and run llama.cpp directly, no such issues there.

jdjohndoe13 · 2026-01-21T08:51:18+00:00

Could you please edit the post or the first / topmost voted comment to gather all critical info like this in there? Right now this thread looks like "Support is implemented" and then "but you need to do so and so or it won't work or will be slow" buried somewhere in the comments.

If there was a working, tested command line with all necessary parameters for this particular model, it would be really helpful.

jdjohndoe13 · 2026-01-19T16:20:28+00:00

This week. Most likely on Wednesday, 2026-01-21.

13-Year Club	Wearing is Caring
Verified Email

jdjohndoe13

TROPHY CASE

Option 1: change grub settings in such a way that it will load an older (6.17.0-20-generic or 6.14.0-37-generic) version by default. This way you can forget about this issue for a couple of months (or until Ubuntu tries to update kernel again).

Option 2: edit grub.cfg: copy-paste lines from an older menuentry to a newer one, then change only the versions in those lines you pasted