Re: fc6xen kernel panic after yum update

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Has anyone else had this problem?  I can't be the only one who had
updated to this version.  If you have updated and things are working
fine, I'd like to know.  That way at least I'll know it is something
on my end.

Thanks,
Tauren


On 5/14/07, Tauren Mills <tauren@xxxxxxxxxxx> wrote:
Hello,

I used yum update on a newly installed dual cpu i386 FC6 system a
couple days ago. My system was updated from Fedora Core
2.6.18-1.2798.fc6xen to 2.6.20-1.2948.fc6xen. The update went fine.
After reboot, I got the following kernel panic:

Scanning logical volumes
  Reading all physical volumes. This may take a while...
  No volume groups found
Activating logical volumnes
  Volume group "vg0" not found
Creating root device.
Mounting root filesystem.
mount: could not fine 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: error mounting /proc failed: No such file or directory
setuproot: error mounting /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
Kernel panic - not syncing: Attempted to kill init!

If I'd boot into the original kernel, it booted just fine.

So, today I took a spare system and installed FC6 fresh from
installation disks. The very first thing I did after the installation
was completed was do a yum update. After reboot, the exact same
problem. Both systems don't work with the latest XEN kernel.

For reference, the only packages installed from the graphical
installer were these:

Applications/Editors:
        vim-enhanced

Applications/Text-based Internet:
        lynx

Base System/Base:
        finger
        gnupg
        man-pages
        mdadm
        mlocate
        nfs-utils
        openssh-clients
        oopenssh-server
        rsync
        sudo
        telnet
        wget
        which
        yum
Base System/Virtualization:
        virt-manager

Since the errors indicate LVM problems, here's info about my disk
layout. I'm configured using two 72GB scsi disks using raid1, then lvm
on top. Disk partitioning:

/dev/sda (72GB)
        /dev/sda1 (102MB)
        /dev/sda2 (69.9GB)
/dev/sdb (72GB)
        /dev/sdb1 (102MB)
        /dev/sdb2 (69.9GB)

/dev/sda1 & /dev/sdb1 are mirrored to /dev/md0
        used by /boot partition (102MB)

/dev/sda2 & /dev/sdb2 are mirrored to physical volume /dev/md1
        used in VolGroup00

/dev/md1 is LVM VolGroup00 and contains these logical volumes
        /dev/VolGroup00/lvdom0 (root)           3GB
        /dev/VolGroup00/lvswap0 (swap)          4GB

The rest of the space was left empty for xen guest partitions.

I've edited grub.conf to use /dev/mapper vs /dev/VolGroup00, but
nothing has booted with the new kernel.

Is there a problem with the new kernel? Where should I go for a
solution? Should I just run the old kernel for now? If I'm not in the
best forum for this, where should I go for help?

Any help would be appreciated!

Thanks!


--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen

[Index of Archives]     [Fedora General]     [Fedora Music]     [Linux Kernel]     [Fedora Desktop]     [Fedora Directory]     [PAM]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux