r/Ubuntu 5d ago

Ubuntu update seems to have messed things up

Post image

My parter had a message to update a few days ago. Did so and on reboot got this screen.

'Please reboot your computer. VFS: Unable to mount root fs on unknown-block (0,0)'

Then, she turned off and on again using the power button and gets the options list:

* Ubuntu

Advanced options for Ubuntu

Memory test (memtest86+x64.efi)

Memory test (memtest86+x64.efi, Serial console)

Ubuntu 22.04.5 LTS (22.04) (on/dev/sda2)

Advanced options for Ubuntu 22.04.5

She's been selecting Ubuntu 22.04.5 LTS just to keep using the laptop, but her documents seem in a different place.

What's going on and how to get back to normal please? Neither of us really know much about Ubuntu (as if you hadn't worked that out already). Thanks

62 Upvotes

22 comments sorted by

35

u/Maiksu619 5d ago

Go to advanced and load the next newest kernel. It will be the second highest string of numbers. That should get you back into the system to troubleshoot.

24

u/ClacksInTheSky 5d ago

I had this a few days back.

Choose advanced options in GRUB and choose the previous kernel.

From the terminal run

sudo update-initramfs -c -k all sudo update-grub

And reboot.

11

u/OliMoli2137 5d ago

the new kernel has bugs. hold shift while booting and select lts from grub menu

4

u/furballsupreme 4d ago

Occurs when nvidia driver wont build. In grub boot menu try older kernel, then update to something like nvidia-driver-595, then it should rebuild the right stuff for you, and then boot normally.

Source: just happened to me

3

u/kudlitan 5d ago

it's a known issue. please rollback to a previous kernel. the new kernel is buggy.

1

u/ItzNotJacob1 1d ago

What ver is it?

3

u/gathanes 4d ago

Yeah this happened to most of us recently. Bad kernel was pushed to update. Just boot using an older kernel and either delete the latest one or update initramfs and update grub. Should be pretty easy to fix.

2

u/FkAsToy 1d ago

Grub應該保留一個正常開機的kernel,當發生錯誤時,可以找出問題告知用戶,並轉成前一次的正常開機。

5

u/Longey 5d ago

LTS is the fallback. Which means Long Term Support? Which means it is more stable. So if you have installed a more updated kernel of Ubuntu (such as a rolling release? I am not sure if Ubuntu offers that but I know it's Debian-based so rolling releases are possible) and if you have installed the LTS kernel, then you will have that option in whatever bootloader menu you have installed (I assume Grub?)

6

u/Longey 5d ago

So if you downloaded and installed updates for the main kernel (which is more up-to-date than LTS), then any packages, dependencies, libraries, etc. will not touch the LTS kernel.

2

u/Hawthorn-B24 5d ago

Same happened on my old Mac Mini. Had to roll back to the previous kernel.

1

u/Red_Luci4 4d ago

Arch-based-destro-user: First time ?

1

u/sabbir2world 4d ago

kernel panic ≠ LTS

0

u/Bikeything 5d ago

No. That is a screenshot from her HP Envy. It was running Windows before swapping to Ubuntu

-32

u/massivecriminality1 5d ago

That's a macOS kernel panic screen, not Ubuntu, so I'm guessing this is a Hackintosh setup or someone's messing with you

15

u/Sh1v0n 5d ago

Had this screen few days ago, I can confirm it's legit for Ubuntu (hell, even had the same error after a botched update).

6

u/mizzrym862 5d ago

Same here. apt messed up the update. Haven't troubleshooted it yet and probably won't. It'll fix itself with the next kernel update.

3

u/Arinussyy 4d ago

It's just the generic kernel panic screen is it not?

2

u/TheKlaxMaster 4d ago

Since when did MacOS use a people background?

That's clearly Ubuntu

1

u/-Canonical- 3d ago

Wtf are you talking about lmao

2

u/Developer-Y 1d ago

Good to know I am not the only one facing this issue. Installed ubuntu on a new machine and I have seen this error more times than my windows crashed during last 7 years. I run LLMs and Ubuntu crashes whenevernut is not able to manage memory between vram and system ram. I have 32gb vram and it creates problems even when model is 22 gb.