Home » Uncategorized » 6 January 2009 » 3,112 supporters » No Comment »

extract initrd to trace kernel panic

6 January 2009 3,112 supporters No Comment

This is for my record. In case i have format my laptop. I still have this record.

Currently i want to get openvz to work in my fedora after successfully instal in Ubuntu 8.10. After booting with new Stable kernel openVZ i get kernel panic. So i suspect it have something to do with the initrd.

I have to extract initrd.

[root@localhost boot]# mkdir initrd
[root@localhost boot]# cp initrd-2.6.18-92.1.13.el5.028stab059.6.img initrd
[root@localhost boot]# cd initrd
[root@localhost initrd]# ls
[root@localhost initrd]# gzip -dc initrd-2.6.18-92.1.13.el5.028stab059.6.img | cpio -id
16615 blocks
[root@localhost initrd]# ls
bin  etc   initrd-2.6.18-92.1.13.el5.028stab059.6.img  lib64  sbin  sysroot
dev  init  lib                                         proc   sys   usr

The most important thing is init…

[root@localhost initrd]# cat init

mount -t proc /proc /proc
echo Mounting proc filesystem
echo Mounting sysfs filesystem
mount -t sysfs /sys /sys
echo Creating /dev
mount -o mode=0755 -t tmpfs /dev /dev
mkdir /dev/pts
mount -t devpts -o gid=5,mode=620 /dev/pts /dev/pts
mkdir /dev/shm
mkdir /dev/mapper
echo Creating initial device nodes
mknod /dev/null c 1 3
mknod /dev/zero c 1 5
mknod /dev/systty c 4 0
mknod /dev/tty c 5 0
mknod /dev/console c 5 1
mknod /dev/ptmx c 5 2
mknod /dev/fb c 29 0
mknod /dev/tty0 c 4 0
mknod /dev/tty1 c 4 1
mknod /dev/tty2 c 4 2
mknod /dev/tty3 c 4 3
mknod /dev/tty4 c 4 4
mknod /dev/tty5 c 4 5
mknod /dev/tty6 c 4 6
mknod /dev/tty7 c 4 7
mknod /dev/tty8 c 4 8
mknod /dev/tty9 c 4 9
mknod /dev/tty10 c 4 10
mknod /dev/tty11 c 4 11
mknod /dev/tty12 c 4 12
mknod /dev/ttyS0 c 4 64
mknod /dev/ttyS1 c 4 65
mknod /dev/ttyS2 c 4 66
mknod /dev/ttyS3 c 4 67
/lib/udev/console_init tty0
daemonize –ignore-missing /bin/plymouthd
plymouth –show-splash
echo Setting up hotplug.
echo Creating block device nodes.
echo Creating character device nodes.
echo “Loading ehci-hcd module”
modprobe -q ehci-hcd
echo “Loading ohci-hcd module”
modprobe -q ohci-hcd
echo “Loading uhci-hcd module”
modprobe -q uhci-hcd
mount -t usbfs /proc/bus/usb /proc/bus/usb
echo “Loading scsi_mod module”
modprobe -q scsi_mod
echo “Loading sd_mod module”
modprobe -q sd_mod
echo “Loading libata module”
modprobe -q libata
echo “Loading ahci module”
modprobe -q ahci
modprobe scsi_wait_scan
rmmod scsi_wait_scan
resume UUID=c9ac6dfd-1b8c-496e-b603-56b49788e888
echo Creating root device.
mkrootdev -t ext2 -o defaults,ro UUID=254ded33-dad8-4637-b4db-f3a9ba426a25
echo Mounting root filesystem.
mount /sysroot
cond -ne 0 plymouth –hide-splash
echo Setting up other filesystems.
plymouth –newroot=/sysroot
echo Switching to new root and running init.
echo Booting has failed.
sleep -1
[root@localhost initrd]#

I need more research on this..

Leave your response!

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.