FED13 Kickstart. Client failed, loader failed to mount

[fjbejarano]

Hi

First, sorry for my english, I don't speak (write) very well
I have configured the remote installation of Fedora 13 with kickstart with nfs installation method. All work ok until I boot the Fedora 13 client system.

Fed13 client system receives the IP address from dhcp, receives the loader, loads vmlinuz and initrd.img from tftp, load anaconda, configures the network and dev eth0, mounts nfs server to load kickstart file, loads kickstart file (language...) but when it tries to mount nfs server to install from Fedora 13 installation tree it fails.

First, I thought that I had an error on my NFS configuration but I was wrong. I opened tty with ALT+F4 on the Fedora 13 client and I sew this error:

INFO loader: mounting nfs path 192.168.2.50:/export/Fed13/images
INFO loader: can access /mnt/stage2//install.img
ERROR loader: failed to mount loopback device /dev/loop0 on /mnt/runtime as /mnt/stage2//install.img: (null)
WARNING loader: unable to mount /mnt/stage2//install.img

The loader adds two backslash when it only must add one backslash...

Is this a bug or can I modify anything to correct this error? How?

Thanks

[fjbejarano]

Is there any solution for this? or I can not use kickstart with fedora 13 and nfs.

Has somebody installed fedora 13 with kickstart and nfs?

Thanks

[fjbejarano]

The problem was not from Fedora13.

The problem was related to VirtualBox 3.2.4. With 3.2.6 it works fine.

The solution is here (in spanish, sorry)

http://yoadminsis.blogspot.com/2010/06/virtual-box-326-actualizacion.html

[fjbejarano]

The problem was not from Fedora13.

The problem was related to VirtualBox 3.2.4. With 3.2.6 it works fine.

The solution is here (in spanish, sorry)

http://yoadminsis.blogspot.com/2010/06/virtual-box-326-actualizacion.html