LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 12-20-2013, 11:20 PM   #1
octetstream
LQ Newbie
 
Registered: Dec 2006
Posts: 7

Rep: Reputation: 0
Slackware64 14.1 initrd for generic kernel can't find RAID1 root partition


Okay guys, I'm starting to feel like a serious n00b with this one. I've been using Slackware since the 7.0 days, and RAID1/5 since the 10.0 days. For the life of me, I can't find a single mkinitrd command that will let me boot the generic kernel.

For starters, my drives are in a (soft) RAID1 configuration setup from Slackware 14.0, and I've successfully performed an install of Slackware64 14.1 after formatting my root (/dev/md3) and boot (/dev/md1) partitions (/dev/md4 is /home, which does not get formatted). All are formatted with ext4. The huge kernel boots my system with no problem. After failing at installing VMWare (like a n00b) I decided to switch to the generic kernel and attempted to build an initrd filesystem.

First, prior to finding http://www.linuxquestions.org/questi...id-4175488307/, I had been making a mkinird command by hand. Of course, this didn't work. I've since used mkinitrd_command_generator.sh to create a mkinitrd command, added -L as suggested in the link (although I'm not using LVM). During boot the kernel still can't find my root RAID1 partition, but it does load my keyboard modules and I can run commands to check what's being detected.

As mentioned in the other post, my raid partitions are given random numbers as they're discovered. When I review fdisk, it complains about my partitions not existing on cylinder boundaries, which I ignore. According to fdisk -l, my /dev/md1 partition is currently represented as /dev/md127, /dev/md3 is /dev/md126, and /dev/md4 is /dev/md125. After booting to a root shell, the kernel complains that it can't find a valid rootdev partition.

The mkinitrd command I've used to get this far is:
Code:
mkinitrd -c -k 3.10.17 -f ext4 -r /dev/md3 -m usbhid:hid_generic:ohci-hcd:xhci-hcd:mbcache:jbd2:ext4 -R -L -u -o /boot/initrd.gz
The important sections of my lilo.conf (comments removed)look like this:
Code:
append=" vt.default_utf8=0"
boot = /dev/sda
  bitmap = /boot/slack.bmp
  bmp-colors = 255,0,255,0,255,0
  bmp-table = 60,6,1,16
  bmp-timer = 65,27,0,255
prompt
timeout = 1200
change-rules
  reset
vga = normal
image = /boot/vmlinuz # symlinked to the generic kernel
  initrd = /boot/initrd.gz
  root = /dev/md3
  label = Linux
  read-only
image = /boot/vmlinuz-huge-3.10.17
  root = /dev/md3
  label = "Huge"
  read-only
I'm obviously doing something wrong. Does anybody see my error?
 
Old 12-20-2013, 11:24 PM   #2
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,575

Rep: Reputation: 466Reputation: 466Reputation: 466Reputation: 466Reputation: 466
http://www.linuxquestions.org/questi...7/#post5084215
 
Old 12-21-2013, 08:28 AM   #3
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,575

Rep: Reputation: 466Reputation: 466Reputation: 466Reputation: 466Reputation: 466
Or to put it in another way: If you have the file /etc/mdadm.conf in your initrd, then it must contain the information required to build your raid arrays. If you don't have the file /etc/mdadm.conf in your initrd at all, then the init code will attempt to scan for your raid arrays and build them for you.

The default /etc/mdadm.conf that is installed as part of the mdadm package does not contain any default information in it that would build any arrays; it has only comments in it.

The copying of /etc/mdadm.conf into the initrd-tree is new behavior in 14.1; that's why we haven't seen this odd behavior in earlier releases.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Initrd for kernel 3.8.11 and encrypted luks root partition in current Phorize Slackware 8 06-15-2013 10:04 AM
Where can I find generic vmlinuz and initrd.img files? seannachie Linux - General 8 05-06-2012 03:25 PM
[SOLVED] setting up initrd / generic kernel in Grub2...can't load generic Ubunoob001 Slackware 8 01-06-2011 12:37 AM
Generic kernel + initrd not working rpedrica Slackware 12 06-22-2010 11:17 AM
Generic SMP kernel with no initrd? songangel Slackware 8 03-26-2009 07:12 PM


All times are GMT -5. The time now is 10:26 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration