[SOLVED] How to get more space on /boot

[CrazyCaver]

I am trying to upgrade my laptop from 32-bit Fedora 15 to 32-bit Fedora 16. I tried preupgrade, but it came up with a message that /boot did not have enough space. I went to a DVD installer, but get the same message. This same problem happened on one of my VirtualBox VMs, and I wound up totally trashing the VM and still not getting it to work.

I have removed all kernels except one. On the VM I even removed that one, and it still would not work. The VM is now unbootable - totally lost.

I am not going to make the laptop unbootable. The VM is a crash-test dummy which I can (and often do) totally trash out. The laptop is a working computer which would take days to rebuild from scratch.

The /boot partition has 194 meg of space, of which about 28 meg is used. The DVD installer says I need 3 meg more space.

What can I delete in /boot that will NOT render the computer unbootable?

Thanks - Bill Gee

[leigh123linux]

Run this, it should give you at least 4Mb

su
dracut -v -f -H  /boot/initramfs-$(uname -r).img $(uname -r)

[CrazyCaver]

Hi Leigh -

Thanks, that worked nicely.

Now I have a new problem ... After completing the F16 upgrade from DVD, the system will not run "yum update". It gets through all the package downloads (over 900 meg!!!), then fails when running the transaction check. There are many, many lines of errors. Here are the first few:

ERROR with transaction check vs depsolve:
libmtp = 1.0.6-5.fc15 is needed by (installed) libmtp-hal-1.0.6-5.fc15.i686
Please report this error in http://yum.baseurl.org/report
**Found 51 pre-existing rpmdb problem(s), 'yum check' output follows:
GConf2-gtk-2.32.3-1.fc15.i686 has missing requires of GConf2 = ('0', 2.32.3', '1.fc15')

This goes on for several screens.

Now what? I tried "package-cleanup --orphans", but that did not change anything.

Thanks - Bill Gee

[Skull One]

The procedure is written here:
http://fedoraproject.org/wiki/Upgrad...dora_using_yum

You need to do:

yum update yum
yum clean all
yum --releasever=16 --disableplugin=presto distro-sync

[CrazyCaver]

Hi Skull One -

Hmmm ... I ran the first command "yum update yum" and got a reply "No packages marked for Update." I think this means yum is already up to date.

Reviewing the link you posted, I think it does not apply to me. The link describes how to do a version upgrade with yum. In my case the version upgrade is already done ... It's too late to do it with yum. What I need to do is bring the *current* version up to date.

Am I missing something else in your reply?

Thanks - Bill Gee

[leigh123linux]

Originally Posted by CrazyCaver

Hi Skull One -

Hmmm ... I ran the first command "yum update yum" and got a reply "No packages marked for Update." I think this means yum is already up to date.

Reviewing the link you posted, I think it does not apply to me. The link describes how to do a version upgrade with yum. In my case the version upgrade is already done ... It's too late to do it with yum. What I need to do is bring the *current* version up to date.

Am I missing something else in your reply?

Thanks - Bill Gee

dist-sync may clear the package errors

[Skull One]

Originally Posted by CrazyCaver

Hi Skull One -

Hmmm ... I ran the first command "yum update yum" and got a reply "No packages marked for Update." I think this means yum is already up to date.

Reviewing the link you posted, I think it does not apply to me. The link describes how to do a version upgrade with yum. In my case the version upgrade is already done ... It's too late to do it with yum. What I need to do is bring the *current* version up to date.

Am I missing something else in your reply?

Thanks - Bill Gee

Sorry for that, you are in a case similar to 'using preupgrade'.

The commands are standard after an upgrade:
- be sure to have the latest yum;
- clean all the cache;
- sync the packages to the distribution. You could just use 'yum --disableplugin=presto distro-sync'.

As Leigh said, this will solve the errors.

[CrazyCaver]

Hi Leigh and SkullOne -

That did not work. I ran the yum commands you gave and the system downloaded a complete new set of packages. However, it failed at the same point with the same error.

Just for grins, I tried "yum remove libmtp". It wants to remove amarok and rythmbox for dependencies. Those are not big deals for me. I did not go ahead with the removal because I am not sure it will fix the other 51 dependency errors.

Any idea what I should try next?

Thanks - Bill Gee

[leigh123linux]

Originally Posted by CrazyCaver

Hi Leigh and SkullOne -

That did not work. I ran the yum commands you gave and the system downloaded a complete new set of packages. However, it failed at the same point with the same error.

Just for grins, I tried "yum remove libmtp". It wants to remove amarok and rythmbox for dependencies. Those are not big deals for me. I did not go ahead with the removal because I am not sure it will fix the other 51 dependency errors.

Any idea what I should try next?

Thanks - Bill Gee

Post the complete error output.

[Skull One]

Try adding '--skip-broken' for a first update, and '--obsoletes' for a second one.

[CrazyCaver]

OK, you asked for it ... Here is the complete yum transaction. The command line for this was:

yum --releasever=16 --disableplugin=presto distro-sync --skip-broken

Due to size - over 130K - I am trying this as an attached file rather than inline text.

Bill Gee

[leigh123linux]

Can you post

yum --releasever=16 update *\boost\*

[CrazyCaver]

Hi Leigh -

No joy ... Yum installed 18 packages updating various boost components. After that I tried the regular yum update again, and it gave the same errors I have already posted.

Thanks - Bill Gee

[leigh123linux]

Originally Posted by CrazyCaver

Hi Leigh -

No joy ... Yum installed 18 packages updating various boost components. After that I tried the regular yum update again, and it gave the same errors I have already posted.

Thanks - Bill Gee

You need to post the output for this command each time.

yum --releasever=16 --disableplugin=presto distro-sync

[CrazyCaver]

Umm..... OK - but it did not change.

Bill Gee

---------- Post added at 09:40 AM ---------- Previous post was at 09:38 AM ----------

Oops, missed the attached file.

Dammit, won't let me attach the file! I get a message that I have already uploaded it.