[SOLVED] (Another) mkinird question

I have been building generic kernels on 64-current for a while now and all runs just fine when I build my initrd.gz using "mkinitrd -c -R -k $kerno -m ext4"(no quotes) in a short script where I prompt for the kernel version. If I use the mkinitrd shell script in /usr/share to generate a mkinitrd.conf in /etc and then generate my initrd.gz using mkinitrd -c -F at a command prompt from the /boot directory it generated the initrd.gz but the system won't boot, stopping shortly after the boot starts saying that it can't find /mnt. The mkinitrd.conf file is -

Code:cat mkinitrd.conf
#
# 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 5.12.12 -f ext4 -r /dev/md126 -m xhci-pci:ohci-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:crc32c_generic:ext4 -R -u -o /boot/initrd.gzThis is exactly what happened some time ago when I tried to boot a generic kernel and had not read the man page thoroughly for mkinitrd and had neglected to add the -R command line parameter to reflect that it is a raid system. The mkinitrd.conf file does however include a -R so that should not be the problem.

I'm Probably missing something obvious but can't see forrest for trees at this point. Thanks in advance.