On 27 May 2026 at 7:46, Go Canes wrote:

From:                   Go Canes <[email protected]>
Date sent:              Wed, 27 May 2026 07:46:21 -0400
Subject:                Re: Had a major issue with machine not booting 
fully.
To:                     [email protected],
        Community support for Fedora users 
<[email protected]>
Send reply to:          Community support for Fedora users 
<[email protected]>

> > > On 5/26/26 8:53 PM, Michael D. Setzer II via users wrote:
> > > > Machine booting with rescue kernel gets to this point.
> > > >
> > > > Job dev-disk-by\x2duuid-9we0af15\x2...tart running (8min 14s
> 
> Confirm disk/partition UUIDs in:
> -  /boot/efi/EFI/fedora/grub.cfg
> -  /boot/grub2/grub.cfg
> -  /etc/kernel/cmdline

At moment don't have access to bad machine (103 last ip digit), 
tried to have it boot from kernel, but must be sitting at the previous 
line. So can't vnc or telnet into it). 
Machine 80 that I had done a bit level copy of sda1 sda2 sda3 (boot 
swap and /) from.

It shows fromt /boot
find . | grep grub.cfg
./grub2/grub.cfg

It has 264 lines, but only one with UUID?
  set 
kernelopts="root=UUID=1a2e295f-8e7e-463b-ad2c-938075a880c8 
ro resume=UUID=92e0af15-a78a-443e-a6cf-6f23cd3be54f rhgb 
quiet rd.driver.blacklist=nouveau,nova_core 
modprobe.blacklist=nouveau,nova_core "

will have to check those UUID numbers on machine 103 when I get 
access again. but this works find on machine 80?
Again did bit level copies of sda1 sda2 and sda3 /boot swap and / so 
those are identicle between machine 80 and 103. Did change the 
/etc/hostname and fstab file to make sure they matched. Did also 
change the /home partition in fstab to use the correct /dev/sda5 
UUID. 

Try to boot the rescue kernel in case there is a difference. Some 
machines have same motherboards, but not sure is 80 and 103 are 
100%. 
cat 
/boot/loader/entries/bd97d9dfc2d04f1cb050aff929929ddf-0-rescue.
conf 

title Fedora Linux (0-rescue-bd97d9dfc2d04f1cb050aff929929ddf) 
43 (Workstation Edition)
version 0-rescue-bd97d9dfc2d04f1cb050aff929929ddf
linux /vmlinuz-0-rescue-bd97d9dfc2d04f1cb050aff929929ddf
initrd /initramfs-0-rescue-bd97d9dfc2d04f1cb050aff929929ddf.img
options root=UUID=1a2e295f-8e7e-463b-ad2c-938075a880c8 ro 
resume=UUID=92e0af15-a78a-443e-a6cf-6f23cd3be54f rhgb quiet 
rd.driver.blacklist=nouveau,nova_core 
modprobe.blacklist=nouveau,nova_core 
grub_users $grub_users
grub_arg --unrestricted
grub_class fedora

My G4L entry that works fine on both 80 and 103.
# cat 
/boot/loader/entries/bd97d9dfc2d04f1cb050aff929929ddf-0-G4L.co
nf 
title G4L 0.70
version 0.G4L
linux /bz7x0.10 telnetd=yes
initrd /initramfs.lzma $tuned_initrd
grub_users $grub_users
grub_arg --unrestricted
grub_class fedora

That boots and allows me to telnet into machine 103.
Both machines use regular partitions. Don't have UEFI boot and no 
secure boot. 

So, G4L works, just using the custom /boot/bz7x0.10 kernel and 
initramfs.lzma.
ls -l /boot/bz7x0.10 /boot/initramfs.lzma | cut -b 25-200
13329408 May 23 23:51 /boot/bz7x0.10
26251886 May 23 23:51 /boot/initramfs.lzma

ls -l /boot/*rescue* | cut -b 25-200
291013189 May 16 15:03 
/boot/initramfs-0-rescue-bd97d9dfc2d04f1cb050aff929929ddf.img
 18434408 May 16 15:02 
/boot/vmlinuz-0-rescue-bd97d9dfc2d04f1cb050aff929929ddf

Could be something since blkid on partitions 1,2,3 match? Perhaps 
dracut build some physical drive option as being different.

Thanks. When get access to 103 again, will check. Brother has to 
manually restart machine and select g4l option.

Pretty sure if I did a full image of disk in machine 80 to 103, it 
would probable boot. But would require that disk size of 103 would 
need to be same of larger. 

Again, thanks for info.
Machines are Fedora 43 at moment. Have one machine here with 
44, but just doing testing. 




> 
> IIRC, if /etc/kernel/cmdline is wrong you'll have to build a new initramfs.
> -- 
> _______________________________________________
> users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[email protected]
> Do not reply to spam, report it: 
> https://forge.fedoraproject.org/infra/tickets/issues/new


+------------------------------------------------------------+
 Michael D. Setzer II - Computer Science Instructor (Retired)     
 mailto:[email protected]                            
 mailto:[email protected]
 mailto:[email protected]
 Guam - Where America's Day Begins                        
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+



-- 
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to