I think one can get this issue if the installation system images are
missing...

Thus:

	..../SL/RPMS/...
	       /base/   <--- this one

I'm not going to mess our working system up to try it (!) but I believe
this has bitten us in the past.

Martin.


 

> -----Original Message-----
> From: [log in to unmask] 
> [mailto:[log in to unmask]] On 
> Behalf Of Miles O'Neal
> Sent: 17 November 2005 14:27
> To: Scientific Linux Users
> Subject: Re: kickstart problem
> 
> Sascha Brechenmacher said...
> 
> |i tried since a day to install a server (amd64) via 
> kickstart. The first 
> |problem was the bcm5700 kernel module.
> |That is now fixed. But now i receive a "That directory does 
> not seem to 
> |contain a Scientific Linux installation tree"
> |from kickstart.
> |
> |That's what I've done. I mirrored the i386 and x86_64 tree 
> from SL 4x to 
> |/data/mirror/SL/4x/i386 and
> |/data/mirror/SL/4x/x86_64 than I changed my kickstart.cfg to install 
> |from NFS with the following entry
> |
> |nfs --server=192.168.52.253  --dir=/data/mirror/SL/4x/x86_64/SL/
> |
> |than I reboot. NFS is working I see the mount in the logs.
> 
> You might try it without the "SL/" part.
> 
> We use
> 
>    ... --dir=$basepath/SciLinux/3.0.4/64bit/LiveFS
> 
> The contents of that are:
> 
>    apt/      images/    misc/   RELEASE-NOTES.html  
> RPM-GPG-KEYs/  SL.documentation/  SRPMS/
>    contrib/  isolinux/  README  RHupdates/          SL/       
>      SL.releasenote
> 
> I built that directory by mounting the ISOs via
> loopback (man mount for details).  I don't know
> how that compares to what you're getting via
> rsync, but if these sorts of contents are in
> the same dir as SL/, that's where you need to
> point.  Or you may need to go down a level or
> two; without having your file tree right here
> it's hard to say for sure.
> 
> -Miles
>