I can't seem to preupgrade to f13-beta. Is this just a mirror problem and waiting a while longer will fix it or is preupgrade not supposed to work before the final release? I've tried "yum clean all" and it still comes up with this error.
# preupgrade /usr/lib/python2.6/site-packages/yum/__init__.py:215: UserWarning: Use .preconf instead of passing args to _getConfig warnings.warn('Use .preconf instead of passing args to _getConfig') Loaded plugins: blacklist, fastestmirror, presto, refresh-packagekit, whiteout Detected in-progress upgrade to Rawhide Clearing data from upgrade to Rawhide preupgrade (baseurl) url: http://fake.url/preupgrade now: http://fake.url/preupgrade Determining fastest mirrors * fedora: mirror.stanford.edu * updates: mirrors.kernel.org preupgrade (mirrorlist) url: http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=$basearch now: http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=x86_64 Checking for new repos for mirrors unknown metadata being downloaded: repomd9pHc7btmp.xml [Errno 256] No more mirrors to try. [Errno 256] No more mirrors to try. #
-wolfgang
----- "Wolfgang S. Rupprecht" wolfgang.rupprecht@gmail.com wrote:
I can't seem to preupgrade to f13-beta. Is this just a mirror problem and waiting a while longer will fix it or is preupgrade not supposed to work before the final release? I've tried "yum clean all" and it still comes up with this error.
# preupgrade /usr/lib/python2.6/site-packages/yum/__init__.py:215: UserWarning:Use .preconf instead of passing args to _getConfig warnings.warn('Use .preconf instead of passing args to _getConfig') Loaded plugins: blacklist, fastestmirror, presto, refresh-packagekit, whiteout Detected in-progress upgrade to Rawhide Clearing data from upgrade to Rawhide preupgrade (baseurl) url: http://fake.url/preupgrade now: http://fake.url/preupgrade Determining fastest mirrors * fedora: mirror.stanford.edu * updates: mirrors.kernel.org preupgrade (mirrorlist) url: http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=$basearch now: http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=x86_64 Checking for new repos for mirrors unknown metadata being downloaded: repomd9pHc7btmp.xml [Errno 256] No more mirrors to try. [Errno 256] No more mirrors to try. #
-wolfgang
The preupgrade to F13 Branched should work provided that you have at least 250MiB /boot. It seems to me that you tried preupgrade to Rawhide instead.
On Wed, 2010-04-14 at 04:18 -0400, Kamil Paral wrote:
The preupgrade to F13 Branched should work provided that you have at least 250MiB /boot.
I just tried to run preupgrade on my 32-bit F12 system with 400MB /boot. Preupgrade seemed to run successfully, but when trying to reboot to the grub entry for the upgrade I only get a black screen with a cursor in the upper left hand corner.
Booting F12 still works.
I have not tried rerunning preupgrade yet.
birger
----- "birger" birger@birger.sh wrote:
On Wed, 2010-04-14 at 04:18 -0400, Kamil Paral wrote:
The preupgrade to F13 Branched should work provided that you have
at
least 250MiB /boot.
I just tried to run preupgrade on my 32-bit F12 system with 400MB /boot. Preupgrade seemed to run successfully, but when trying to reboot to the grub entry for the upgrade I only get a black screen with a cursor in the upper left hand corner.
Booting F12 still works.
I have not tried rerunning preupgrade yet.
birger
That's this one: https://bugzilla.redhat.com/show_bug.cgi?id=582590 https://fedoraproject.org/wiki/Common_F13_bugs#black-screen-on-kickstart-ins...
On Mon, 2010-04-19 at 04:32 -0400, Kamil Paral wrote:
That's this one: https://bugzilla.redhat.com/show_bug.cgi?id=582590 https://fedoraproject.org/wiki/Common_F13_bugs#black-screen-on-kickstart-ins...
Not at first glance. I just tried a boot to test your tip.
When booting F12 the screen goes black with the cursor in the upper left corner and the disk led goes on while it reads the initial image.
When booting the F13 upgrade it gets stuck there with the disk led on. No reaction to Ctrl-Alt-F1 or F7 or anything else but Ctrl-Alt-Delete.
birger
On Mon, Apr 19, 2010 at 11:45:35AM +0200, birger wrote:
On Mon, 2010-04-19 at 04:32 -0400, Kamil Paral wrote:
That's this one: https://bugzilla.redhat.com/show_bug.cgi?id=582590 https://fedoraproject.org/wiki/Common_F13_bugs#black-screen-on-kickstart-ins...
Not at first glance. I just tried a boot to test your tip.
When booting F12 the screen goes black with the cursor in the upper left corner and the disk led goes on while it reads the initial image.
When booting the F13 upgrade it gets stuck there with the disk led on. No reaction to Ctrl-Alt-F1 or F7 or anything else but Ctrl-Alt-Delete.
I've run into, once or twice (too random to file a bug about it), a similar issue where I was able to fix it by changing root=<UUID> to root=/dev/<sdXx> in the kernel line.
Perhaps it might be worthwhile changing the grub timeout to 3 or so, removing rhgb quiet from the kernel line, and booting into runlevel 3 to see if there's more information about why it's failing.
On Mon, 2010-04-19 at 11:45 +0200, birger wrote:
On Mon, 2010-04-19 at 04:32 -0400, Kamil Paral wrote:
That's this one: https://bugzilla.redhat.com/show_bug.cgi?id=582590 https://fedoraproject.org/wiki/Common_F13_bugs#black-screen-on-kickstart-ins...
Not at first glance. I just tried a boot to test your tip.
When booting F12 the screen goes black with the cursor in the upper left corner and the disk led goes on while it reads the initial image.
When booting the F13 upgrade it gets stuck there with the disk led on. No reaction to Ctrl-Alt-F1 or F7 or anything else but Ctrl-Alt-Delete.
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?
birger
----- "birger" birger@birger.sh 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
On Mon, 2010-04-19 at 07:42 -0400, Kamil Paral wrote:
----- "birger" birger@birger.sh 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?
birger
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@birger.sh 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?
Thanks, James
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@birger.sh 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
-
Birger Monsen -
James Laska -
Kamil Paral -
Scott Robbins -
Wolfgang S. Rupprecht