I want to fix booting my system after upgrade to Ubuntu 24.04.1. It uses UEFI Only mode (CSM Support: No).
Ubuntu Version:
Ubuntu version 22.04 LTS
Desktop Environment (if applicable):
GNOME
Problem Description:
I’ve just upgraded to new Ubuntu version 24.04. Upgrade completed successfully. System does not load. After I select Ubuntu in grub menu I get into BusyBox v1.30.1.with ALERT! UUID=xxxx does not exists.
Relevant System Information:
One ssd disk, details in Ubuntu Pastebin
ThinkPad T460
Screenshots or Error Messages:
Gave up waiting for root file system device. Common Problems:
- Boot args (cat /proc-cmdline)
- Check rootdelay= (did the sytem wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
- ALERT! UUID=c0ac1b15-d468-4fb2-b3b2-3b9d34a6f2dc does not exist. Drop to a shell!
BussyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3.1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
What I’ve Tried:
I tried Boot-Repair.
Added Ubuntu entry with a command efibootmgr -c -d /dev/sda -p 1 -L Ubuntu -l '\EFI\ubuntu\grubx64.efi' because it was absent in the list.
Change boot order with ‘efibootmgr -o 0001,0000,…’
Fix persistence by disabling Boot Order Lock in BIOS.
Change Boot Mode “Quick” to “Diagnostics”
Remove “Windows boot manager” via bios.
Try to use another efi file with a command efibootmgr -c -d /dev/sda -p 1 -L Ubuntu -l '\EFI\ubuntu\shimx64.efi' (delete previous and changed order if required)
You say you upgraded from 22.04 to 24.04 but you did not tell us how you did that.
Did you use the command line upgrade system (which I have never used) or did you do a new installation from a downloaded .iso archive file; if the latter did you make sure that you used the manual partitioning utility, ie “Something Else” in the installer and pointed it to the old root partition for the new one?
One thing that stood out for me from the boot script summary was this:
line 88: Locked-NVram detected. Please do not forget to make your UEFI firmware boot on the Ubuntu 24.04.1 LTS entry (sda1/efi/ubuntu/grubx64.efi file)
On the Ubuntu Forums there were a number of threads where this was an issue but no single solution.
I did upgrade by pressing Upgrade button in the notification dialog. I did not use the command line upgrade commands and I did not download any iso files. I did not do any partition changes. When upgrade was completed I pressed Reboot now or something like that. One strange thing for me was during upgrade it was a new dialog with a question if I want to upgrade to 24.04.01, I did not touch it and wait until current upgrade process is completed.
In 2021 I’ve installed Ubuntu 22.04 (maybe it was 20.04 and I already did upgrade) by erasing all disk. Only one system was on laptop.
Gave up waiting for root file system device. Common Problems:
- Boot args (cat /proc-cmdline)
- Check rootdelay= (did the sytem wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
- ALERT! UUID=c0ac1b15-d468-4fb2-b3b2-3b9d34a6f2dc does not exist. Drop to a shell!
BussyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3.1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
I use ctrl+alt+del to reboot. To turn off my computer I can use only a long press power button or I guess I can use GUI turn off button if I load system from USB drive.
Power off via the power button may damage the file systems because they are still mounted.
Can you boot into a “Try Ubuntu” live session (preferably using a 24.04.1 iso) and run fsck on both your partitions. sudo fsck /dev/sda1 sudo fsck /dev/sda2
So are you telling us that you normally shutdown the computer using a long press of the power button?
If so I am not surprised that you have problems such as this busybox error.
Always shut down using either the GUI shutdown buttons/dialog in the panel or if really needed with command sudo shutdown -h now
No, I do not turn off my computer by power button (only in rare case when it does not respond). I BusyBox I does not have another option to turn off laptop as to use power button.
check file system on /dev/sda1 for errors and (if possible) fix them 00:00:00 ( SUCCESS )
fsck.fat -a -w -v '/dev/sda1' 00:00:00 ( SUCCESS )
fsck.fat 4.2 (2021-01-31) Checking we can access the last sector of the filesystem Boot sector contents: System ID "mkfs.fat" Media byte 0xf8 (hard disk) 512 bytes per logical sector 4096 bytes per cluster 32 reserved sectors First FAT starts at byte 16384 (sector 32) 2 FATs, 32 bit entries 524288 bytes per FAT (= 1024 sectors) Root directory start at cluster 2 (arbitrary size) Data area starts at byte 1064960 (sector 2080) 130812 data clusters (535805952 bytes) 63 sectors/track, 255 heads 2048 hidden sectors 1048576 sectors total Reclaiming unconnected clusters. Checking free cluster summary. /dev/sda1: 15 files, 4948/130812 clusters
grow file system to fill the partition 00:00:00 ( SUCCESS )
using libparted
========================================
Check and repair file system (ext4) on /dev/sda2 00:00:09 ( SUCCESS )
Pass 1: Checking inodes, blocks, and sizes Inode 2228739 extent tree (at level 1) could be shorter. Optimize? yes
Inode 5638991 extent tree (at level 1) could be shorter. Optimize? yes
Inode 7471117 extent tree (at level 2) could be narrower. Optimize? yes
Inode 7471431 extent tree (at level 2) could be narrower. Optimize? yes
Pass 1E: Optimizing extent trees Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information
/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
1081142 inodes used (3.46%, out of 31227904) 9007 non-contiguous files (0.8%) 1560 non-contiguous directories (0.1%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 1035366/1166/2 65307829 blocks used (52.29%, out of 124895488) 0 bad blocks 14 large files
Not much progress yet, but, let’s try another approach.
Your PC is a Lenovo and the boot-repair report states Warning: NVram is locked (Ubuntu not found in efibootmgr)
Can you access the UEFI settings and disable the following (if they are present)
When you end up in an initramfs shell like this, the fstab is not available yet anyway, the UUID comes from the kernel command line…
With the ls -l /dev/disk/by-uuid popey was on the right track, but you should run it from the initramfs shell to see what disks the kernel found or if it didn’t find one at all …
