Blackscreen after updating ubuntu 22.04 to 24.04

[UbunHelpPlease]

Hi all,

I am encountering a black screen after upgrading from ubuntu 22.04 to 24.04. My device is a HP 840 G7 laptop. I normally dual boot with windows 10 and ubuntu 22.04.

I have booted from a USB stick and run boot-repair, this is the report https://paste.ubuntu.com/p/CB9jHPmZ2G/. If I click on recomended repair it then tells me "grub-efi-amd64-signed purge cancelled".

I have also tried to go into safe mode when booting up. That puts me into initramfs with the following message:

Begin: Waiting for root file system Begin: Running/scripts/local-block ... done.



done.



Gave up waiting for root file system device. Common problems:



     - Boot args (cat /proc/cmdline)



        - Check rootdelay= (did the system wait long enough?)



     - Missing  modules (cat /proc/modules; ls /dev)

 ALERT!  UUID=28fb8e59-f65f-48ca-9240-ff1fe5f96ff3 does not exist. Dropping to a  shell!



BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3.1) built-in shell (ash)



Enter 'help' for a list of built-in commands.

(initramfs

Not really sure how to proceed. Thank you in advance for any help!

 

[Condobloke]

G'day UbunHelpPlease, Welcome to Linux.org

In installing Ubuntu 24.04, am i right to assume you wiped win 10....or does it still exist as a dual boot ?

 

[UbunHelpPlease]

G'day UbunHelpPlease, Welcome to Linux.org

In installing Ubuntu 24.04, am i right to assume you wiped win 10....or does it still exist as a dual boot ?

No I did not wipe my Windows 10. I just followed the procedure in the software updater program. I did the same when updating from 20.04 to 22.04 and it worked fine.

 

[souperdude3]

Hello there!

I was really going crazy with the same error message during boot processes. I was so pinned onto UUID not being there, and I literally reinstalled, reset UUIDs and wiped storages clean, over and over again for days. I actually got to clean the inside of my workstation. Yes, everything started with upgrade which I usually don't do.

Oh well, this exact error message has been around for awhile. Basically, the same symptom but caused by something different every time when new kernels have been released. For my setup, I could not acquire the driver which was missing during boot process. Of course, I went back to 22.04, which didn't resolve the issue right away. However, previous kernel is working fine.

If you googled and ran into forums discussing the same error messages.

This problem can be also fixed by disabling the problem causing hardware as well.

Good luck!

[ubuntu] Ubuntu 24.04 UUID =/ - Page 4

Hello everyone, I bought a new Asus Vivobook E1504GA. I downloaded the Ubuntu 24.04 distribution onto a flash drive, cleaned the disk through the installer and installed Ubuntu. When I try to start my laptop, I get into the BusyBox shell. How can I fix this? The commands don't work in the shell...

ubuntuforums.org

Hi all,

I am encountering a black screen after upgrading from ubuntu 22.04 to 24.04. My device is a HP 840 G7 laptop. I normally dual boot with windows 10 and ubuntu 22.04.

I have booted from a USB stick and run boot-repair, this is the report https://paste.ubuntu.com/p/CB9jHPmZ2G/. If I click on recomended repair it then tells me "grub-efi-amd64-signed purge cancelled".

I have also tried to go into safe mode when booting up. That puts me into initramfs with the following message:

Begin: Waiting for root file system Begin: Running/scripts/local-block ... done.



done.



Gave up waiting for root file system device. Common problems:



     - Boot args (cat /proc/cmdline)



        - Check rootdelay= (did the system wait long enough?)



     - Missing  modules (cat /proc/modules; ls /dev)

 ALERT!  UUID=28fb8e59-f65f-48ca-9240-ff1fe5f96ff3 does not exist. Dropping to a  shell!



BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3.1) built-in shell (ash)



Enter 'help' for a list of built-in commands.

(initramfs

Not really sure how to proceed. Thank you in advance for any help!

 

[Alexzee]

After logging in to my Ubuntu One acct.....and reading through the output from the boot info script it looks like the fstab file is missing on the nvme or is badly configured and didn't get written properly during the upgrade.

The fstab is used by the kernel during boot time.
If the entries in your fstab file don't refect the changes that were made in the upgrade that would explain the black screen. The fstab is used by the kernel during boot time.

nvme0n1p1    : is---ESP,    part-has-no-fstab,    no-nt,    no-winload,    no-recov-nor-hid,    no-bmgr,    notwinboot, vfat
nvme0n1p3    : isnotESP,    part-has-no-fstab,    no-nt,    haswinload,    no-recov-nor-hid,    no-bmgr,    notwinboot, ntfs
nvme0n1p4    : isnotESP,    part-has-no-fstab,    no-nt,    no-winload,    recovery-or-hidden,    no-bmgr,    notwinboot, ntfs

The partition doesn't have a fstab file.

nvme0n1p1    : not--sepboot,    no---boot,    part-has-no-fstab,    not-sep-usr,    no---usr,    part-has-no-fstab,    no--grub.d,    nvme0n1

What is the output of:

sudo fdisk -l

This is your root partition:

└─nvme0n1p5 ext4     28fb8e59-f65f-48ca-9240-ff1fe5f96ff3 dc28c7b3-f8a9-4947-9705-9349f4b05d09

Let's see what @wizardfromoz thinks about your partitions.

In the meantime look here:

UUID=xxx does not exist. Dropping to a shell

Because of a hardware failure my motherboard has just been replaced. After the replacement, my system (Ubuntu 17.10) doesn't boot: ALERT! UUID=dd84f4b3-d5bf-42e4-9b5e-ec685a461fad does not exist...

askubuntu.com