mkinitrd script not working

allend · 01-21-2019, 07:29 AM

Quote:

i canrt find any logs... does te mkinitrd generator log anywhere/?

Try 'cat /boot/initrd-tree/command_line' to show the last command used to build the initrd.

This has been in -current since Tue Oct 10 18:08:31 UTC 2017.

Alien Bob · 01-21-2019, 08:42 AM

Quote:

Originally Posted by business_kid

If you're on Slackware, ignore that and simply run (as root)

Code:

# /sbin/mkinitrd  -c -f <your root filesystem> -r <root device>

You might want to add -m <modules> but this in mounted on /. Itonly has to get your root filesystem loaded and mounted on /, at which point it's overwritten by the root filesystem, and vanishes. You don't need the kitchen sink in it.

I think it's you who ignored information.

Quote:

Originally Posted by wigums

fresh current install with lvm/luks

Your own trivial mkinitrd command will only work for trivial installs. It won't result in a useful commandline for a LUKS/LVM configuration.

wigums · 01-21-2019, 10:04 AM

here are the asked for results of mkinitrd generator vs the interactive mkinitrd

NOT INTERACTIVE
mkinitrd -c -k 4.19.16 -f ext4 -r /dev/cryptvg/root -C /dev/sda2 -L -u -o /boot/initrd.gz

INTERACTIVE
mkinitrd -c -k 4.19.16 -f ext4 -r /dev/cryptvg/root -m xhci-pci

hci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:crc32c-intel:ext4 -C /dev/sda2 -L -u -o /boot/initrd.gz

business_kid · 01-22-2019, 04:12 AM

I don't know why it has all that usb stuff. You don'y need any of it to mount /.

What's the errors? Why doesn't it work?

wigums · 01-22-2019, 04:30 AM

if i knew why it didnt work id fix it. all i know is the non interactive command doesnt produce a working initrd while the interactive command does create a working initrd

wigums · 01-22-2019, 04:32 AM

alienBOB do what?!?!

Quote:

Your own trivial mkinitrd command will only work for trivial installs. It won't result in a useful commandline for a LUKS/LVM configuration.

i dont use my own command. i use the generator. i think you dont understand my problem

Alien Bob · 01-22-2019, 07:47 AM

Quote:

Originally Posted by wigums

alienBOB do what?!?!

i dont use my own command. i use the generator. i think you dont understand my problem

Nah, that was not meant as a comment to you. It was meant for business_kid who showed a trivial mkinitrd command that will not work for your LUKS/LVM setup.

_peter · 01-22-2019, 08:36 AM

Quote:

Originally Posted by wigums

re: the command the interactive output theres no was i can remember it. it was 3 full screen lines
(thats adds up to a string approx 69" long LOL)

always have had long strings upon failed boot with fresh /boot/initrd.gz when i forgot to re-run lilo or made mistakes with its configuration

LVM/LUKS, probably not running lilo, are you ?

as said by business_kid, the usb stuff, try disconnecting anything non-native to your hardware before booting & re-running the below

Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh

GazL · 01-22-2019, 08:50 AM

Quote:

Originally Posted by wigums

if i knew why it didnt work id fix it. all i know is the non interactive command doesnt produce a working initrd while the interactive command does create a working initrd

Well, from a cursory glance, your "non-interactive" command is missing at least '-m ext4' which will be required when using the slackware 'generic' kernel.

BTW, '-u' is unnecessary. It's been the default for quite a while.

Alien Bob · 01-22-2019, 12:43 PM

Let's take a step back.

You do realize that you need to run the command inside chrooted Slackware installation, right? If you run the generator command in the Slackware installer environment, you will not get the correct results.

I tried my own machine for fun. This is what the non-interactive command returns:

Code:

root@hogan:/# /usr/share/mkinitrd/mkinitrd_command_generator.sh  
#
# mkinitrd_command_generator.sh revision 1.45
#
# This script will now make a recommendation about the command to use
# in case you require an initrd image to boot a kernel that does not
# have support for your storage or root filesystem built in
# (such as the Slackware 'generic' kernels').
# A suitable 'mkinitrd' command will be:

mkinitrd -c -k 4.19.2 -f ext4 -r /dev/nvme0n1p7 -m usb-storage:xhci-hcd:xhci-pci:ohci-pci:ehci-pci:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:crc32c-intel:ext4 -u -o /boot/initrd.gz

You notice that this non-interactive comandline lists a lot of kernel modules (the "-m" parameter). It is a Slackware 14.2 machine with a custom kernel, additional USB storage attached and the root partition is a ext4 filesystem on a NVMe drive.
I used this exact output to generate the initrd and my computer boots just fine.

philanc · 01-22-2019, 03:17 PM

Quote:

Originally Posted by business_kid

I don't know why it has all that usb stuff. You don'y need any of it to mount /

@business_kid: Yes the USB stuff is needed because a keyboard is needed to read the cryptsetup/LUKS password, and the PC may have only a USB keyboard.

business_kid · 01-22-2019, 05:14 PM

Quote:

Originally Posted by philanc

@business_kid: Yes the USB stuff is needed because a keyboard is needed to read the cryptsetup/LUKS password, and the PC may have only a USB keyboard.

Well, if his hd is encrypted, then I suppose it is needed. I wasn't aware it was added by default.

wigums · 01-22-2019, 06:54 PM

i wrote this.... tell me its wrong

https://slackwiki.com/LVM/Luks_Encryption

Richard Cranium · 01-22-2019, 11:24 PM

Quote:

Originally Posted by wigums

i wrote this.... tell me its wrong

https://slackwiki.com/LVM/Luks_Encryption

I haven't tried what you wrote, but it looks correct to me. I've used LVM and LUKS on both of my laptops (down to one laptop after I dropped one and broke the screen). Encrypting the PV is the way to go, IMO.

wigums · 01-23-2019, 04:15 PM

point being is that i know how to do it and im getting crap commands from the generator.
im over it. i can get a valid command from the interactive generator. youd think id know better than to ask slackers for help with slackware by now