suse 10.0 nfs install
Are there any known issues with using the OpenSUSE 10.0 original distro to do an NFS install to a PXE-booted client? Any show stopping bugs that require an update? I have set up dhcp ok, pxelinux.0 runs and uses my default file. All options as described in the SUSE online docs have been used. But I do not quite get the install to start: The install kernel boots. At some point it wants to get a DHCP address for the ethernet card. This 'should' be working as it got an address when it first booted. I see this in the server's /var/log/messages. But this seems to timeout. My dhcp entry is: host jboc1 { filename "/suseInstall/pxelinux.0"; fixed-address 192.30.105.204; hardware ethernet 00:30:48:56:38:B2; next-server 192.30.105.201; option host-name "jboc1"; } 192.30.105.201 is the server for everything (dhcp, pxe, suse install) After this, I get a message that the SUSE installation source cannot be found. When trying to set it up by hand (nice it does that), I see that the default values it offers are the ones I expect (despite the probable DHCP oddness). But when it tries to mount the nfs install source, it fails with 'unknown error -1'. Why is it looking for a DHCP server when I add the hostip= command to the kernel command line? This option seems to be ignored. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 53 Fax: Int +46 8-31 42 23
Are there any known issues with using the OpenSUSE 10.0 original distro to do an NFS install to a PXE-booted client? Any show stopping bugs
On Wed, 2006-02-22 at 17:06 +0100, Roger Oberholtzer wrote: that
require an update?
I have set up dhcp ok, pxelinux.0 runs and uses my default file. All options as described in the SUSE online docs have been used. But I do not quite get the install to start:
The install kernel boots. At some point it wants to get a DHCP address for the ethernet card. This 'should' be working as it got an address when it first booted. I see this in the server's /var/log/messages. But this seems to timeout. My dhcp entry is:
I should add that I do not know that the dhcp request is timing out. It is just the last message I see. Perhaps it is the next thing that is timing out. I do see this in /var/log/messages on the server: dhcpd: DHCPDISCOVER from 00:30:48:56:38:b3 via eth0 dhcpd: DHCPOFFER on 192.30.105.204 to 00:30:48:56:38:b2 via eth0 dhcpd: DHCPREQUEST for 192.30.105.204 (192.30.105.201) from 00:30:48:56:38:b2 via eth0 dhcpd: DHCPACK on 192.30.105.204 to 00:30:48:56:38:b2 via eth0 I think dhcp is ok. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 53 Fax: Int +46 8-31 42 23
Looks similar to my dhcpd.conf (apart that I just have "pxelinux.0", so without the path). But since it found the boot kernel that seems to be ok. In my tftpboot/pxelinux.cfg/default: default linux64AUTO # install label linux64AUTO kernel linux64 append initrd=initrd64 ramdisk_size=65536 install=nfs://10.0.0.200/usr/SuSE10DVD/SuSE autoyast=nfs://10.0.0.200/var/lib/autoinstall/repository/borgClientsInstall.xml vnc=1 vncpassword=XXX splash=silent showopts I remember I had protection issues on the install source. I put it under the root's home directory but since I have root_squash it could not be loaded. I had to open that directory so others could read it. append initrd=initrd64 ramdisk_size=65536 install=nfs://10.0.0.200/usr/SuSE10DVD/SuSE autoyast=nfs://10.0.0.200/var/lib/aut oinstall/repository/borgClientsInstall.xml Roger Oberholtzer wrote:
Are there any known issues with using the OpenSUSE 10.0 original distro to do an NFS install to a PXE-booted client? Any show stopping bugs that require an update?
I have set up dhcp ok, pxelinux.0 runs and uses my default file. All options as described in the SUSE online docs have been used. But I do not quite get the install to start:
The install kernel boots. At some point it wants to get a DHCP address for the ethernet card. This 'should' be working as it got an address when it first booted. I see this in the server's /var/log/messages. But this seems to timeout. My dhcp entry is:
host jboc1 {
filename "/suseInstall/pxelinux.0"; fixed-address 192.30.105.204; hardware ethernet 00:30:48:56:38:B2; next-server 192.30.105.201; option host-name "jboc1"; }
192.30.105.201 is the server for everything (dhcp, pxe, suse install)
After this, I get a message that the SUSE installation source cannot be found. When trying to set it up by hand (nice it does that), I see that the default values it offers are the ones I expect (despite the probable DHCP oddness). But when it tries to mount the nfs install source, it fails with 'unknown error -1'.
Why is it looking for a DHCP server when I add the hostip= command to the kernel command line? This option seems to be ignored.
-- Best regards, Mattijs Mattijs Janssens OpenCFD Ltd. The Mews, Picketts Lodge, Picketts Lane, Salfords, Surrey RH1 5RG. Tel: +44 (0)1293 821272 Email: M.Janssens@OpenCFD.co.uk URL: http://www.OpenCFD.co.uk
On Wed, 2006-02-22 at 16:43 +0000, Mattijs Janssens wrote:
Looks similar to my dhcpd.conf (apart that I just have "pxelinux.0", so without the path). But since it found the boot kernel that seems to be ok.
I see that when I try the manual install offered after the auto one fails, I can select DHCP. If I do, that fails. I see no reason why as DHCP is working for this client. Should there be something special in the dhcp config file? I thought next-server was about it.
In my tftpboot/pxelinux.cfg/default:
default linux64AUTO # install label linux64AUTO kernel linux64 append initrd=initrd64 ramdisk_size=65536 install=nfs://10.0.0.200/usr/SuSE10DVD/SuSE autoyast=nfs://10.0.0.200/var/lib/autoinstall/repository/borgClientsInstall.xml vnc=1 vncpassword=XXX splash=silent showopts
My current entry is: label linux kernel linux append initrd=initrd insmod=e1000 hostip=192.30.105.204 \ install=nfs://192.30.105.201/vol1/distro/OpenSUSE10.0/suse10.0 Another question: If I use YAST to set up the NFS install server, it asks me for a directory and a name for the install. The files from the CD are put in a sub-directory of the one I specified, called whatever name I gave for the install. In my example, I specified /vol1/distro/OpenSUSE10.0 as the directory, and suse10.0 as the name of the install. All the CD files were cop However, when it sets up the NFS export, it does not include the install name (i.e., the subdir with the actual SUSE source). I do not think this is a problem. But Yast's intentions are unclear. I have been trying both version in the append command (/vol1/distro/OpenSUSE10.0/suse10.0 and /vol1/distro/OpenSUSE10.0). Neither work. If I look at the on-line docs on setting this up by hand, the procedure is different. For example, the by-hand docs say to put the files in a directory called 'CD1'. Yast does not do this.
I remember I had protection issues on the install source. I put it under the root's home directory but since I have root_squash it could not be loaded. I had to open that directory so others could read it.
I had YasT set up the install source. I see that it exported the directory with: *(ro,root_squash,sync) I also tried: *(rw,sync) with no change. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 53 Fax: Int +46 8-31 42 23
participants (2)
-
Mattijs Janssens -
Roger Oberholtzer