Boot error message (mkinitrd_command_generator.sh)

samac · 03-04-2010, 04:12 AM

Quote:

You may need to create an initrd (Read /boot/README.initrd) or you can try the script "/usr/share/mkinitrd/mkinitrd_command_generator.sh" to help create one.

This didn't work for me, and I usually have no problems making an initrd.gz and running the generic kernel it failed with the following error

Quote:

mounting /dev/sda1 on /mnt failed
ERROR: no /sbin/init found on rootdev

samac

Alien Bob · 03-04-2010, 05:11 AM

Quote:

Originally Posted by samac

This didn't work for me, and I usually have no problems making an initrd.gz and running the generic kernel it failed with the following error

samac

Samac, why did mkinitrd_command_generator.sh not work for you? I want this script to function in all cases if possible. If you have any error output and PC configuration details, I'd appreciate it.

Eric

samac · 03-04-2010, 07:50 AM

Hi Eric Output follows:

Quote:

samac@quad:~$ su
Password:
root@quad:/home/samac# /usr/share/mkinitrd/mkinitrd_command_generator.sh
#
# mkinitrd_command_generator.sh revision 1.40
#
# 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 2.6.33 -f ext4 -r /dev/sda1 -m ext4 -o /boot/initrd.gz
root@quad:/home/samac#

Quote:

root@quad:/home/samac# uname -a
Linux quad 2.6.33 #1 SMP Wed Mar 3 21:51:23 GMT 2010 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux
root@quad:/home/samac#

Quote:

root@quad:/home/samac# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda
compact
lba32
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
default = Linux
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 20
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.33
root = /dev/sda1
initrd = /boot/initrd.gz
label = Slackware64
read-only
# Linux bootable partition config ends
root@quad:/home/samac#

Not sure how to get the boot error message as I have to reboot the machine but the post above gives the general idea. How much detail do you need on the hardware or in uname -a enough?

samac

damgar · 03-04-2010, 08:05 AM

nevermind

samac · 03-04-2010, 08:15 AM

There is nothing in /var/log/syslog, as I suspected, because it does not boot passed the initrd.gz into the system on the disk, but thanks for the idea.

samac

damgar · 03-04-2010, 08:28 AM

Yeah I realized that was going to happen as soon as I hit submit.

Alien Bob · 03-04-2010, 09:44 AM

Quote:

Originally Posted by samac

Not sure how to get the boot error message as I have to reboot the machine but the post above gives the general idea. How much detail do you need on the hardware or in uname -a enough?

samac

No need for the exact boot error message I think; what you posted was OK.
When the tool suggests this line:

Code:

mkinitrd -c -k 2.6.33 -f ext4 -r /dev/sda1 -m ext4 -o /boot/initrd.gz

was that what you would have used as well?
And did you actually run this command to create the initrd.gz (not thinking you're dumb, just have to ask this to be very sure) and then run lilo? Because your system setup really does not look all that exotic and the command should have produced a working initrd/

Eric

samac · 03-04-2010, 09:57 AM

I tried my usual first

Code:

mkinitrd -c -k 2.6.33 -m ext4 -f ext4 -r /dev/sda1

which I cut and modified from the initrd.readme in /boot ie. mkinitrd -c -k 2.6.32.3 -m ext4 -f ext4 -r /dev/sdb3. I then used your script /usr/share/mkinitrd/mkinitrd_command_generator.sh and it returned

Quote:

mkinitrd -c -k 2.6.33 -f ext4 -r /dev/sda1 -m ext4 -o /boot/initrd.gz

lilo was re-run in both cases and exited without error.

The only thing that was different from normal was running this list of commands to get my Nvidia driver working. http://www.linuxquestions.org/questi...ml#post3884572

samac

samac · 03-04-2010, 10:00 AM

I was also missing a working 32-bit extensions because libuuid had been moved from e2fsprogs to util-linux-ng and I had to create a new compat32 version.

samac

samac · 03-04-2010, 11:40 AM

It leaves me at a busy box prompt asking if I want to fix it, entering exit brings up more errors and a strace.

gegechris99 · 03-04-2010, 04:15 PM

Hello,

FYI, mkinitrd worked for me on Slackware -current 32-bits and LVM partition:

Code:

cd /boot
mkinitrd -c -k 2.6.33-smp -m ext4 -f ext4 -r /dev/vg/root -L
lilo

samac · 03-05-2010, 01:47 AM

Apologies. I have asked a moderator to split out the non-relevant bits.

samac

samac · 03-05-2010, 01:27 PM

Eric

I have fixed the problem by re-installing the kernel packages. It is strange that it did not work before, as it was a fresh install. Maybe this

Quote:

cp /boot/config-huge-2.6.33 /usr/src/linux-2.6.33/.config && cd /usr/src/linux-2.6.33 && make && make modules_install && cp arch/x86_64/boot/bzImage /boot/vmlinuz && lilo && echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf && telinit 6

caused the problem.

samac