For instance, when I try to boot Mageia I'm getting a message that uuid 894e96b8-etc. doesn't exist before crashing into dracut shell. Yet, when I do lsinitrd on all the initrd's in my boot folder, none of them have that ID. It's very odd.
- Code: Select all
menuentry 'Mageia 4 latest tip' {
insmod part_msdos
insmod ext2
search --no-floppy --fs-uuid --set=root 894e96b8-3836-41d2-b887-1d7355ac62f6
linux /boot/vmlinuz-desktop root=UUID=894e96b8-3836-41d2-b887-1d7355ac62f6 ro nokmsboot profile rd.hostonly=0 3
initrd /boot/initrd-desktop.img
## initrd options
#initrd initrd-3.12.25-desktop-3.mga4.img
#initrd initrd-3.13.0-46-generic.img.bak1
#initrd initrd-3.14.24-desktop-1.mga4.img.bak1
#initrd initrd-3.19.2-1-ARCH.img
#initrd initrd-3.2.0-34-generic.img
#initrd new-initrd.imgm
#systemd.unit=multi-user
#rd.hostonly=0
}
initrd-desktop.img is a link pointing to "/boot/initrd-3.19.2-1-ARCH.img"
Suffice it to say, I am still buggered in dracut shell.
But:
- Code: Select all
lsinitrd /boot/initrd-desktop.img | grep -e uuid
lrwxrwxrwx 1 root root 16 Mar 24 17:04 usr/lib64/libuuid.so.1 -> libuuid.so.1.3.0
-rwxr-xr-x 1 root root 15864 Mar 24 17:04 usr/lib64/libuuid.so.1.3.0
and
- Code: Select all
lsinitrd /boot/initrd-3.19.2-1-ARCH.img | grep -e uuid
lrwxrwxrwx 1 root root 16 Mar 24 17:04 usr/lib64/libuuid.so.1 -> libuuid.so.1.3.0
-rwxr-xr-x 1 root root 15864 Mar 24 17:04 usr/lib64/libuuid.so.1.3.0
I'm quite confused but I'm getting better at this, thanks to your help!
OMS!!!
PS Here's my Mage boot folder in case this is helpful:
- Code: Select all
ls /boot/ | grep initrd
initrd-3.12.25-desktop-3.mga4.img
initrd-3.13.0-46-generic.img.bak1
initrd-3.14.24-desktop-1.mga4.img.bak1
initrd-3.19.2-1-ARCH.img
initrd-3.2.0-34-generic.img
initrd-desktop.img@
initrd.img.bak1@
new-initrd.img