[CALUG] Fedora upgrade unsuccessful

[James Ewing Cottrell 3rd]

  Well, I hate to jump in here because Bryan seems to be giving you good 
advice, but since I have never used Amahi either I can't resist.

My advice is of the form "when you realize that you're going down the 
wrong road, turn back as soon as possible" and "don't throw good money 
(or effort) after bad".

I never do upgrades...always clean installs. And I would *never* attempt 
to update further than N to N+1.

And I never accept the default partitioning. Disks are Huge these days, 
but someone chose a Puny /boot size.

I usually make an 8G partition, install a small Rescue Linux there that 
owns the MBR, and then use that same partition as the /boot of my "real" 
systems. But *don't reformat* that partition on install.

Since you are using LVM, sharing your existing root LV and create 
another. You can dual boot both systems...F12 and F14. OK, so your files 
in /boot will conflict with each other, but you can put them into 
subdirectories and alter your grub.conf lines.

Or if you want to keep the same root, just same the old files. Do 
something like:

cd /; mkdir /var/hda/f12; rsync -ax / /boot /var/hda/f12

Then do a clean install of f14 (hey...f15 is out now) and redo your 
customizations. How extensive are they?

JIM

P.S. What does your fsck look like? Does it go thru all the 5 passes? 
Since it's probably "dirty" it ought to run, but you may need to use the 
-f option to force it. The -o remount,ro trick that Bryan mentioned 
works nicely, altho you can also run it from Rescue Mode from the CD.

On 6/12/2011 10:42 AM, Bryan J Smith wrote:
> As I mentioned, Anaconda is Anaconda, whether Preupgrade Anaconda or the DVD
> Anaconda.  It's not going to let you upgrade a system with unclean file systems.
>
>
> As such, your issue is with your current Fedora 12 install, and why it is not
> shutting down/rebooting prior.  I have no experience with Amahi, so I don't know
> what it could be doing to Fedora's init process that would cause this.
>
> The solution is to boot into a mode where the file systems are read-only and run
> fsck manually on all file systems.  After that, reboot directly into Anaconda
> for the Fedora 14 upgrade.  And even that assumes the fsck doesn't leave the
> packages in an unknown state after the file system is made consistent.
>
>
>
> ----- Original Message ----
> From: Joe<joe_tseng at hotmail.com>
> Sent: Sun, June 12, 2011 10:20:22 AM
>
> Since we last left our caped crusaders...
>
> 1. I commented out the "hiddenmenu" option in grub.conf and deleted the
> caches created by preupgrade.
> 2. I ran preupgrade and got it to cache everything.  When it was all done
> (right before I rebooted), I unmounted /boot and fsck'd it to make sure it
> was clean.  I left it unmounted and rebooted.
> 3. I still got the "unclean mount" message.
> 4. I reran step 2 but I rebooted using an F14 DVD.  I got up to the point
> where it asked me to designate a system disk - after I did that THEN that
> "unclean mount" message reappeared.
>
> _______________________________________________
> CALUG mailing list
> CALUG at unknownlamer.org
> http://lists.unknownlamer.org/listinfo/calug
>