(Reply to my own post, for the benefit of others who might run into the same problem). Ok, finally got the solution for this. During kickstart apply the anaconda update from <a href="http://rvykydal.fedorapeople.org/updates.608773.beta2.img">http://rvykydal.fedorapeople.org/updates.608773.beta2.img</a> like linux ks=<all your usual parameters> updates=http://<yourserver>/<path>/updates.608773.beta2.img This is the update required for anaconda included in beta2. <div class="gmail_quote">On 7 July 2010 10:10, Kurt Keller <<a href="mailto:kkathag@gmail.com">kkathag@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Since beta 2 we encounter one error on every kickstart install. This prevents us from performing the fully automated installs we require, as somebody has to manually select 'retry'. Has anybody else these errors? Is there any switch which could be used to automatically retry instead of waiting for an admin to select 'retry'? What happens is: - we PXE boot - kickstart and channels are accessed via http - while in the stage "Starting installation process", there will always be exactly one rpm package (not always the same) with the following error: "The file xxxx.rpm cannot be opened. This is due to a missing file, a corrupt package or corrupt media..." - selecting retry works fine and the installation continues - 30 seconds before this error occurs, we see in the webserver logs, that last request for partial of this file (status code 206) - at the time this occurrs we see syslog messages from the machine being installed saying it timed out on the file We don't think this is a problem with the webserver, network or the like, as it happens always with RHEL6b2 and never with RHEL4/5 F13, using the same installation infrastructure and even running at the same time. Thanks, Kurt </blockquote></div>