Fedora Account System
Red Hat Associate
Red Hat Customer
This bug was filed automatically by anaconda.
Created attachment 324873 [details] Attached traceback automatically from anaconda.
Created attachment 324876 [details] Attached traceback automatically from anaconda.
second crash for my PPC machine, another installation. In some reazon (probably another bug in anaconda) anaconda put this bug as attachment for current bug report.
There is nothing to triage here. Switching to ASSIGNED so that developers have responsibility to do whatever they want to do with it.
Dump in comment #2 is fake (i tried to upgrade f10 to f10). I had two upgrade attempts. First attemp enged with exception simillar to comment 2, but upgrade procedure not stopped. Probably it depend on another bug in save exception dialog. In this case i tried to save exception to bugzilla but i typed wrong user name, unexist. (user name 'axet' instead 'ak' with my real password). after it i got no errors or warning dialog. after it i close exeption dialog by esc key or close window button. And upgrade procedure continued... After upgrade procedure i tried to reproduce bug on my ppc machine, and here is comment #2.
I too had this same anaconda crash when I tried to do a F9 -> F10 upgrade. The other problem is I can't save the stack dump. I did copy it by hand. The python stack dump is identical to mine. My system is: Pentium II 450 MHz 327600 MB Is there any other information needed?
*** Bug 473170 has been marked as a duplicate of this bug. ***
*** Bug 473467 has been marked as a duplicate of this bug. ***
When you hit the traceback, can you press ctrl-alt-f2 to get to a shell, type mount, and paste the output into this bug report? Right now, I'm not seeing how it's possible to get into the situation you're in and need a little more information.
*** Bug 473529 has been marked as a duplicate of this bug. ***
Matt - are you able to reproduce this on a machine that I can come sit in front of?
*** Bug 473380 has been marked as a duplicate of this bug. ***
(In reply to comment #9) > When you hit the traceback, can you press ctrl-alt-f2 to get to a shell, type > mount, and paste the output into this bug report? Right now, I'm not seeing > how it's possible to get into the situation you're in and need a little more > information. fdisk -l Disk /dev/sda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xc0a5aeec Device Boot Start End Blocks Id System /dev/sda1 * 1 14593 117218241 83 Linux mount rootfs on / type rootfs (rw) /proc on /proc type proc (rw) /dev on /dev type tmpfs (rw) /dev/pts on /dev/pts type devpts (rw,mode=600) /sys on /sys type sysfs (rw) none on /tmp type ramfs (rw) /dev/sr0 on /mnt/stage2 type iso9660 (ro) /dev/loop0 on /mnt/runtime type squashfs (ro) /selinux on /selinux type selinuxfs (rw) /dev/sda1 on /mnt/sysimage type ext3 (rw,errors=continue,user_xattr,acl,data=ordered) /dev/sdb1 on /1 type ext4 (rw,barrier=1,data=ordered)
/dev/sdb1 on /1 type ext4 (rw,barrier=1,data=ordered) is my usb-flash, connected after traceback for log's transfer
i found that really happens. problem with swap file my system have swap file in root file system. look like anaconda enable swap file which prevent to unmount old file system! [axet@axet-laptop ~]$ cat /etc/fstab UUID=17050de4-c9bc-4938-9615-090c227ce8fb / ext3 defaults 1 1 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /var/swap swap swap
Yes, I also have a swap file in root fs. I recall (vaguely) that I noticed anaconda had enabled it, and thought that was strange, but didn't realize it was the problem.
remove "/var/swap swap swap" line from fstab and you get able to upgrade!
*** Bug 474711 has been marked as a duplicate of this bug. ***
John, do you also have a swap file configured?
I confirm that deleting the swap file line in /etc/fstab allowed me to boot into F10. I had originally filed 474711, which is now closed duplicate.
I can reproduce this pretty easily by creating a swap file: dd if=/dev/zero of=/var/swap bs=1M count=2048 mkswap /var/swap echo '/var/swap swap swap defaults 0 0' >> /etc/fstab swapon -a and then attempting an upgrade. Removing the swapfile from fstab fixes it.
Patch to fix this up for discussion in the following thread: https://www.redhat.com/archives/anaconda-devel-list/2008-December/msg00104.html
Yes, I do have two swap files configured and I did commented them out in /etc/fstab. I was able to get further, but the update process hung. I saw a Bugzilla entry dealing with the update process hang.
I've pushed a fix for this that will be included in the next build of anaconda. In addition, we're considering this fix for inclusion in an updates.img against F10 to help people complete their upgrades.
Created attachment 326511 [details] Attached traceback automatically from anaconda.
Created attachment 327313 [details] Attached traceback automatically from anaconda.
*** Bug 478829 has been marked as a duplicate of this bug. ***
It has been a while since Chris Lumens posted comment #24 (over a month) and there has been three subsequent comments since. Has there been any movement on this bug? It seems to still have the status of ON_QA. It there a significant backlog of higher priority bugs ahead of this one? I would really like to start upgrading to F10 and use it before F11 gets released.
My trace posted to Bug 478829 . Removing swap from fstab resolved the issue.
why this bug still not closed?
I was waiting for some official work on getting an updates image together, but that never materialized. Therefore, I've put together my own updates image for this bug. If you add updates=http://clumens.fedorapeople.org/f10-updates.img to your boot arguments, you should be able to work around this problem. If you do not have network access, you can still use an updates image on physical media. For more information on working with an updates image, see http://fedoraproject.org/wiki/Anaconda/Updates. Thanks for your patience.
Created attachment 331934 [details] Attached traceback automatically from anaconda.
I'd like to thank Chris Lumens for his effort in fixing this bug. I was afraid I was going to evolve into Homo Sapien Sapiens Paleo Flatus. My question is, has the net install CD, Fedora-10-i386-netinstall.iso, been re-spun with the Mr. Lumens updates? If it hasn't, then, I could do this. My next question is, where would I upload this ISO image?
*** Bug 492534 has been marked as a duplicate of this bug. ***
Hello, thank you for your fast replay. However, I'd like to solve the issue by being able to use pregrade to do an upgrade from f9 to f10. How exactly do I do this? Thank you Jason