Red Hat Bugzilla – Bug 98719
kernel-smp hangs install if symlink not present...
Last modified: 2007-11-30 17:06:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314
Description of problem:
When installing kernel-smp it seems that it's expecting this symlink to be there:
that isn't there. In the install.log file located in /mnt/sysimage/tmp, the last
"tar: error while loading shared libraries: libredhat-kernel.so.1: cannot open
shared object file: No such file or directory"
Also, I am not doing a full install (see below for the ks.cfg script that
specifies the RPMS that are being install).
Additional Info (May be helpful, may not)
Hardware: Dell Poweredge 1600SC
Installation type: Network install using Kickstart script
nfs --server apt.provo.novell.com --dir /inet/ftp/pub/redhat/2.1AS/i386/
langsupport --default en_US en_US
authconfig --enableshadow --enablemd5
part swap --size 1 --maxsize 512 --grow --asprimary --fstype swap
part / --size 1 --grow --asprimary --fstype ext3
@ Classic X Window System
@ X Window System
@ Network Support
@ Advanced Server
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Steps to recreate:
1. do a kickstart install with a ks.cfg file that has the same package list as
the ks.cfg file from the description.
2. wait until the kernel-smp rpm is trying to be installed.
3. notice that the installer hangs and that you see the same error message as
above in the install.log file.
Actual Results: the installer hangs while installing the kernel-smp rpm and
Expected Results: it should finish installing the kernel-smp rpm
Ok, I just did a CD install using the same ks.cfg file and it installed just
fine, so it seems to be only on NFS installs that it has problems.
My Symlink conclusion could be wrong. Looking at the filesystem from a
successful cd install with the same ks.cfg file, I've noticed that it doesn't
contain a symlink either. So I'm really not sure what's causing this.
One more thing, this is using all update-2 stuff. When I'm doing the NFS
install, I'm using bootnet.img and drvnet.img (both update-2 of course).
Created attachment 92785 [details]
install.log file from a successfull CD install using the same ks.cfg file
Created attachment 92786 [details]
install.log file from an unsuccessfull NFS install using the same ks.cfg file
*** This bug has been marked as a duplicate of 98717 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.