Re: preupgrade to f13-beta

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2010-05-04 at 08:59 -0400, James Laska wrote:
> On Tue, 2010-05-04 at 13:14 +0200, birger wrote:
> > On Mon, 2010-04-19 at 07:42 -0400, Kamil Paral wrote:
> > > ----- "birger" <birger@xxxxxxxxx> wrote:
> > > > 
> > > > I retried, but let it sit there with the blinking cursor while
> > > > cleaning
> > > > the house. After a loooong time it finally popped up a graphical
> > > > installer.
> > > > 
> > > > All log files seem to have started at the moment the system woke up,
> > > > so
> > > > it seems like it 'just' needs a long time loading the initram or
> > > > something like that? Right now it's sitting in the installer waiting
> > > > for
> > > > me to select disk. Is there anything I should check?
> > > > 
> > > > Restart the upgrade with some options?
> > > 
> > > I think you should wait a while until preupgrade-1.1.5 is out,
> > > it fixes some more errors that may have influenced your
> > > upgrade process:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=572148
> > > https://bugzilla.redhat.com/show_bug.cgi?id=575400
> > 
> > I installed 1.1.5 from updates-testing and tried again.
> > 
> > Previously, anaconda stopped and asked which disk to upgrade on after
> > the boot. It doesn't do that anymore, so it was too late to stop the
> > upgrade process. I have not had a chance to test the end result.
> > 
> > The hang was still there. After preupgrade did its job and rebooted, I
> > got the black screen with the blinking cursor in the upper left hand
> > corner as before. This time I got to time it, and after exactly 20
> > minutes it started X and did the upgrade.
> > 
> > Are there any log files or commands that would be interesting in order
> > to determine where the problem is?
> 
> On your upgraded system, you can remove "rhgb quiet" from the boot
> arguments, this should allow a closer look at what might be causing the
> slow boot.  Additionally, there should be a /var/log/boot.log file for
> inspection after you've booted.  Any hints there?

I have no problems booting the upgraded system. It seems like it is only
the anaconda/f13 upgrade boot that consistently would hang for 20
minutes.

All of the /var/log/anaconda.* log files start at the moment the system
got unstuck after the 20 minute hang. No help there.

This system is a 2.8GHz P4 system with only 512MB RAM.

The only issue I have had so far after the upgrade is a small evolution
problem with my imap account.


birger

-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux