Slackware 14.2 with mdadm software RAID. I am using GPT drives and using GRUB2 instead of LILO. I can turn on the PC and I get to where grub boots. After that when I hit enter it loads some kernel text but then it panics and it says

Before that I am also getting "Invalid raid superblock on sdX" X for whatever partition.

My /etc/fstab looks like this

http://i.imgur.com/zzsGv1Ih.jpg

I would also like to note that I am using Metadata 1.2 on all partitions for the RAID....I hope this is not a problem. To give more info.

/dev/md0 is /var RAID1 with sda1 and sdb1.
/dev/md1 is /swap RAID10 on sd[c-f]1
/dev/md2 is /boot RAID10 on sd[c-f]2
/dev/md3 is / RAID10 on sd[c-f]3

I am in the process of making sure /boot/grub/grub.cfg is in all 4 hard drives/partitions and will be changing /etc/fstab to use UUIDs.

Here is my mkinitrd, http://i.imgur.com/uwvwCJ1h.jpg I made sure /dev/md2 was mounted as the is where /boot partition is located in the RAID. I also ran the grub mkconfig command again.

Now I am getting "mount: can't find /mnt in /etc/fstab"

"ERROR: No /sbin/init found on rootdev (or not mounted).

The kernel can't find your boot device. What kernel parameters are you passing?

I don't have a clue, could you tell me where I could find such things? I Haven't Been Messing With slackware installations in about a year and I've forgotten where many things are...especially with grub as I normally just use lilo. Also please note that I am no longer getting that error now that I made the initramfs. I am getting

"mount: can't find /mnt in /etc/fstab"

"ERROR: No /sbin/init found on rootdev (or not mounted).

So I looked online at where I could see kernel parameters and I'll see if I can get a picture.

Here are some of the kernel parameters...I think http://m.imgur.com/gyOeqS8,lQf1Hjq

Have you tried /usr/share/mkinitrd/mkinitrd_command_generator.sh to see if you're using a decent mkinitrd command? It needs to specify the root partition and all modules your system needs to start.

I tried that and I think that's where the problem lied. I instead followed this post http://www.linuxquestions.org/questi...1/#post5307864 and how he made his mkinitrd. The kernel finally loads except I noticed a couple of "could not insert" while the kernel was loading and one of those was ext4, the other was jbd2 or something...I have no clue what these are but the ext4 scares me. I am also stuck using the huge kernel now.....I am afraid of changing anything lol, I'm afraid to upgrade to the 4.4.19 also loo.

What was the output when you ran it?

I just ran it again and it shows those missing things, jb2, ext4, and now I notice mbcache with an "added" symbol. http://i.imgur.com/oZKMCxEh.jpg I'm going to rerun the grub-mkconfig command.

Maybe I'm doing something wrong, but that link shows almost nothing that is useful.

And I'll admit that my post was not specific enough.

What I should have asked (but did not) was...

Sorry. Okay, lets get a few things clear to avoid confusion. So, I linked that post before, I believe #15 because I copied that method that he did to generate the mkinitrd, which involved making that /etc/mkinirtd file or whatever, editing it, and then doing mkinitrd -F or whatever the command was. Previously, I had tried to use the script from the Slackware docs beginners guide , and I got...strange...what is showing up is now (I just ran that command) is ENTIRELY different from what I got when I ran it before, possibly because I was using the livecd and chrooted (I had no choice as I couldn't boot into it directly). I am going to run what you want me to run now, except note that I am only on kernel 4.4.14 and not 4.4.19 yet. When I run that command you told me to ran I get this, which is the same as the command in Slackware beginner's guide

The last time I ran was when I was in the livecd chrooted, I had a lot of weird stuff showing up, a lot of "linux_raid_member" stuff, about 14 of them to be exact and nothing that I see here. That is probably why it wouldn't boot correctly, though I remember now I had some other weird issue that was preventing the boot procedure before I tried generating an initramfs. I am going to run the output I got above in a bit and see if I can boot.

The cause of mount error about /etc/fstab:
http://www.linuxquestions.org/questi...0/#post5574558