On a server where i was updating slackware i had the need to use mkinitrd, because on this machine there was an hardware SCSI
controller (mtpspi kernel module) and an ext4 root partition, as usual i typed:
but after checking initrd-tree directory i found mtpspi* modules were missing.
Instead these were included if i typed:
Perhaps modules searching (and dependencies) are affected by the alphabetical names.
This could be a big problem because there is a risk that a machine like this refuses to boot.

A quick look at the file /sbin/mkinitrd version 1.4.8 module search should be around line 624.

Are you sure it's not mptspi?

--mancha

yes, I'm sorry I misspelled, but the problem remains.

I'm unable to reproduce your problem.

Can you run the following:

and post log1.txt & log2.txt to a pastebin (e.g. dpaste.com)?

--mancha

No, I am sorry.
My job is behind a firewall that blocks certain sites.

Anyway oddity may be shown by temporarily renaming /boot/initrd.gz to /boot/initrd.gz.original and
/boot/initrd-tree to /boot/initrd-tree.original, then typing as I said in the first post
and checking /boot/initrd-tree/lib/modules/3.xx.xx/kernel.

Of course, don't forget to put back /boot/initrd.gz.original to /boot/initrd.gz.

@ mkinitrd mantainers

it would not hurt if it were added to a dry-run option to the script mkinitrd to control his intentions before he does damage ...

Does it matter?

Just run mkinitrd with proper -s and -o options.

1 members found this post helpful.

Probably was my mistake (typed mtpspi instead mptspi), thank you all for the answers.

In post #5, the mkinitrd commands I originally posted to debug OP's issue mangle /dev/null.

For anyone who happened to run these, please fix your /dev/null with:

I've edited that post since to remove the error.

--mancha