Description of problem: I booted the F14 DVD to upgrade my f13 system. The installer does not present 'upgrade existing system as an option. If I forge ahead and select a custom install, my volume group is displayed, but without any of my existing logical volumes. Similarily, booting into rescue mode also insists that I don't have any existing linux partitions. Version-Release number of selected component (if applicable): whatever is on the F14 DVD How reproducible: Every time. DVD, netboot.iso, pxeboot. all fail. Steps to Reproduce: 1. boot DVD 2. select 'custom install' 3. review disks Actual results: volume group with no logical volumes Expected results: volume group with logical volumes. install offers 'upgrade system' Additional info: switching over to vt-2, if I run lvm and then lvscan, it shows all my volumes, but as 'inactive'. If I activate them, go back from the storage screen and re-enter, they are not shown and back in vt-2 the lvm lvscan shows them inactive again. on vt-3, I see (vg name is 'j'): INFO storage: adding dm-* to singlepath_disks .... INFO storage: devices to scan: ['dm-14', ..., 'sda2', 'sda1'] WARN storage: invalid data for sda2: 'LVM2_LV_NAME' WARN storage: ignoring dm device 'j-f13root' WARN storage: ignoring dm device 'j-f13var' WARN storage: ignoring dm device 'j-f13swap'
Seems like anaconda problem...
Please attach the logs from /tmp/*log to this bug. Grab them after you get to the partitioning screen. Also, what is in /etc/redhat-release?
redhat release doesn't seem to exist in /etc/ or /mnt/runtime/etc when in anaconda. as for the exising f13 system, it's "Fedora release 13 (Goddard)". attachments of /tmp/log from booting DVD and netbooting to rescue mode coming up.
Created attachment 495794 [details] tarball of /tmp from anaconda via DVD
Created attachment 495795 [details] tarball of /tmp from netboot rescue mode
you can see in the anaconda storage log that it couldn't find the logical volumes in my vg 'j'.. I tried backing out of the storage screen, switching to vt-2, renaming my vg from 'j' to 'VolGroup', and going back to the storage screen... the storage log shows that it then found all my logical volumes, but they still didn't show up on the storage screen.. it showed VolGroup as empty...
Would you mind attaching the individual files? tarballs make it harder to read the logs. Thanks!
Created attachment 496620 [details] anaconda.log attaching individual files, as requested
Created attachment 496621 [details] syslog attaching individual files, as requested
Created attachment 496622 [details] storage.log attaching individual files, as requested
Created attachment 496623 [details] pogram.log attaching individual files, as requested
dupe, based on the 'ERR udevd-work: ressize 4096 too short' error in the syslog. *** This bug has been marked as a duplicate of bug 652318 ***