Bugzilla – Bug 154839
installation stops at "Finishing Basic Installation" "Creating initrd..." 72%
Last modified: 2006-03-23 23:28:53 UTC
Installation now has stopped in the very same spot twice! This update (from 10.1 beta3) is attempted on my Thinkpad 390E (128 MB RAM) I have no /boot partion everything goes to / that is reiserfs 3.6, standard journal, using ordered data mode, using flush barriers (disabled later) I will attach logs
Created attachment 71079 [details] yast2 log
Created attachment 71081 [details] boot.msg from 10.1 beta5
I let the Thinkpad continue over the night, still on 72%... Another interesting thing is that the installation process has not freezed - it is possible use Abort the installation.
Jiri: If this is nothing for you, please assign it back to us.
Please, reproduce the bug once more, and attach contents of /mnt/var/log/YaST2/ directory when the problem occurres. Most probably some packages was not installed, which caused this fail...
Isn't that exactly what the already attached yast2 log is?
No. You attached /var/log/YaST2/*, I need /mnt/var/log/YaST2/*. The reason is that some parts of YaST are running in chroot, and store their logs to /mnt/var/log/YaST2 (they cannot write outside the chroot jail). If you try to reproduce it, please, try Beta6 (or the newest available beta)
Retried but failed earlier. "Installation of package /suse/i586/kerry-0.07-4.i586.rpm failed" Details ... kerry-0.07-4.i586.rpm installed ok ... yast-packagemanager-2.13.14-3.i586 remove failed rpm output: error: package yast2-packagemanager-2.13.14-3.i586 is not installed (removed by earlier installation attempt?) mono-core-1.1.13.2-5.i586 remove failed rpm output: error: package mono-core-1.1.13.2-5.i586 is not installed (related to bug #154659 ?) Interesting to note is that removing an already removed package results in an error... (kerry installed ok!)
Created attachment 71510 [details] /mnt//../YaST2
Requested log attached from the above described failed install.
Since the fault mentioned in comment 8 looked to be in error I ignored it and let the installation continue. This time it passed those 72% and worked!? (Currently in Clean Up after the initial boot)
Did ignore make it ignore all other CDs? The install did never request anything from CD2-CD5 (upgrade from Beta3)
This problem should have already been fixed. Please, try with Beta8, and if problems persist, reopen and attach new logs.
Run into bug #155284 (update=0, new=818) when trying to upgrade to beta8. This has to be solved before I can retest...