Fc2 Vfs kernel panic after upgrade from Fc1 using Volume Management

Peter Smith peter.smith at utsouthwestern.edu
Fri May 21 19:34:30 UTC 2004


Thank you for the reply!  I did some searching for lvm & fedora core and 
did find similar issues with the upgrade of FC1->FC2t3 ..  I upgraded 
from CDROM and Anaconda.  However I have some interesting news.  If I 
install a clean FC2 with / and swap on LVM I get the same Vfs panic.  I 
think this may be more basic and illustrate the problem better.

Here is the anaconda-ks.cfg ...

# Kickstart file automatically generated by anaconda.
install
cdrom
lang en_US.UTF-8
langsupport --default en_US.UTF-8 en_US.UTF-8
keyboard us
xconfig --card "VMWare" --videoram 16384 --hsync 31.5-35.1 --vsync 50-61 
--resolution 800x600 --depth 16
network --device eth0 --bootproto dhcp
#rootpw --iscrypted
firewall --enabled --port=ssh:tcp
selinux --disabled
authconfig --enableshadow --enablemd5
timezone --utc America/Chicago
bootloader --location=mbr
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
#clearpart --all
#part /boot --fstype ext3 --size=100 --asprimary
#part pv.7 --size=100 --grow --asprimary
#volgroup Volume00 pv.7
#logvol swap --fstype swap --name=LogVol00 --vgname=Volume00 --size=256
#logvol / --fstype ext3 --name=LogVol01 --vgname=Volume00 --size=3728
%packages
@ dialup
@ admin-tools
@ server-cfg
@ text-internet
kernel-smp
grub
lvm2
e2fsprogs
%post

After installing the kernel will boot and be unable to mount the root fs..

Peter


Alexandre Oliva wrote:

>On May 20, 2004, Peter Smith <peter.smith at utsouthwestern.edu> wrote:
>
>  
>
>>Originally I had installed Fc1 and opted for the Volume Management
>>arrangement.  The default was to setup root (/) as
>>/dev/Volume00/LogVol01 .  After upgrading to Fc2,
>>    
>>
>
>How did you upgrade?  Anaconda, or up2date, yum or something else that
>couldn't possibly have fixed things up?
>
>I don't know whether Anaconda does anything to fix LVM upgrades, but I
>vaguely remember some note about this not working in FC2 test releases
>Release Notes, and I can't find it in the FC2 final release notes, so
>I assume it should work.
>
>Anyhow, if it doesn't, or if you chose one of the other upgrade paths,
>the way to fix it is to remove the LVM1 device nodes from the VG
>directories.  After that, a reboot should fix things up.  If it
>doesn't, run as root, after entering the password when the system
>fails to boot up:
>
>mount -o remount,rw /
>echo mkdmnod | nash
>vgscan
>vgchange -ay
>vgmknodes
>
>this was required in early FC2 test releases, when initrd attempted to
>use device nodes from the root filesystem, instead of from initrd.
>I don't think this should still be necessary, but if everything else
>fails, it's worth a shot.
>
>
>After setting things up, you may want to re-create initrd, just in
>case.
>
>  
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20040521/9619fdc0/attachment-0001.sig>


More information about the fedora-list mailing list