Error while upgrading from F11 to F13

[lester81]

Hello to everyone!

I want to upgrade my 32bit Fedora from 11 to 13 version. I tried both options: via preupgrade tool and via installation media (DVD). Both options failed with following Anaconda error at the beginning of installation process:

RpmUtilsError: RPM Error opening Package

In my case, the problem was in package:

/mnt/sysimage/var/cache/yum/anaconda-InstallationRepo-xxx.i386/packages/fontpackages-filesystem-1.44-1.fc13.noarch.rpm.

I switched to terminal, and discovered that size of this file is 0.

I downloaded installation DVD from official torrent, so checksum was autmatically checked. Verification test at the beginnig of installation was also successfully passed. So media is OK. Moreover, I also tried to upgrade via preupgrade tool with the same results.

I found similar bug with unclear status in Fedora Bug Tracking system for Anaconda in F12:
https://bugzilla.redhat.com/show_bug.cgi?id=540571

Could someone describe me possible reason of such error?

Many thanks!

[JEO]

Maybe your filesystem containing /var is out of inodes or out of space? That could cause an rpm to be 0 length.

[lester81]

Originally Posted by JEO

Maybe your filesystem containing /var is out of inodes or out of space? That could cause an rpm to be 0 length.

JEO,

Thanks for reply.

I thought that when I install from DVD, all these packages are located on media, so out of space shouldn't be a problem...

I should say that I had problem with space on /boot partition (it is 100Mb - it was default size in lagacy Fedora installation). I cleared space on /boot as much as I could, now it's ~50% free. It was the first problem with upgrade, but now it seems it's gone. But at the moment I'm facing with problem, described above...

[JEO]

I know that the packages are located on the DVD media. They get copied to your target harddisk and installed. If your target harddisk is full or has some filesystem problem you could end up with 0 length file(s).

[lester81]

Originally Posted by JEO

I know that the packages are located on the DVD media. They get copied to your target harddisk and installed. If your target harddisk is full or has some filesystem problem you could end up with 0 length file(s).

Understod.

So there is no way to upgrade to F13 in case /boot partition has only 100 Mb ?

[JEO]

I think the 100MB /boot only would affect the preupgrade method not the DVD upgrade. Anyway, the area you should check is the volume that contains /var/cache on your harddisk, since that is the location of the 0 length rpm file. Sometimes that would be your root / partition or sometimes you might have created a separate /var partition. Boot from a livecd or install media in rescue mode and do an fsck.ext4 (or ext3) filesystem check on it when it is not mounted. Also check it for free space, and you can use the dumpe2fs -h command to look at other statistics like free inodes.

[lester81]

Originally Posted by JEO

I think the 100MB /boot only would affect the preupgrade method not the DVD upgrade. Anyway, the area you should check is the volume that contains /var/cache on your harddisk, since that is the location of the 0 length rpm file. Sometimes that would be your root / partition or sometimes you might have created a separate /var partition. Boot from a livecd or install media in rescue mode and do an fsck.ext4 (or ext3) filesystem check on it when it is not mounted. Also check it for free space, and you can use the dumpe2fs -h command to look at other statistics like free inodes.

I checked space on my disk. I have three partitions:

1. /boot 98.7Mb, 45.6 Mb free, 53.8% is used;
2. / 37.8 Gb, 26.2 Gb free, 30.8% is used - /var/cache is on this partition;
3. /home 37.8 Gb, 10.1 Gb free, 73.2% is used;

2 and 3 each have own LogicalVolumeGroup.

I definitly think that this problem (rpm has size 0) relates to /var/cache on media (I was checking this folder on DVD via terminal during the installation). But I can't understand why it is reproduced for upgrade via preupgrade option at the same time...

[JEO]

When you are checking out the error, can you post the output of

cat /proc/mounts

Maybe that will help narrow down what is mounted at /mnt/sysimage/var/cache

[lester81]

Originally Posted by JEO

When you are checking out the error, can you post the output of

cat /proc/mounts

Maybe that will help narrow down what is mounted at /mnt/sysimage/var/cache

JEO,

Sorry for the late answer.

Below is the output of cat /proc/mounts:

rootfs / rootfs rw,relatime 0 0
/proc /proc proc rw,relatime 0 0
/dev /dev tmpfs rw,seclabel,relatime 0 0
/dev/pts /dev/pts devpts rw,seclabel,relatime,gid=5,mode=620,ptmxmode=000 0 0
/sys /sys sysfs rw,seclabel,relatime 0 0
none /tmp tmpfs rw,seclabel,relatime,size=256000k 0 0
/dev/loop0 /mnt/runtime squashfs ro,relatime 0 0
/selinux /selinux selinuxfs rw,relatime 0 0
/dev/mapper/VolGroup00-LogVol00 /mnt/sysimage ext3 rw,seclabel,relatime,errors=continue,user_xattr,acl,data=ordered 0 0
/dev/sdb1 /mnt/sysimage/boot ext3 rw,seclabel,relatime,errors=continue,user_xattr,acl,data=ordered 0 0
/dev /mnt/sysimage/dev tmpfs rw,seclabel,relatime 0 0
/dev/devpts /mnt/sysimage/dev/pts devpts rw,seclabel,relatime,gid=5,mode=620,ptmxmode=000 0 0
/dev/tmpfs /mnt/sysimage/dev/shm tmpfs rw,seclabel,relatime 0 0
/dev/mapper/VolGroup00-LogVol01 /mnt/sysimage/home ext3 rw,seclabel,relatime,errors=continue,user_xattr,acl,data=ordered 0 0
/dev/proc /mnt/sysimage/proc proc rw,relatime 0 0
/dev/sysfs /mnt/sysimage/sys sysfs rw,seclabel,relatime 0 0
/dev/sr0 /mnt/source iso9660 ro,relatime 0 0
/selinux /mnt/sysimage/selinux selinuxfs rw,relatime 0 0
/proc/bus/usb /mnt/sysimage/proc/bus/usb usbfs rw,relatime 0 0

---------- Post added at 02:24 PM CDT ---------- Previous post was at 02:17 PM CDT ----------

And here is the log from Anaconda (full log is also attached):

anaconda 13.42 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.6/site-packages/rpmUtils/miscutils.py", line 414, in hdrFromPackage
    raise rpmUtils.RpmUtilsError, "RPM Error opening Package"
  File "/usr/lib/python2.6/site-packages/yum/packages.py", line 732, in returnHeaderFromPackage
    hdr = rpmUtils.miscutils.hdrFromPackage(ts, rpmfile)
  File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 208, in populateTs
    hdr = txmbr.po.returnHeaderFromPackage()
  File "/usr/lib/anaconda/yuminstall.py", line 915, in run
    self.populateTs(keepold=0)
  File "/usr/lib/anaconda/yuminstall.py", line 1703, in doInstall
    rc = self.ayum.run(self.instLog, cb, anaconda.intf, anaconda.id)
  File "/usr/lib/anaconda/backend.py", line 299, in doInstall
    return anaconda.backend.doInstall(anaconda)
  File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
    self.moveStep()
  File "/usr/lib/anaconda/gui.py", line 1313, in nextClicked
    self.anaconda.dispatch.gotoNext()
  File "/usr/lib/anaconda/iw/progress_gui.py", line 79, in renderCallback
    self.intf.icw.nextClicked()
  File "/usr/lib/anaconda/gui.py", line 1334, in handleRenderCallback
    self.currentWindow.renderCallback()
RpmUtilsError: RPM Error opening Package

Local variables in innermost frame:
package: /mnt/sysimage/var/cache/yum/anaconda-InstallationRepo-201005130056.i386/packages/fontpackages-filesystem-1.44-1.fc13.noarch.rpm
e: error reading package header
ts: <rpmUtils.transaction.TransactionWrapper instance at 0xb18090ec>
fdno: 29

[JEO]

"/dev/mapper/VolGroup00-LogVol00 /mnt/sysimage ext3 rw,seclabel,relatime,errors=continue,user_xattr,ac l,data=ordered 0 0"

The above lvm volume is where /mnt/sysimage/var/cache is located. Anyway what I would recommend is doing a filesystem check on it (when booted from a livecd or rescue environment, when the volume is *not* mounted).

# umount /dev/mapper/VolGroup00-LogVol00
# fsck.ext3 -f /dev/mapper/VolGroup00-LogVol00

[BenderRodriguez]

Last time i read someone recommended upgrading to F12 first and then to F13.