24.04 Will Not Boot after I installed it

Support & Help Requests
,
#1

hi all,
i installed Ubuntu mate 24.04 ( clean install ) it will not boot into the OS more than once.
after i booted into the OS i installed updates and then restated all i get is a black screen.
so i ran boot repair then i could boot into 24.04 3 times shut down the computer went to bead the next morning started up the computer and all could get is a black screen tryed to run boot repair but could not get it to work agine.
so i reinstalled Ubuntu mate 24.04 and all it would do is boot into the os 1 time .
so i reinstalled Ubuntu mate 24.04 agine made a custom portion using Ubuntu mate 24.04 would never boot into Ubuntu mate 24.04.
then i reload my backup of 22.04.4 LTS and had no problems booting into it at all.
then tryed to upgrade to Ubuntu mate 24.04 and all i would get is a black screen on start up .
now im back to 22.04.4 LTS with no problems.
any ideas y i cant run Ubuntu mate 24.04.

Kernel: 6.5.0-35-generic x86_64 bits: 64 compiler: N/A Desktop: MATE 1.26.0
Distro: Ubuntu 22.04.4 LTS (Jammy Jellyfish)
Machine:
Type: Desktop Mobo: ASRock model: X570 PG Velocita
serial: UEFI: American Megatrends v: P5.41
date: 09/07/2023
CPU:
Info: 8-core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64
type: MT MCP arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
Speed (MHz): avg: 724 high: 2998 min/max: 400/4673 cores: 1: 400 2: 400
3: 400 4: 400 5: 400 6: 2998 7: 400 8: 2998 9: 400 10: 400 11: 400 12: 400
13: 400 14: 400 15: 400 16: 400 bogomips: 121596
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT / 6800M] vendor: ASRock
driver: amdgpu v: kernel bus-ID: 0f:00.0
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu resolution: 2560x1440
OpenGL: renderer: AMD Radeon RX 6750 XT (navi22 LLVM 15.0.7 DRM 3.54
6.5.0-35-generic)
v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes
Drives:
Local Storage: total: 1.39 TiB used: 29.71 GiB (2.1%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 1TB
size: 931.51 GiB temp: 33.9 C
ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
ID-3: /dev/sdb type: USB vendor: Generic model: SD MMC size: 29.84 GiB
Partition:
ID-1: / size: 915.32 GiB used: 29.71 GiB (3.2%) fs: ext4
dev: /dev/nvme0n1p3
ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat
dev: /dev/nvme0n1p2
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile

1 Like
[Solved]Plymouth appears during startup in various resolutions and after black screen
#2

Welcome @mike2 to the community!

1 Like
#3

thank you
for the work you do on this

1 Like
#4

Hello,

Well, no specific ideas except for possible UEFI misconfiguration. Hopefully SOLVED: Mate does not boot would help.

Good luck!

1 Like
#5

I have UEFI changed to legacy
o and by the way i tryed to
daul boot the system
Ubuntu mate 24.04 and 22.04.4 LTS
nothing worked after that .
i had to
reinstall 22.04.4 LTS with no problems.

1 Like
#6

The latest bios update for that mobo is dated this year. It says for logo fail. Have you updated to the latest bios? That's what I would look at first.

image
image1359×160 32.1 KB

1 Like
#7

ill give it a try thanks

#8

well i updated my bios and set Ubuntu mate 24.04 and 22.04.4 LTS to dual boot .
it will boot into 22.04.4 LTS no problem.
no boot screen if i do f11 i can choose witch one to boot into.
if i pick 24.04 it boot into it one time only . and after that black screen .
so i go in to Ubuntu with linury 6.8.0-31 generic recovery mod and fix boot i can boot back in but the display is set to 1280x720 0 hz but i have to pick generic recovery every time to boot in .

#9

Hi, @mike2 :slight_smile:

You wrote:

When you mention "if i pick 24.04 it boot into it one time only . and after that black screen .", I have the following question: during that black screen, if you press the Esc key of your keyboard, do the boot messages appear? If so could you take a picture of those boot messages (using your smartphone, for instance) and reply again in this same topic, with the picture of those boot messages? Maybe it can help for further troubleshooting.

1 Like
#10

nothing happened . had to reboot 9 times before i could get back in the os.

#11

Hi again, @mike2 :slight_smile:

I'm not sure I can help a lot here, but I'll try.

First, it would be good to know the "layout" of your disk partitions and mountpoints. To do that, please run the following command and report the output (assuming the output does not have any information that you prefer not to disclose):

lsblk | grep --invert-match 'snap'

The next thing would be to change some of the GNU GRUB (GRand Unified Boot Loader) settings, so we have more information to understand what may be happening during the boot process. To do so, inside your Ubuntu MATE 22.04 ("Jammy Jellyfish"), edit your /etc/default/grub file. For instance, if you use the "vim" text editor, run the following command to start editing that file:

sudo vim /etc/default/grub

In that /etc/default/grub file, change the following lines (they may appear in a different order in your file and have other lines between them) :

GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

... so they become the following ones:

GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_CMDLINE_LINUX_DEFAULT=""

After doing that, save and close the file, and then run the following command:

sudo update-grub

For instance, if I run that same command in this laptop that I'm using right now, that has a Dual Boot of Ubuntu MATE 22.04 and Windows 11, I then get the following result:

$ 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-107-generic
Found initrd image: /boot/initrd.img-5.15.0-107-generic
Found linux image: /boot/vmlinuz-5.15.0-105-generic
Found initrd image: /boot/initrd.img-5.15.0-105-generic
Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done

Please, copy the output of the execution of that sudo update-grub command to some text file, so you can also include that output in another reply from you in this same discussion topic.

Now, please reboot the computer. During the reboot, see if the GNU GRUB boot loader menu appears and what are the options that appear in that menu. If possible, take a picture of the screen at that time (for instance, using the camera of your smartphone) and please reply back here with the result. Good luck :slight_smile:

3 Likes
#12

  1. mike@mike-X570-PG-Velocita:~$ lsblk | grep --invert-match 'snap'
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
    sda 8:0 0 465.8G 0 disk
    └─sda1 8:1 0 465.8G 0 part
    sdb 8:16 1 0B 0 disk
    sdc 8:32 1 0B 0 disk
    sdd 8:48 1 0B 0 disk
    sde 8:64 1 0B 0 disk
    sr0 11:0 1 1024M 0 rom
    nvme0n1 259:0 0 931.5G 0 disk
    ├─nvme0n1p1 259:1 0 1G 0 part /boot/efi
    └─nvme0n1p2 259:2 0 930.5G 0 part /
    mike@mike-X570-PG-Velocita:~$

  2. sudo: vim: command not found

i have reinstalled only Ubuntu MATE 24.04 .
i just don't reboot at all

#13

image
image780×541 49.8 KB

#14

Thanks for those outputs, @mike2 :slight_smile: Could you please run the following commands and reply with the corresponding outputs (again, assuming that those outputs do NOT have any information that you don't want to disclose):

lsblk --fs | grep --invert-match '/snap'

sudo fdisk /dev/sda -l

sudo parted /dev/sda print

sudo fdisk /dev/nvme0n1 -l

sudo parted /dev/nvme0n1 print

grep ^[^#] /etc/fstab

1 Like
#15

mike@mike-X570-PG-Velocita:~$ lsblk --fs | grep --invert-match '/snap'
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
└─sda1 ext4 1.0 System backup 6359d8a9-99e3-461b-95ae-ec9972dcfb4b
sdb
sdc
sdd
sde
sr0
nvme0n1
├─nvme0n1p1 vfat FAT32 4463-2C41 1G 1% /boot/efi
└─nvme0n1p2 ext4 1.0 8c20433f-f058-4bc2-8b36-d3ba41bfaeb7 844G 3% /

Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 860
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: 0xd6b7290e

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 976773119 976771072 465.8G 83 Linux

mike@mike-X570-PG-Velocita:~$ sudo parted /dev/sda print
Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 500GB 500GB primary ext

mike@mike-X570-PG-Velocita:~$ sudo fdisk /dev/nvme0n1 -l
Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 980 PRO 1TB
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: gpt
Disk identifier: 8CC885FB-347E-4A18-8E80-A4A3E6C30F54

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 2203647 2201600 1G EFI System
/dev/nvme0n1p2 2203648 1953521663 1951318016 930.5G Linux filesystem

mike@mike-X570-PG-Velocita:~$ sudo parted /dev/nvme0n1 print
Model: Samsung SSD 980 PRO 1TB (nvme)
Disk /dev/nvme0n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 1128MB 1127MB fat32 boot, esp
2 1128MB 1000GB 999GB ext4

mike@mike-X570-PG-Velocita:~$ grep ^[^#] /etc/fstab
/dev/disk/by-uuid/8c20433f-f058-4bc2-8b36-d3ba41bfaeb7 / ext4 defaults 0 1
/dev/disk/by-uuid/4463-2C41 /boot/efi vfat defaults 0 1
/swap.img none swap sw 0 0

#16

Thanks again, @mike2 :slight_smile:

So, If I understood correctly, based on all your previous messages:

1 - The first logical storage drive - /dev/sda - is a "Samsung model: SSD 860 EVO 500GB size: 465.76 GiB", with type "dos" - that is, it has a MBR (Master Boot Record) partition table - and has only one partition - /dev/sda1, formatted as ext4, and has a label of "System backup". You use that SSD for saving your backups, right? Is that an internal SSD -OR- is it an external SSD (connected via USB)?

2 - The second logical storage drive - /dev/nvme0n1 - is a "Samsung model: SSD 980 PRO 1TB size: 931.51 GiB", with type "gpt" - that is, it has a GPT (GUID Partition Table) - that has 2 partitions:

  • /dev/nvme0n1p1 formatted as "vfat" where the ESP (EFI System Partition) resides and that is mounted on /boot/efi
  • /dev/nvme0n1p2 formatted as "ext4" that is mounted on / that has your Ubuntu MATE 24.04 LTS ("Noble Numbat") installation.

Did I understand correctly your setup?

If I did understand correctly your setup, I would do what I describe below. There are some risks involved, so please FIRST make sure that you have some kind of USB flash drive with Ubuntu MATE 22.04 or Ubuntu 24.04 that you can boot from (in case you stop being able to boot from your hard drive) AND, preferably, also guarantee that you have a good BACKUP of your data in some kind of external drive!

1 - You've mentioned that you have your UEFI settings changed to Legacy. But, according to your setup, it seems to me that is not necessary, given that your Ubuntu MATE 24.04 drive has a GPT (GUID Partition Table) and an ESP (EFI System Partition). Is there any particular reason why you changed it to Legacy?

2 - I would do the same changes to the /etc/default/grub file in your Ubuntu MATE 24.04 installation that I had suggested in my previous message for your Ubuntu MATE 22.04 installation and, based on your setup, I would also UNCOMMENT (that is, REMOVE the initial # sign to activate it) from the line #GRUB_DISABLE_OS_PROBER=false. So, change the following line:

#GRUB_DISABLE_OS_PROBER=false

... so it becomes the following line:

GRUB_DISABLE_OS_PROBER=false

So, please edit that file with administrator privileges, by running the following command (that will open the "Pluma" text editor as superuser):

sudo pluma /etc/default/grub

In that /etc/default/grub file, change the following lines

GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
#GRUB_DISABLE_OS_PROBER=false

... so they become the following ones:

GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_DISABLE_OS_PROBER=false

After doing that, save and close the file, and then run the following command:

sudo update-grub

Please, copy the output of the execution of that sudo update-grub command to some text file, so you can also include that output in another reply from you in this same discussion topic.

Now, please reboot the computer. During the reboot, go to your UEFI Settings and change it from Legacy to UEFI, save your changes and exit the UEFI. After that, see if the GNU GRUB boot loader menu appears and what are the options that appear in that menu. If possible, take a picture of the screen at that time (for instance, using the camera of your smartphone) and please reply back here with the result. And again: Good luck! :slight_smile:

3 Likes
#17

thanks trying it now

2 Likes
#18

mike-X570-PG-Velocita:~$ sudo update-grub
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.0-31-generic
Found initrd image: /boot/initrd.img-6.8.0-31-generic
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
done

2 Likes
#19

IMG_1868
IMG_18681600×1200 275 KB

2 Likes
#20

well so for it has booted fine 5 times with no problems

2 Likes