Red Hat Bugzilla – Bug 28925
Install crashes in expert text mode
Last modified: 2007-04-18 12:31:40 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.1-0.1.9 i686)
In expert text mode install crashes when preparing to install packages.
Steps to Reproduce:
1. At the syslinux boot prompt type "expert text"
2. Choose the following options (maybe not in exact order):
english/cdrom install/no driver disks/custom install/install
everything/manual partition using disk druid/added one non-root
user/default security options.. ie. md5 & shadow.. no kerberos etc./medium
I think that pretty much covers it
Actual Results: In expert text mode install crashes when preparing to
I attempted a total of 4 installs using "expert text" from the syslinux
prompt. 3 of those 4 crashed. the first machine this happened on was a
compaq ipaq. the install went through on the second attempt. I thought it
might just be flakey hardware until the same thing happened on my home
machine twice. after the second time i tried the graphical install and it
went through alright.
It crashes when it is preparing to install the packages. it gets and
unexptected sig 11.
Expected Results: Expected to install successfully
What is the error it gives when it crashes?
Ok i tried an expert text install on my picturebook and got similar results.
The installed aborted just after it began to install packages.
The following errors were displayed:
install exited abnormally -- recieved signal 11
sending termination signals...done
sending kill signlals...done
/mnt/sysimage umount failed (16)
you may safely reboot yoursystem
i believe it died while installing the db3 package.
after playing with it a few times.. messing around on virtual consoles, it
seemed to get through the install process ok. I didn't change anything tho.
Just checked the MD5 sum and it looks like it failed.
I could have sworn that i checked it earlier. oh well. this is probably the
source of the problem.
I will double check that it is not the source of my other bug report as well.
I reinstalled with a good cd and the problems no longer occured, so I think this
bug can be closed.