[CALUG] Fedora upgrade unsuccessful

[Joe]

I just did everything in your suggestion and it still gave me that error msg 
at the end:

- I ran the fsck a couple of times and nothing fishy occurred at all.
- I still got the image too large for /boot error after deleting my old 
kernel and its associated files.  After I rebooted and the bootloader 
configured my NIC, it showed a progress bar for loading /install.img - I 
thought maybe it was loading that file into /boot at that moment.

This is what my filesystems look like if it helps at all:

[jtseng at server0 ~]$ df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/vg_server0-lv_root
                      70718880   6393544  60732940  10% /
tmpfs                  1996752         0   1996752   0% /dev/shm
/dev/sda1               198337     59035    129062  32% /boot
/dev/sdb1            480720592 195744272 260557044  43% /var/hda

Maybe the act of loading install.img somehow "corrupted" /boot....  Any 
other suggestions or do I have to fall back to using a DVD?

-----Original Message----- 
From: Bryan J Smith
Sent: Thursday, June 09, 2011 8:15 AM
To: Joe ; calug at unknownlamer.org
Subject: Re: [CALUG] Fedora upgrade unsuccessful

First off, the CLI Preupgrade (preupgrade-cli) is new.  I already ran into 
one
person using it that had no problem when the ran the GUI Preupgrade
(preupgrade).  So ssh -X into the box and launch the GUI version if at all
possible.

NOTE:  Preupgrade is much better than straight media.  _Both_ use the 
Anaconda
system (far more intelligence than YUM-RPM alone).  But Preupgrade does all
pre-dependency calculation and downloads _exactly_ what you need, including 
from
all 3rd party software repos, to the hard drive (fast and no chance of media
errors).  With the media, you're stuck with what's included in the media, 
and
it's slower (let alone optical drives have much higher error rates than the 
hard
drive).

Secondly, try remounting /boot read-only on the live system, and re-fsck:
  # mount -o remount,ro /dev/sda1 /boot
  # fsck -n /dev/sda1  (try a dry run first)

I'm still wondering why it didn't fsck during boot, unless you meant you 
booted
into the Anaconda upgrader instead of the existing distro/kernel.

Lastly, if you're /boot isn't large enough, try removing older kernels that 
you
are no longer booting.  That should solve the problem.

-- Bryan

P.S.  I'm still wondering why Amahi hasn't just moved to Red Hat Enterprise
Linux (EL) and its "rebuilds," instead of Fedora.  Fedora moves 
way-too-fast,
and the ABI/API can change regularly.  With EL, you never upgrade, just 
update,
plus there are the "EL rebuild" options (e.g., CentOS).  They could be 
releasing
for EL6 now (Red Hat developer subscriptions are cheap, always have been 
since
RHN dropped RHL), and others could be running it on "EL rebuilds" when they
become available.

-- 
Bryan J  Smith       Professional, Technical Annoyance
Linked Profile:     http://www.linkedin.com/in/bjsmith

________________________________
From: Joe <joe_tseng at hotmail.com>
To: calug at unknownlamer.org
Sent: Thu, June 9, 2011 7:56:15 AM
Subject: [CALUG] Fedora upgrade unsuccessful


All,

I’m working on upgrading my Amahi 5/F12 install to Amahi 6.1/F14 and I’m
running into an issue.

First off, during the system check, the installer comes back and says it 
can’t
save the install.img file in /boot (/dev/sda1) because the partition is  too
small.  Then after I’ve had preupgrade-cli download all the files and 
rebooted
the system, I get a msg saying:

“The following file systems for your system were not unmounted  cleanly. 
Please

boot your installation, let the file systems be checked  and shut down 
cleanly
to upgrade.  (/dev/sda1)”

The reboot does not fsck that partition and I can’t do it while  mounted. 
Is
there some way I can get around this hurdle or can I just use  a F14 install
disk for the upgrade?