Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Problem booting with gentoo-kernel-dist + dracut
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
matt2kjones
Tux's lil' helper
Tux's lil' helper


Joined: 03 Mar 2004
Posts: 96

PostPosted: Thu Nov 14, 2024 11:52 am    Post subject: Problem booting with gentoo-kernel-dist + dracut Reply with quote

Hello,

I have a system using split-usr, openrc & lilo that is currently booting from an old 4.x kernel built with genkernel using gentoo-sources

I'm trying to switch it to gentoo-kernel-dist which is using dracut but I can't get it to boot.

This is my lilo config:

Code:

hercules /boot # cat /etc/lilo.conf
raid-extra-boot=mbr-only

boot=/dev/md1
lba32

prompt
timeout=59
image = /boot/vmlinuz-6.6.58-gentoo-dist
  label = Production
  read-only
  append="init=/linuxrc rootdelay=60 root=/dev/md3 rootfstype=ext4"
  initrd=/boot/initramfs-6.6.58-gentoo-dist.img

image=/boot/kernel-genkernel-x86_64-4.9.72-gentoo
  label=Backup
  read-only
  root=/dev/ram0
  append="init=/linuxrc ramdisk=8192 real_root=/dev/md3 rootfstype=ext4 domdadm"
  initrd=/boot/initramfs-genkernel-x86_64-4.9.72-gentoo

In that lilo config above, the first kernel is the new gentoo-kernel-dist and the second kernel is my old 4.x gentoo-sources built using genkernel which still boots

Now the problem I have, is that if I use the dracut config below, it tries to boot from "root=UUID=7669f93e-bc5b-465e-9208-7ad7581c7dc3" which doesn't exist when dropped into the debug shell:

Code:

# PUT YOUR CONFIG IN separate files
# in /etc/dracut.conf.d named "<name>.conf"
# SEE man dracut.conf(5) for options

# dracut modules to add to the default
add_dracutmodules+=" mdraid "

# additional kernel modules to the default
add_drivers+=" dm_mod dm_mirror dm_log dm_region_hash "

# install local /etc/mdadm.conf
mdadmconf="yes"

# Only build for this host
hostonly="yes"

When in the emergency shell, /dev/md3 DOES exist, so I thought I could just change the above dracut config to include hostonly_cmdline="no" to stop it from using UUID's for boot, like follows:

Code:

# PUT YOUR CONFIG IN separate files
# in /etc/dracut.conf.d named "<name>.conf"
# SEE man dracut.conf(5) for options

# dracut modules to add to the default
add_dracutmodules+=" mdraid "

# additional kernel modules to the default
add_drivers+=" dm_mod dm_mirror dm_log dm_region_hash "

# install local /etc/mdadm.conf
mdadmconf="yes"

# Only build for this host
hostonly="yes"
hostonly_cmdline="no"

However, with the above config it DOES try to boot from /dev/md3 but now that DOESN'T exist, so by adding that hostonly_cmdline="no" option is some-how now stopping /dev/md3 from being created

How do I get this system to boot? I've gone through the dracut gentoo guide but it is very vague on booting from md devices and any troubleshooting related to that.

My live fstab uses the /dev/md devices to mount partitions:

Code:

/dev/md1                                                /boot           ext2            noatime         1 2
/dev/md3                                                /               ext4            noatime         0 1
/dev/md2                                                none            swap            sw              0 0
/dev/md4                                                /mnt/DataArray  ext4            noatime         0 0


Any help would be much appreciated
Back to top
View user's profile Send private message
matt2kjones
Tux's lil' helper
Tux's lil' helper


Joined: 03 Mar 2004
Posts: 96

PostPosted: Thu Nov 14, 2024 12:22 pm    Post subject: Reply with quote

Managed to get it to boot. Missing kernel modules in dracut conf.

/etc/lilo.conf
Code:

raid-extra-boot=mbr-only

boot=/dev/md1
lba32

prompt
timeout=59
image = /boot/vmlinuz-6.6.58-gentoo-dist
  label = Production
  read-only
  initrd=/boot/initramfs-6.6.58-gentoo-dist.img


/etc/dracut.conf
Code:
# PUT YOUR CONFIG IN separate files
# in /etc/dracut.conf.d named "<name>.conf"
# SEE man dracut.conf(5) for options

# dracut modules to add to the default
add_dracutmodules+=" mdraid "

# additional kernel modules to the default
add_drivers+=" raid1 raid456 raid10 dm-raid dm_mod dm_mirror dm_log dm_region_hash "

# install local /etc/mdadm.conf
mdadmconf="yes"

# Only build for this host
hostonly="yes"


Guess the /dev/disk/by-uuid entries weren't created because the mdraid devices were inaccessible even though the /dev/md* device notes were created (maybe because I'm passing in mdadm.conf
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum