LinuxQuestions.org - kernel panic - not syncing: Attempted to kill init!

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - kernel panic - not syncing: Attempted to kill init! (https://www.linuxquestions.org/questions/linux-general-1/kernel-panic-not-syncing-attempted-to-kill-init-305582/)

kernel panic - not syncing: Attempted to kill init!

I'm currently running Fedora Core 3 with the 2.6.10.770_FC3 kernel.
I wanted to take a look at Zen Linux, so I downloaded the Zen Linux Gnome live CD iso.
After burning the cd, I tried it and it failed to start X. I rebooted and now I get a kernel panic when I boot FC3. Here are the last few lines of the boot process:

Code:

Mounting root filesystems 

ReiserFS: dm-0: found reiserfs format "3.6" with standard journal 

ReiserFS: dm-0: using ordered data mode 

ReiserFS: dm-0: journal params: device dm-0, size 8192 journal first block 18,

max trans len 1024, max batch 900, max commit age 30, max trans age 30

ReiserFS: dm-0: checking transaction log (dm-0) 

ReiserFS: dm-0: Using r5 hash to sort names 

Switching to new root 

exec of init (/bin/sh) failed!!!: 13 

umount /initrd/dev failed: 13 

kernel panic - not syncing: Attempted to kill init!

It then hangs.

How do I fix this?

Thanks.

Kent, K5KNT

Have you checked the md5 checksum for the ISO image? From the output I'd suggest checking that - if it's fine the reburn the image, if not the redownload the ISO then reburn.

Quote:

Originally posted by brundles
Have you checked the md5 checksum for the ISO image? From the output I'd suggest checking that - if it's fine the reburn the image, if not the redownload the ISO then reburn.

I didn't check the md5 checksum, but I think you may have misunderstood my post. The kernel panic is when I tried to boot my installed Fedora Core 3, not the Zen Linux live CD.

Anyway, the CD is now in my growing pile of "useless" CD's and I have reinstalled Fedora Core 3.

Kent

Sorry about that Kent - you're right, having reread the original post I got the boot up the wrong way around :o

FYI I'm getting this error in Mandriva 2007 also.

I am also having this problem with Fedora 7. I went to the Fedora-specific forum first for help, but received none. I always check my md5sums. I know the CD boots fine. It installed fine. But when booting, I get kernel panic.

If anyone could offer some possible reasons for this, that would be very helpful.

You get kernel panic but for which reason?
It is important to know what is displayed before the kernel panic.
Are you using LVM? Which file system are you using?
Please post more information.

Anyway, you can try to make a new initrd file with the correct setup from the boot CD (try rescue, chroot to your system and run mkinitrd)

This message is misleading, because it implies that the problem you should be focusing upon is here, when in fact the root cause of the problem occurred earlier. The "attempted to kill 'init'" message is actually the last piston that the machine will typically cough-up before it dies ... a death caused by a message that will have occurred sooner.

The actual problem in this case is:

Code:

exec of init (/bin/sh) failed!!!: 13

When the init process (which is "the origin of all things" in a Linux system) was unable to do that, it died. But... the init process is not allowed to "die." The message really should have been:

Code:

Oh, my!  'init' died!  

But 'init' is not allowed to die!  Oh dear... I can't possibly continue.  

All I can think of to do right now is to panic! 

(Koff! Koff! Ka-pooie!  I'm comin', Martha! It's the big one!  Aaack!)

(System halted.)

Have you tried booting into single user mode from a CD and testing the init binary and/or the /bin/sh binary? It may be something like a missing library for example.

Try booting via a CD, mount your Fedora partition and try running the /sbin/init (and also /bin/sh) on that partition to see if it gives any errors - post them here if you get any.

(Just an hunch that's all! :))

Q: is there a way to copy the text that comes up during boot (without having to manually write it)?

Use the dmesg command

I was able to copy the following text from the boot screen:

Code:

Waiting for driver initialization.

Trying to resume from /dev/sdb1

No suspend signature on swap, not resuming.

Creating root device.

Mounting root filesystem.

mount: could not find filesystem '/dev/root'

Setting up other filesystems.

Setting up new root fs

setuproot: moving /dev failed: No such file or directory

no fstab.sys, mounting internal defaults

setuproot: moving /proc failed: No such file or directory

setuproot: moving /sys failed: No such file or directory

Switching to new root and running init.

unmounting old /dev

unmounting old /proc

unmounting old /sys

switchroot: mount failed: No such file or directory

Booting has failed.

Kernel panic - not syncing: Attempted to kill init!

Then the computer freezes, and the keyboard lights blink. Though this is not the exact same path to kernel panic as what k5knt posted, but the common thread appears to be: 'switching to new root', and 'unmount failed'.

Quote:

Code:

Switching to new root 

exec of init (/bin/sh) failed!!!: 13 

umount /initrd/dev failed: 13 

kernel panic - not syncing: Attempted to kill init!

I hope this helps. Thanks too for any help I can get.

f-t

Unfortunately, the problem dates back from before the part of log you provided.
Indeed, "mount: could not find filesystem '/dev/root'" means that linux can not mount the root filesystem, most probably because it was not able to create the dev file, probably because some modules are missing.
Could you please try to post more of the log?

Also please try this :
Boot from CD and select rescue mode at grub screen. Answer questions and do :

Code:

chroot /mnt/sysimage

mkdir /tmp/initrd

cp /boot/initrd* /tmp/initrd

cd /tmp/initrd

gunzip<initrd* | cpio -i -d

cat init

This will display the init script that linux is executing at boot.
near the end of it, you will see something like that :

Code:

echo Creating root device.

mkrootdev -t something -o defaults,ro somewhere

It will be interesting to know what something and somewhere are, so as to know which filesystem it is trying to mount for your root partition and see if the somewhere indeed contains the something file system and if all the modules are insmoded for this file system.

Regards

Edit : note that you can boot your kernel in quiet mode (option quiet) ; it will reduce the output only to errors, so you can actually see them.

Thanks Agrouf. I'll try booting from the CD and checking out the init file. I'll also try Jeiku's suggesiton of:

Quote:

try running the /sbin/init (and also /bin/sh)

I saw your EDIT to boot in quiet mode -- I'll try that. If you need to see more of the boot log, I don't know how to get that. Jeiku suggested the "dmesg" command, but I am not familiar with that, nor how to use/execute it. If someone could explain, that would be great.

Also, I should note that I installed with both the Fedora 7 Live CD, and the Fedora 7 Installation CD, and got kernel panic both times I tried to boot directly after installation. I can't be sure that the errors were the same, but the end result was.

IMHO, /sbin/init won't help you because your system didn't mount the root partition, therefore it didn't access the init file, therefore the problem can't be there.
The program that isn't working is the init in the initrd file.
With all respect, I don't think dmesg can help you either, since the log files are written nowhere (since the partitions are not mounted linux can't access any file, but those in the initrd because it is copied to ram by grub).
If you have a live CD, you can mount your boot partition and check your initrd file.
It is located at /boot ; the command :
gunzip<initrd_file | cpio -i -d
extracts the initrd file.
We just need to know which file system (ext2? ext3? reiserfs?) you are using and on which kind of hardrive it is installed (USB? SATA? LVM? RAID? IDE?)

This is what I got when I copied the initrd file from my Fedora /boot directory on my hard drive:

Code:

[root@localhost initrd]# cat init

#!/bin/nash



mount -t proc /proc /proc

setquiet

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/rtc c 10 135

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

echo Setting up hotplug.

hotplug

echo Creating block device nodes.

mkblkdevs

echo "Loading uhci-hcd.ko module"

insmod /lib/uhci-hcd.ko 

echo "Loading ohci-hcd.ko module"

insmod /lib/ohci-hcd.ko 

echo "Loading ehci-hcd.ko module"

insmod /lib/ehci-hcd.ko 

mount -t usbfs /proc/bus/usb /proc/bus/usb

echo "Loading mbcache.ko module"

insmod /lib/mbcache.ko 

echo "Loading jbd.ko module"

insmod /lib/jbd.ko 

echo "Loading ext3.ko module"

insmod /lib/ext3.ko 

echo "Loading scsi_mod.ko module"

insmod /lib/scsi_mod.ko 

echo "Loading sd_mod.ko module"

insmod /lib/sd_mod.ko 

echo "Loading libata.ko module"

insmod /lib/libata.ko 

echo "Loading ata_generic.ko module"

insmod /lib/ata_generic.ko 

echo "Loading ata_piix.ko module"

insmod /lib/ata_piix.ko 

echo Waiting for driver initialization.

stabilized --hash --interval 250 /proc/scsi/scsi

insmod /lib/scsi_wait_scan.ko

rmmod scsi_wait_scan

mkblkdevs

resume /dev/sdb1

echo Creating root device.

mkrootdev -t ext3 -o defaults,ro sdb5

echo Mounting root filesystem.

mount /sysroot

echo Setting up other filesystems.

setuproot

echo Switching to new root and running init.

switchroot

echo Booting has failed.

sleep -1

I'm using the ext3 filesystem, on an IDE harddrive. No RAID or LVM. I hope that helps you diagnose the problem.

I believe your mkrootdev command is wrong

Code:

mkrootdev -t ext3 -o defaults,ro /dev/sdb5

Try regenerating your initrd file with :

Code:

rootdev=/dev/sdb5 mkinitrd

Check that the mkrootdev command has been correctly generated (gunzip | cpio)
Then edit /boot/grub/menu.lst and use your new initrd file that you have put in /boot

Also check that /dev/sdb5 indeed is an ext3 filesystem.

Code:

su -

mkdir /mnt/test

mount -t ext3 -o defaults,ro /dev/sdb5 /mnt/test

And lastly check in quiet mode that inserting modules ext3 and jbd do not report errors at boot.

Thank you for the help -- I will try these things. Though I'm wondering why I'd have to edit menu.lst to use the 'new' initrd file. Shouldn't the mkinitrd command just overwrite the existing one?

You should give the initrd file to create as argument for mkinitrd.
It won't overwrite unless you specify the -f (force) option.
If you feel like you won't need the old one, go ahead.

When I tried the mkinitrd command this is what I got:

Code:

[root@localhost initrd]# rootdev=/dev/sdb5 mkinitrd

bash: mkinitrd: command not found

I don't have a clue what's wrong here.

btw, I checked, and /dev/hdb5 definitely has the ext3 filesystem

Did you try from a Fedora system (liveCD or rescue CD)?

Yes I did use a Fedora live CD -- I was able to mount my installed partition just fine and view the contents. I copied the initrd-2.6.21-1.3194.fc7.img file to /tmp/initrd -- that's where I ran the "cat init" command to view the contents of the file. It's been a few days now, but I believe I also ran the mkinitrd command in the /tmp/initrd directory (I assumed here that once the new initrd file was created, I could copy it over to the installed partition).

I still don't understand though why it would return "command not found"...

Hi,

I think I might have the same issue as fire-tick. Exept I installed FC7 with lvm.
My system has also 2 SATA drives in raid.

I installed FC7 via the boot CD and via ftp. After installation, the kernel paniced at first reboot. I think the system is stuck on "mkrootdev -t ext3 -o defaults,ro /dev/VolGroup00/LogVol00".

I used the commands Agrouf provided to read into init after starting from the rescue cd.

Code:

chroot /mnt/sysimage

mkdir /tmp/initrd

cp /boot/initrd* /tmp/initrd

cd /tmp/initrd

gunzip<initrd* | cpio -i -d

cat init

I tried:

Code:

[root@localhost initrd]# rootdev=/dev/sdb5 mkinitrd

but did not receive anything back from the prompt. So I supose something happened but I don't know what.

I read somewhere else that you can use mknitrd with options like --with=lvm --with=raid.

So I tried to

Code:

[root@localhost initrd] mkinitrd --force-lvm-probe 

--force-raid-probe --with=lvm --with=raid -f 

initrd-2.6.21-1.3194.fc7 2.6.21-1.3194.fc7

I suppose I did overwrite menu.lst in grub folder. After rebooting I still have the same issue.

Code:

"VolGroup00" was not found

Unable to access resume device (/dev/VolGroup00/LogVol01)

mount: could not find filesystem '/dev/root'

setuproot: moving /dev failed: No such file or directory

etc..

Can somebody tell me if I did something wrong by executing mkinitrd or if there is something else which is not correct?

Quote:

Originally Posted by fire-tick

I still don't understand though why it would return "command not found"...

It means that it doesn't find the command mkinitrd, which should be on your system.
I'm currently on holidays and don't have access to any fedora system, but from memory, it should be in /sbin or in /usr/sbin.
Save your /boot/initrd-2.6.21-1.3194.fc7 somewhere and try this :

Code:

rootdev=/dev/sdb5 /sbin/mkinitrd /boot/initrd-2.6.21-1.3194.fc7 2.6.21-1.3194.fc7

Reboot and try.
If you don't have mkinitrd, copy it from the cd before chroot

Code:

cp /sbin/mkinitrd /mnt/sysimage/sbin

chroot /mnt/sysimage

(if it's not in sbin, it is in /usr/sbin and if it doesn't work in either directory, try "locate mkinitrd" or "find / -name mkinitrd")

Regards

Quote:

Originally Posted by Sanoj21

I installed FC7 via the boot CD and via ftp. After installation, the kernel paniced at first reboot. I think the system is stuck on "mkrootdev -t ext3 -o defaults,ro /dev/VolGroup00/LogVol00".

You probably have a problem with lvm not setup correctly in init

Quote:

Originally Posted by Sanoj21

I used the commands Agrouf provided to read into init after starting from the rescue cd.

Code:

chroot /mnt/sysimage

mkdir /tmp/initrd

cp /boot/initrd* /tmp/initrd

cd /tmp/initrd

gunzip<initrd* | cpio -i -d

cat init

check that your init has a line starting with vgchange

Quote:

Originally Posted by Sanoj21

I tried:

Code:

[root@localhost initrd]# rootdev=/dev/sdb5 mkinitrd

but did not receive anything back from the prompt. So I supose something happened but I don't know what.

mkinitrd doesn't write anything to stdout unless you tell it to or unless there are errors.

Quote:

Originally Posted by Sanoj21

I read somewhere else that you can use mknitrd with options like --with=lvm --with=raid.

So I tried to

Code:

[root@localhost initrd] mkinitrd --force-lvm-probe 

--force-raid-probe --with=lvm --with=raid -f 

initrd-2.6.21-1.3194.fc7 2.6.21-1.3194.fc7

it did create initrd-2.6.21-1.3194.fc7 in /tmp/initrd.
You should copy it to /boot

Quote:

Originally Posted by Sanoj21

I suppose I did overwrite menu.lst in grub folder. After rebooting I still have the same issue.

If you didn't do it explicitely, it didn't edit menu.lst

Quote:

Originally Posted by Sanoj21

Code:

"VolGroup00" was not found

Unable to access resume device (/dev/VolGroup00/LogVol01)

mount: could not find filesystem '/dev/root'

setuproot: moving /dev failed: No such file or directory

etc..

Can somebody tell me if I did something wrong by executing mkinitrd or if there is something else which is not correct?

try to copy mkinitrd to /tmp and edit it
change the line

Code:

vg_list=""

with

Code:

vg_list=VolGroup00

Run this /tmp/mkinitrd with your options.
Check that the new initrd has the correct vgchange (gunzip, cpio, cat init etc)
Copy the generated initrd file to /boot
Edit /boot/grub/menu.lst to use this initrd
Reboot

Good Luck

I know where I screwed up before -- I missed the first part of Agrouf's post that said basically boot into rescue mode. So I booted into rescue mode, and followed all the steps. When I got to the rootdev=/dev/sdb5 mkinitrd part, I stalled for a bit, because i didn't have the right syntax. Then I did:

Code:

rootdev=/dev/sdb5 mkinitrd initrd-2.6.21-1.3195.fc7.img 2.6.21-1.3194.fc7

I changed the filenmae slightly so I wouldn't overwrite the existing one. Then I just got another prompt. I did 'ls' to see if there were 2 initrd files, but there was only one. Did I miss something? Or did it create the file somewhere else?

Agrouf,

I followed your instructions but I still cannot boot Fedora 7 on my system. I copied mkinitrd from /sbin. Updated vg_list which was empty with VolGroup00. I ran mkinitrd with the options previously specified.

The first error I receive is: After Reading all physical volumes. This may take a while..., it takes not even a second. The system says, no volume groups found. "VolumeGroup00" not found.

I shall submit my init, mkinitrd.log and mount info.

Code:

#!/bin/nash



mount -t proc /proc /proc

setquiet

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/rtc c 10 135

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

echo Setting up hotplug.

hotplug

echo Creating block device nodes.

mkblkdevs

echo "Loading uhci-hcd.ko module"

insmod /lib/uhci-hcd.ko 

echo "Loading ohci-hcd.ko module"

insmod /lib/ohci-hcd.ko 

echo "Loading ehci-hcd.ko module"

insmod /lib/ehci-hcd.ko 

mount -t usbfs /proc/bus/usb /proc/bus/usb

echo "Loading mbcache.ko module"

insmod /lib/mbcache.ko 

echo "Loading jbd.ko module"

insmod /lib/jbd.ko 

echo "Loading ext3.ko module"

insmod /lib/ext3.ko 

echo "Loading scsi_mod.ko module"

insmod /lib/scsi_mod.ko 

echo "Loading sd_mod.ko module"

insmod /lib/sd_mod.ko 

echo "Loading libata.ko module"

insmod /lib/libata.ko 

echo "Loading sata_via.ko module"

insmod /lib/sata_via.ko 

echo Waiting for driver initialization.

stabilized --hash --interval 250 /proc/scsi/scsi

echo "Loading pata_via.ko module"

insmod /lib/pata_via.ko 

echo Waiting for driver initialization.

stabilized --hash --interval 250 /proc/scsi/scsi

echo "Loading dm-mod.ko module"

insmod /lib/dm-mod.ko 

echo "Loading dm-mirror.ko module"

insmod /lib/dm-mirror.ko 

echo "Loading dm-zero.ko module"

insmod /lib/dm-zero.ko 

echo "Loading dm-snapshot.ko module"

insmod /lib/dm-snapshot.ko 

echo Making device-mapper control node

mkdmnod

insmod /lib/scsi_wait_scan.ko

rmmod scsi_wait_scan

mkblkdevs

rmparts sdb

rmparts sda

dm create via_cghfdbhccb 0 240121727 mirror core 2 131072 nosync 2 8:0 0 8:16 0

echo Scanning logical volumes

lvm vgscan --ignorelockingfailure

echo Activating logical volumes

lvm vgchange -ay --ignorelockingfailure VolGroup00

resume /dev/VolGroup00/LogVol01

echo Creating root device.

mkrootdev -t ext3 -o defaults,ro /dev/VolGroup00/LogVol00

echo Mounting root filesystem.

mount /sysroot

echo Setting up other filesystems.

setuproot

echo Switching to new root and running init.

switchroot

echo Booting has failed.

sleep -1

mkinitrd log

Code:

Creating initramfs

Looking for deps of module uhci-hcd

Looking for deps of module ohci-hcd

Looking for deps of module ehci-hcd

Looking for deps of module ext3: mbcache jbd 

Looking for deps of module mbcache

Looking for deps of module jbd

Looking for deps of module sata_via: scsi_mod libata 

Looking for deps of module scsi_mod

Looking for deps of module sd_mod: scsi_mod 

Looking for deps of module scsi_wait_scan: scsi_mod 

Looking for deps of module libata: scsi_mod 

Looking for deps of module pata_via: scsi_mod libata 

Looking for deps of module ide-disk

Looking for deps of module dm-mod

Looking for deps of module dm-mirror: dm-mod 

Looking for deps of module dm-zero: dm-mod 

Looking for deps of module dm-snapshot: dm-mod 

Looking for deps of module lvm

Looking for deps of module raid

Using modules:  /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/usb/host/uhci-hcd.ko /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/usb/host/ohci-hcd.ko /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/usb/host/ehci-hcd.ko /lib/modules/2.6.21-1.3194.fc7/kernel/fs/mbcache.ko /lib/modules/2.6.21-1.3194.fc7/kernel/fs/jbd/jbd.ko /lib/modules/2.6.21-1.3194.fc7/kernel/fs/ext3/ext3.ko /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/scsi/scsi_mod.ko /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/scsi/sd_mod.ko /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/ata/libata.ko /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/ata/sata_via.ko /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/ata/pata_via.ko  /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/md/dm-mod.ko /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/md/dm-mirror.ko /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/md/dm-zero.ko /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/md/dm-snapshot.ko  

Building initrd in /tmp/initrd.WH4004

/sbin/nash -> /tmp/initrd.WH4004/bin/nash

  /usr/lib/libnash.so.6.0.9 -> /tmp/initrd.WH4004/usr/lib/libnash.so.6.0.9

  /usr/lib/libbdevid.so.6.0.9 -> /tmp/initrd.WH4004/usr/lib/libbdevid.so.6.0.9

  /lib/libdevmapper.so.1.02 -> /tmp/initrd.WH4004/lib/libdevmapper.so.1.02

  /usr/lib/libparted-1.8.so.6 -> /tmp/initrd.WH4004/usr/lib/libparted-1.8.so.6

    /usr/lib/libparted-1.8.so.6.0.0 -> /tmp/initrd.WH4004/usr/lib/libparted-1.8.so.6.0.0

  /lib/libblkid.so.1 -> /tmp/initrd.WH4004/lib/libblkid.so.1

    /lib/libblkid.so.1.0 -> /tmp/initrd.WH4004/lib/libblkid.so.1.0

  /lib/libselinux.so.1 -> /tmp/initrd.WH4004/lib/libselinux.so.1

  /lib/libsepol.so.1 -> /tmp/initrd.WH4004/lib/libsepol.so.1

  /lib/libuuid.so.1 -> /tmp/initrd.WH4004/lib/libuuid.so.1

    /lib/libuuid.so.1.2 -> /tmp/initrd.WH4004/lib/libuuid.so.1.2

  /usr/lib/libpopt.so.0 -> /tmp/initrd.WH4004/usr/lib/libpopt.so.0

    /usr/lib/libpopt.so.0.0.0 -> /tmp/initrd.WH4004/usr/lib/libpopt.so.0.0.0

  /lib/libresolv.so.2 -> /tmp/initrd.WH4004/lib/libresolv.so.2

    /lib/libresolv-2.6.so -> /tmp/initrd.WH4004/lib/libresolv-2.6.so

      /lib/libc.so.6 -> /tmp/initrd.WH4004/lib/libc.so.6

        /lib/libc-2.6.so -> /tmp/initrd.WH4004/lib/libc-2.6.so

          /lib/ld-lsb.so.3 -> /tmp/initrd.WH4004/lib/ld-lsb.so.3

            /lib/ld-2.6.so -> /tmp/initrd.WH4004/lib/ld-2.6.so

  /lib/libdl.so.2 -> /tmp/initrd.WH4004/lib/libdl.so.2

    /lib/libdl-2.6.so -> /tmp/initrd.WH4004/lib/libdl-2.6.so

  /usr/lib/libdhcp.so.1 -> /tmp/initrd.WH4004/usr/lib/libdhcp.so.1

  /usr/lib/libnl.so.1 -> /tmp/initrd.WH4004/usr/lib/libnl.so.1

    /usr/lib/libnl.so.1.0-pre5 -> /tmp/initrd.WH4004/usr/lib/libnl.so.1.0-pre5

  /usr/lib/libdhcp4client-3.0.5.so.0 -> /tmp/initrd.WH4004/usr/lib/libdhcp4client-3.0.5.so.0

  /usr/lib/libdhcp6client-0.10.so.0 -> /tmp/initrd.WH4004/usr/lib/libdhcp6client-0.10.so.0

  /lib/libglib-2.0.so.0 -> /tmp/initrd.WH4004/lib/libglib-2.0.so.0

    /lib/libglib-2.0.so.0.1200.11 -> /tmp/initrd.WH4004/lib/libglib-2.0.so.0.1200.11

  /lib/libm.so.6 -> /tmp/initrd.WH4004/lib/libm.so.6

    /lib/libm-2.6.so -> /tmp/initrd.WH4004/lib/libm-2.6.so

  /lib/libcrypto.so.6 -> /tmp/initrd.WH4004/lib/libcrypto.so.6

    /lib/libcrypto.so.0.9.8b -> /tmp/initrd.WH4004/lib/libcrypto.so.0.9.8b

  /lib/libz.so.1 -> /tmp/initrd.WH4004/lib/libz.so.1

    /lib/libz.so.1.2.3 -> /tmp/initrd.WH4004/lib/libz.so.1.2.3

/sbin/insmod -> /tmp/initrd.WH4004/bin/insmod

/sbin/rmmod -> /tmp/initrd.WH4004/bin/rmmod

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/usb/host/uhci-hcd.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/uhci-hcd.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/usb/host/ohci-hcd.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/ohci-hcd.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/usb/host/ehci-hcd.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/ehci-hcd.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/fs/mbcache.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/mbcache.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/fs/jbd/jbd.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/jbd.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/fs/ext3/ext3.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/ext3.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/scsi/scsi_mod.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/scsi_mod.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/scsi/sd_mod.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/sd_mod.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/ata/libata.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/libata.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/ata/sata_via.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/sata_via.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/ata/pata_via.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/pata_via.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/md/dm-mod.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/dm-mod.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/md/dm-mirror.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/dm-mirror.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/md/dm-zero.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/dm-zero.ko' [elf32-i386]

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/md/dm-snapshot.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/dm-snapshot.ko' [elf32-i386]

/sbin/lvm -> /tmp/initrd.WH4004/bin/lvm

  /sbin/lvm.static -> /tmp/initrd.WH4004/sbin/lvm.static

/etc/lvm -> /tmp/initrd.WH4004/etc/lvm

`/etc/lvm/lvm.conf' -> `/tmp/initrd.WH4004/etc/lvm/lvm.conf'

Adding module scsi_wait_scan

copy from `/lib/modules/2.6.21-1.3194.fc7/kernel/drivers/scsi/scsi_wait_scan.ko' [elf32-i386] to `/tmp/initrd.WH4004/lib/scsi_wait_scan.ko' [elf32-i386]

Adding module uhci-hcd

Adding module ohci-hcd

Adding module ehci-hcd

Adding module mbcache

Adding module jbd

Adding module ext3

Adding module scsi_mod

Adding module sd_mod

Adding module libata

Adding module sata_via

Adding module pata_via

Adding module dm-mod

Adding module dm-mirror

Adding module dm-zero

Adding module dm-snapshot

Adding dm map "via_cghfdbhccb"

This initrd uses dynamic shared objects.

Adding dynamic linker configuration files.

/etc/ld.so.conf -> /tmp/initrd.WH4004/etc/ld.so.conf

Running ldconfig

I did also run cat /proc/mounts

Code:

rootfs / rootfs rw 0 0

/proc /proc proc rw 0 0

/dev /dev tmpfs rw 0 0

/dev/pts /dev/pts devpts rw 0 0

/sys /sys sysfs rw 0 0

none /tmp ramfs rw 0 0

none /tmp/ramfs ramfs rw 0 0

/proc/bus/usb /proc/bus/usb usbfs rw 0 0

/tmp/loop0 /mnt/runtime squashfs ro 0 0

/selinux /selinux selinuxfs rw 0 0

/dev/VolGroup00/LogVol00 /mnt/sysimage ext3 rw,data=ordered 0 0

/dev/mapper/via_cghfdbhccbp3 /mnt/sysimage/boot ext3 rw,data=ordered 0 0

/tmp/sysfs /mnt/sysimage/sys sysfs rw 0 0

/tmp/proc /mnt/sysimage/proc proc rw 0 0

/dev /mnt/sysimage/dev tmpfs rw 0 0

/selinux /mnt/sysimage/selinux selinuxfs rw 0 0

The new file I created was already in the /boot folder. I ran the dpkg and cat init command to check if the changes had been made, and indeed...

Code:

mkrootdev -t ext3 -o defaults,ro sdb5

had changed to:

Code:

mkrootdev -t ext3 -o defaults,ro /dev/sdb5

But, when I edited menu.lst to use the new initrd file, and re-booted, I still got kernel panic -- in fact, [what appears to be] the exact same series of errors to produce the kernel panic.

I think I'm going to re-install Mandriva for now.

Thanks anyway to everyone for their help. I'll keep an eye on this thread to see if a resolution is reached.

<EDIT: so as to not be a quitter, I'll stick it out w/ Fedora for a while. I really appreciate the fact that there is a community of folks that are willing and able to provide support>

Quote:

Originally Posted by fire-tick

The new file I created was already in the /boot folder. I ran the dpkg and cat init command to check if the changes had been made, and indeed...

Code:

mkrootdev -t ext3 -o defaults,ro sdb5

had changed to:

Code:

mkrootdev -t ext3 -o defaults,ro /dev/sdb5

Mandriva is a good distro.
I may have had guessed wrong, the problem isn't rootdev then.
If you decide to persist with Fedora, please post the first error that is displayed at boot and some errors after this one if possible.
If you decide to give up for the moment, that is understandable, you can always come back here later and I'll be happy to help if I can.

Quote:

Originally Posted by Sanoj21

What is the output of "pvdisplay" please?

Agrouf,

I haven't tried booting in quiet mode yet -- I SuSE's GRUB to boot Elive and Fedora. What do I add to menu.lst to tell it to boot Fedora in quiet mode?

the output of my pvdisplay:

Code:

  --- Physical volume ---

  PV Name              /dev/mapper/via_cghfdbhccbp4

  VG Name              VolGroup00

  PV Size              36.27 GB / not usable 22.47 MB

  Allocatable          yes 

  PE Size (KByte)      32768

  Total PE              1160

  Free PE              1

  Allocated PE          1159

  PV UUID              82QhnT-97OD-0WTL-Bf77-Jlu1-jg6z-TuoE66

Quote:

Originally Posted by fire-tick

Agrouf,

I haven't tried booting in quiet mode yet -- I SuSE's GRUB to boot Elive and Fedora. What do I add to menu.lst to tell it to boot Fedora in quiet mode?

You have to add quiet at the end of the kernel line.
example :

Code:

kernel /boot/vmlinuz root=LABEL=ROOT quiet

Regards

Quote:

Originally Posted by Sanoj21

the output of my pvdisplay:

Code:

  --- Physical volume ---

  PV Name              /dev/mapper/via_cghfdbhccbp4

  VG Name              VolGroup00

  PV Size              36.27 GB / not usable 22.47 MB

  Allocatable          yes 

  PE Size (KByte)      32768

  Total PE              1160

  Free PE              1

  Allocated PE          1159

  PV UUID              82QhnT-97OD-0WTL-Bf77-Jlu1-jg6z-TuoE66

Is this software or hardware raid?
Does /proc/mdstats exist?
What is the output of dmraid -s?
What is the output of

Code:

echo dm list | nash

Agrouf,

I booted in quiet mode, and I copied down the entire boot output:

Code:

root (hd1,4)

  Filesystemtype is ext2fs, partition type 0x83

kernel /boot/vmlinuz-2.6.21-1.3194.fc7 root=/dev/hdb5 quiet

  [Linux-bxImage, setup=0x1e00, size=0x1c9dd4]

initrd /boot/initrd-2.6.21-1.3195.fc7.img

  [Linux-initrd @ 0x1fd3100, 0x2be794 bytes]



Uncompressing Linux... Ok, booting kernel.

Red Hat nash version 6.0.9 starting

usb 2-2: device descriptor read/all, error -71

mount: could not find filesystem 'dev/root'

setuproot: moving /dev failed: No such file or directory

setuproot: error mounting /proc: No such file or directory

setuproot: error mounting /sys: No such file or directory

switchroot: mount failed: No such file or directory

Kernel panic - not syncing: Attempted to kill init!

I highlighted the 5 in the initrd filename as a reminder -- that's the new one I created.

What can you make of this output?

Quote:

Originally Posted by fire-tick

kernel /boot/vmlinuz-2.6.21-1.3194.fc7 root=/dev/hdb5 quiet

try /dev/sdb5 in menu.lst :

Code:

kernel /boot/vmlinuz-2.6.21-1.3194.fc7 root=/dev/sdb5 quiet

Is this software or hardware raid?

Code:

It's hardware raid. These are my BIOS settings.



Serial ATA RAID BIOS Setting Utility V2.01 

Serial_Ch0 Master: Array 0 - Raid 1 

Serial_Ch1 Master: Array 0 - Raid 1 

VIA PT800 North Controller, Rev C2 

VIA PT8237 South Controller, Rev A2

Does /proc/mdstats exists?

Code:

No but proc/mdstat exists, I suppose you ment this.



Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 

unused devices: <none>

What is the output of dmraid -s

Code:

*** Active Set

name  : via_cghfdbhccb

size  : 240121720

stride : 8

type  : mirror

status : ok

subsets: 0

devs  : 2

spares : 0

What is the ouput of echo dm list | nash

Code:

(running in test mode).

Red Hat nash version 6.0.9 starting

rmparts sdb

rmparts sda

create via_cghfdbhccb

create via_cghfdbhccbp4

create VolGroup00-LogVol01

part VolGroup00-LogVol01

create VolGroup00-LogVol00

part VolGroup00-LogVol00

create via_cghfdbhccbp3

part via_cghfdbhccbp3

create via_cghfdbhccbp5

create via_cghfdbhccbp2

create via_cghfdbhccbp1

I changed /dev/hdb5 to /dev/sdb5, and Fedora booted up just fine [I'm writing this from Fedora] -- Thanks Agrouf for pointing that out!! I think I had tried that earlier, before I created the new initrd file, so I forgot all about that one...

I'm glad I stuck with it a bit longer. I knew Mandriva worked, but I really wanted to give Fedora a try. I liked what I saw with the live CD.

Congrats fire-tick, I'm glad for you. Have a happy fedora experience.

Sanoj21,

I suspect /dev/mapper/via_cghfdbhccbp4 is not generated and therefore vgscan doesn't find your pv.
I suggest adding the line "find /dev/mapper" after dm create and just before the vgscan in init
You can also try regenerating devs with mkblkdevs before vgscan.

Extract your initrd with the usual gunzip|cpio to /tmp/initrd, edit init and then you can regenerate initrd with

Code:

rm /tmp/initrd/initrd*

findall() { echo nash-find  | /sbin/nash --force --quiet; }

(cd /tmp/initrd; findall . | cpio -H newc --quiet -o) >| /boot/tmp.img

gzip -9 </boot/tmp.img >/boot/initrd.img

rm /boot/tmp.img

Adapt your menu.lst to use initrd.img and please tell me if /dev/mapper/via_cghfdbhccbp4 exist.
(boot in verbose mode to see the result of find)

You probably need some raid drivers from via?
check "lsmod | grep via" and "lsmod | grep raid"

Had similar problem. Try checking and/or editing the /etc/ftab file. Also the grub configuration file. What might have happened is that the attempt to run Zen from the CD has altered the partion info. Did it install a swap partion or file?