RE: [suse-autoinstall] suse 10.0 nfs install
Roger, Roger Oberholtzer wrote:
Roger,
Roger Oberholtzer wrote:
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
On Wed, 2006-02-22 at 17:51 +0100, Gunreben, Peter (Peter) wrote: source, it
fails with 'unknown error -1'.
Have you checked whether the nfs-export works properly, e.g. by mounting it manually? I had a similar problem, where I tried to export a loop-mounted directory tree. Only, a userspace-nfsserver can do that.
I can mount it from other systems. Using
mount -t nfs source:/vol1/distro/OpenSUSE10.0/suse10.0 /tmp/vv
I can read files and go into directories.
It just got back to my mind that I had an additional problem. For
any reason I still do not know, I had to add insmod=
On Wed, 2006-02-22 at 18:40 +0100, Gunreben, Peter (Peter) wrote:
Roger,
Roger Oberholtzer wrote:
Roger,
Roger Oberholtzer wrote:
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
On Wed, 2006-02-22 at 17:51 +0100, Gunreben, Peter (Peter) wrote: source, it
fails with 'unknown error -1'.
Have you checked whether the nfs-export works properly, e.g. by mounting it manually? I had a similar problem, where I tried to export a loop-mounted directory tree. Only, a userspace-nfsserver can do that.
I can mount it from other systems. Using
mount -t nfs source:/vol1/distro/OpenSUSE10.0/suse10.0 /tmp/vv
I can read files and go into directories.
It just got back to my mind that I had an additional problem. For any reason I still do not know, I had to add insmod=
to the kernel parameters in order to get everything work. Of course, you need to replace with the one you need. May be it's worth to give it a try.
I have this: insmod=e1000 When all eventually fails, I see that the module is loaded. There seems to be activity on eth0 as well. Is there no way to log access attempts for this? Beyond the dhcp stuff, which indicates, me thinks, that all is well. The computer does have two identical ethernet ports. I have tried one or the other, as well as both. I could have made a mistake in doing that test, but I don't know how. I do not see a dhcp request on an unexpected port. Only on the one I expect. I want to install 10 systems in the morning. And more after that. I didn't expect this part to be the problem. I was saving that for autoyast.
Peter.
Things are just odd. I have two identical ethernet ports on the motherboard. It boots from one (pxelinux.0). SUSE install kernel starts. Then, when it wants to access the install server, it does another dhcp request - but on the other port than it booted. Why, I do not know. I see that the install kernel only enabled one ethernet port. So I only have eth0. Anyone can guess which port gets selected. Selecting eth0 or eth1 on the kernel command line is pointless an only one (not the one it booted from) gets enabled (eth0). I would think that if one MAC address got an address, the dhcp server would not just give the address to the next different MAC address that comes along. Here is what I see in my logs: When booting via PXE: dhcpd: DHCPDISCOVER from 00:30:48:56:38:b3 via eth0 dhcpd: DHCPOFFER on 192.30.105.204 to 00:30:48:56:38:b3 via eth0 dhcpd: DHCPREQUEST for 192.30.105.204 (192.30.105.201) from 00:30:48:56:38:b3 via eth0 dhcpd: DHCPACK on 192.30.105.204 to 00:30:48:56:38:b3 via eth0 When SUSE install kernel does a DHCP request just before locating the install server: dhcpd: DHCPDISCOVER from 00:30:48:56:38:b2 via eth0 dhcpd: DHCPOFFER on 192.30.105.204 to 00:30:48:56:38:b2 via eth0 dhcpd: DHCPDISCOVER from 00:30:48:56:38:b2 via eth0 dhcpd: DHCPOFFER on 192.30.105.204 to 00:30:48:56:38:b2 via eth0 Note that the second group of commands is from a different ethernet port (?!?) and that the client never does a DHCPREQUEST after the server's DHCPOFFER I am a bit lost here... On Wed, 2006-02-22 at 18:56 +0100, Roger Oberholtzer wrote:
On Wed, 2006-02-22 at 18:40 +0100, Gunreben, Peter (Peter) wrote:
Roger,
Roger Oberholtzer wrote:
Roger,
Roger Oberholtzer wrote:
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
On Wed, 2006-02-22 at 17:51 +0100, Gunreben, Peter (Peter) wrote: source, it
fails with 'unknown error -1'.
Have you checked whether the nfs-export works properly, e.g. by mounting it manually? I had a similar problem, where I tried to export a loop-mounted directory tree. Only, a userspace-nfsserver can do that.
I can mount it from other systems. Using
mount -t nfs source:/vol1/distro/OpenSUSE10.0/suse10.0 /tmp/vv
I can read files and go into directories.
It just got back to my mind that I had an additional problem. For any reason I still do not know, I had to add insmod=
to the kernel parameters in order to get everything work. Of course, you need to replace with the one you need. May be it's worth to give it a try. I have this: insmod=e1000
When all eventually fails, I see that the module is loaded. There seems to be activity on eth0 as well.
Is there no way to log access attempts for this? Beyond the dhcp stuff, which indicates, me thinks, that all is well.
The computer does have two identical ethernet ports. I have tried one or the other, as well as both. I could have made a mistake in doing that test, but I don't know how. I do not see a dhcp request on an unexpected port. Only on the one I expect.
I want to install 10 systems in the morning. And more after that. I didn't expect this part to be the problem. I was saving that for autoyast.
Peter.
-- 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
On Thu, 2006-02-23 at 08:57 +0100, Roger Oberholtzer wrote:
Things are just odd.
I have two identical ethernet ports on the motherboard. It boots from one (pxelinux.0). SUSE install kernel starts. Then, when it wants to access the install server, it does another dhcp request - but on the other port than it booted. Why, I do not know. I see that the install kernel only enabled one ethernet port. So I only have eth0. Anyone can guess which port gets selected. Selecting eth0 or eth1 on the kernel command line is pointless an only one (not the one it booted from) gets enabled (eth0). I would think that if one MAC address got an address, the dhcp server would not just give the address to the next different MAC address that comes along.
Here is what I see in my logs:
When booting via PXE:
dhcpd: DHCPDISCOVER from 00:30:48:56:38:b3 via eth0 dhcpd: DHCPOFFER on 192.30.105.204 to 00:30:48:56:38:b3 via eth0 dhcpd: DHCPREQUEST for 192.30.105.204 (192.30.105.201) from 00:30:48:56:38:b3 via eth0 dhcpd: DHCPACK on 192.30.105.204 to 00:30:48:56:38:b3 via eth0
When SUSE install kernel does a DHCP request just before locating the install server:
dhcpd: DHCPDISCOVER from 00:30:48:56:38:b2 via eth0 dhcpd: DHCPOFFER on 192.30.105.204 to 00:30:48:56:38:b2 via eth0 dhcpd: DHCPDISCOVER from 00:30:48:56:38:b2 via eth0 dhcpd: DHCPOFFER on 192.30.105.204 to 00:30:48:56:38:b2 via eth0
More info: I have sorted out a BIOS setup wherein all DHCP requests come over the same ethernet port. However, the client still does not reply to the DHCPOFFER in the second exchange, just as before. I would happily skip the DHCP stuff, but the kernel seems to ignore the hostip= option, even though it is documented in the SUSE docs for PXE installs... -- 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
On Thursday 23 February 2006 09:43, Roger Oberholtzer wrote:
I would happily skip the DHCP stuff, but the kernel seems to ignore the hostip= option, even though it is documented in the SUSE docs for PXE installs...
you need at least hostip=... and netmask=... -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
On Thu, 23 Feb 2006, Uwe Gansert wrote:
On Thursday 23 February 2006 09:43, Roger Oberholtzer wrote:
I would happily skip the DHCP stuff, but the kernel seems to ignore the hostip= option, even though it is documented in the SUSE docs for PXE installs...
you need at least hostip=... and netmask=...
or use hostip=a.b.c.d/<networkbits>. If you're unhappy with the dhcp client, bootp is available, too (via usedhcp=0). Steffen
On Thu, 2006-02-23 at 12:05 +0100, Steffen Winterfeldt wrote:
On Thu, 23 Feb 2006, Uwe Gansert wrote:
On Thursday 23 February 2006 09:43, Roger Oberholtzer wrote:
I would happily skip the DHCP stuff, but the kernel seems to ignore the hostip= option, even though it is documented in the SUSE docs for PXE installs...
you need at least hostip=... and netmask=...
or use hostip=a.b.c.d/<networkbits>. If you're unhappy with the dhcp client, bootp is available, too (via usedhcp=0).
(Reminder of my original question: does the YasT install server setup code in OpenSUSE 10.0 work, or is an update needed?) I am quite happy with dhcp. I use it all the time. In fact, it is doing the first part of this just fine - that is how the SUSE install kernel gets started. But something does wrong. No matter. At this time, I am also happy with using fixed addresses in the pxelinux config files. After adding the required netmask= option, I see that the DHCP question does not get asked. But it still does not find the install source ("unknown error -1"). The directory is, as I described earlier, made by YasT, containing all the CDs. As a reminder, it has these files/directories, as placed there by YasT. ls /vol1/distro/OpenSUSE10.0/suse10.0: ARCHIVES.gz autorun.inf boot ChangeLog content control.xml COPYING COPYING.de COPYRIGHT COPYRIGHT.de directory.yast docu dosutils gpg-pubkey-0dfb3188-41ed929b.asc gpg-pubkey-15c17deb-3f9e80c9.asc gpg-pubkey-3d25d3d9-36e12d04.asc gpg-pubkey-9c800aca-40d8063e.asc INDEX.gz LICENSE.TXT LIESMICH LIESMICH.DOS ls-lR.gz media.1 media.2 media.3 media.4 media.5 pubring.gpg README README.DOS suse SuSEgo.ico My spec is: install=nfs://192.30.105.201/vol1/distro/OpenSUSE10.0/suse10.0 I can ping the client from 192.30.105.201, so I know they are on the same network and active. I can mount the share from any other machine. But still the error "unknown error -1". -- 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
On Thu, 23 Feb 2006, Roger Oberholtzer wrote:
After adding the required netmask= option, I see that the DHCP question does not get asked. But it still does not find the install source ("unknown error -1"). The directory is, as I described earlier, made by
You can go to console 9 and mount the volume manually, e.g.: mount -r -t nfs a.b.c.d:/foo /mnt (that's not the regular mount(1) command and is rather picky with it's args) If that does not do, maybe you want NFS via tcp, boot with nfs.tcp=1 for that.
YasT, containing all the CDs. As a reminder, it has these files/directories, as placed there by YasT.
ls /vol1/distro/OpenSUSE10.0/suse10.0:
ARCHIVES.gz autorun.inf boot
linuxrc is looking for /boot/root. BTW, console 3 has some log messages. Steffen
On Thu, 2006-02-23 at 14:09 +0100, Steffen Winterfeldt wrote:
On Thu, 23 Feb 2006, Roger Oberholtzer wrote:
After adding the required netmask= option, I see that the DHCP question does not get asked. But it still does not find the install source ("unknown error -1"). The directory is, as I described earlier, made by
You can go to console 9 and mount the volume manually, e.g.:
mount -r -t nfs a.b.c.d:/foo /mnt
(that's not the regular mount(1) command and is rather picky with it's args)
If that does not do, maybe you want NFS via tcp, boot with nfs.tcp=1 for that.
The kernel complains that there is no option called 'nfs.tcp=1', so it was ignored.
YasT, containing all the CDs. As a reminder, it has these files/directories, as placed there by YasT.
ls /vol1/distro/OpenSUSE10.0/suse10.0:
ARCHIVES.gz autorun.inf boot
linuxrc is looking for /boot/root.
BTW, console 3 has some log messages.
Very interesting here: Server: 192.30.105.201 (no ip) Looking for a network server... Trying to activate eth0 Setting up localhost...done eth0 activated Starting portmap OK, going to mount 0.0.0.0:/vol1/distro/OpenSUSE10.0/suse10.0: ... if eth0 down which obviously fails. Why 0.0.0.0? Just a few lines back it printed 192.30.105.201, which is the server. I do not know what the 'no ip' means. I tried to mount by hand, but the device was brought down (last line on console 3). There is no ifconfig command, so I was unsure how to bring up the device.
Steffen
-- 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
On Thu, 23 Feb 2006, Roger Oberholtzer wrote:
If that does not do, maybe you want NFS via tcp, boot with nfs.tcp=1 for that.
The kernel complains that there is no option called 'nfs.tcp=1', so it was ignored.
The option is for linuxrc. It normally uses v2 via udp. The above changes that to v3 and tcp.
Very interesting here:
Server: 192.30.105.201 (no ip) Looking for a network server... Trying to activate eth0 Setting up localhost...done eth0 activated Starting portmap OK, going to mount 0.0.0.0:/vol1/distro/OpenSUSE10.0/suse10.0:
...
if eth0 down
which obviously fails. Why 0.0.0.0? Just a few lines back it printed 192.30.105.201, which is the server. I do not know what the 'no ip' means.
Yes, sorry. The log is wrong with 0.0.0.0 at this point. Actually the server address is fine.
I tried to mount by hand, but the device was brought down (last line on console 3). There is no ifconfig command, so I was unsure how to bring up the device.
'ps' shows you whether dhcpcd is running. If not, just start it. BTW, in 10.1 some network tools are available for debugging at this point. You can pick up a beta mini boot-CD from opensuse.org if you want to try it. (You will need to boot with rootimage=/boot/root if you are using it with a 10.0 setup, but apart from that it will work fine.) Steffen
On Thu, 2006-02-23 at 16:39 +0100, Steffen Winterfeldt wrote:
On Thu, 23 Feb 2006, Roger Oberholtzer wrote:
If that does not do, maybe you want NFS via tcp, boot with nfs.tcp=1 for that.
The kernel complains that there is no option called 'nfs.tcp=1', so it was ignored.
The option is for linuxrc. It normally uses v2 via udp. The above changes that to v3 and tcp.
Very interesting here:
Server: 192.30.105.201 (no ip) Looking for a network server... Trying to activate eth0 Setting up localhost...done eth0 activated Starting portmap OK, going to mount 0.0.0.0:/vol1/distro/OpenSUSE10.0/suse10.0:
...
if eth0 down
which obviously fails. Why 0.0.0.0? Just a few lines back it printed 192.30.105.201, which is the server. I do not know what the 'no ip' means.
Yes, sorry. The log is wrong with 0.0.0.0 at this point. Actually the server address is fine.
I tried to mount by hand, but the device was brought down (last line on console 3). There is no ifconfig command, so I was unsure how to bring up the device.
'ps' shows you whether dhcpcd is running. If not, just start it.
dhcpcd is not running, which makes sense as I used hostip= and netmask= on the command line. 'dhcpcd eth0' hangs. I see the request on the server, to which the server replies just like it did when the same client did a PXE boot some seconds earlier. But, unlike that time, the client does not respond to the dhcp address offered by the server.
BTW, in 10.1 some network tools are available for debugging at this point. You can pick up a beta mini boot-CD from opensuse.org if you want to try it. (You will need to boot with rootimage=/boot/root if you are using it with a 10.0 setup, but apart from that it will work fine.)
I'm not in the position to use 10.1 for this. I need to set up a production install of 10.0. -- 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
On Thu, 2006-02-23 at 18:14 +0100, Roger Oberholtzer wrote:
On Thu, 2006-02-23 at 16:39 +0100, Steffen Winterfeldt wrote:
On Thu, 23 Feb 2006, Roger Oberholtzer wrote:
If that does not do, maybe you want NFS via tcp, boot with nfs.tcp=1 for that.
The kernel complains that there is no option called 'nfs.tcp=1', so it was ignored.
The option is for linuxrc. It normally uses v2 via udp. The above changes that to v3 and tcp.
Very interesting here:
Server: 192.30.105.201 (no ip) Looking for a network server... Trying to activate eth0 Setting up localhost...done eth0 activated Starting portmap OK, going to mount 0.0.0.0:/vol1/distro/OpenSUSE10.0/suse10.0:
...
if eth0 down
which obviously fails. Why 0.0.0.0? Just a few lines back it printed 192.30.105.201, which is the server. I do not know what the 'no ip' means.
Yes, sorry. The log is wrong with 0.0.0.0 at this point. Actually the server address is fine.
I tried to mount by hand, but the device was brought down (last line on console 3). There is no ifconfig command, so I was unsure how to bring up the device.
'ps' shows you whether dhcpcd is running. If not, just start it.
dhcpcd is not running, which makes sense as I used hostip= and netmask= on the command line.
'dhcpcd eth0' hangs. I see the request on the server, to which the server replies just like it did when the same client did a PXE boot some seconds earlier. But, unlike that time, the client does not respond to the dhcp address offered by the server.
If I run dhcpcd -d, it tells that it has sent a request. I see (as always) in the server's log: source dhcpd: DHCPDISCOVER from 00:30:48:56:38:b2 via eth0 source dhcpd: DHCPOFFER on 192.30.105.204 to 00:30:48:56:38:b2 via eth0 with no response from the client
-- 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
On Thu, 2006-02-23 at 14:09 +0100, Steffen Winterfeldt wrote:
On Thu, 23 Feb 2006, Roger Oberholtzer wrote:
After adding the required netmask= option, I see that the DHCP question does not get asked. But it still does not find the install source ("unknown error -1"). The directory is, as I described earlier, made by
You can go to console 9 and mount the volume manually, e.g.:
mount -r -t nfs a.b.c.d:/foo /mnt
(that's not the regular mount(1) command and is rather picky with it's args)
If that does not do, maybe you want NFS via tcp, boot with nfs.tcp=1 for that.
The NFS server is using the default installed protocol I have not changed it.
-- 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
Has anyone else on this list actually done EXACTLY this: 1. Install OpenSUSE10.0 on a server 2. Use the YAST to set up an install server for the OpenSUSE 10.0 disks. 3. Used PXE to boot a client so it can do an install of OpenSUSE 10.0 from this server? Anyone? If so, did you do any updates to the OpenSUSE 10.0 on the server before setting up the install server? My problem in this thread is not solved. I can't believe this does not work. But I have yet to see what I have done wrong. Maybe I should post to the general group? -- Roger Oberholtzer
Hi @all, Roger Oberholtzer schrieb:
Has anyone else on this list actually done EXACTLY this:
1. Install OpenSUSE10.0 on a server
I use a boxed SuSE 10 on a MS IIS Installation Server. (Simply copied the DVD-Content.)
2. Use the YAST to set up an install server for the OpenSUSE 10.0 disks.
3. Used PXE to boot a client so it can do an install of OpenSUSE 10.0 from this server?
I`m not using PXE, but as i followed the Thread, that`s not the problem ;-) I prefer http instead of nfs, cause I never had trouble with http.
Anyone? If so, did you do any updates to the OpenSUSE 10.0 on the server before setting up the install server?
My problem in this thread is not solved. I can't believe this does not work. But I have yet to see what I have done wrong.
I also had trouble with the network configuration. My problem was, that with installation from CD every Network Driver was installed correctly, but if I installed the Network Driver in Manual Installation Mode (for Network Install), then the additional Module mii.o was missing. This resulted in a not working Network configuration. Loading the module by hand solves the Problem. So check out with lsmod during broken Installation, and compare with a running System. (Maybe you`ve got a similar Problem.) I hope this helps. Dirk TRIA IT-consulting GmbH Joseph-Wild-Straße 20 81829 München Germany Tel: +49 (89) 92907-0 Fax: +49 (89) 92907-100 http://www.tria.de Registergericht München HRB 113466 USt.-IdNr. DE 180017238 Steuer-Nr. 802/40600 Geschäftsführer: Richard Hofbauer kaufm. Geschäftsleitung: Rosa Igl -------------------------------------------------------- Nachricht von: Dirk.Schreiner@tria.de Nachricht an: roger@opq.se, suse-autoinstall@suse.com # Dateianhänge: 0
On Fri, 2006-02-24 at 10:24 +0100, Dirk Schreiner wrote:
Hi @all,
Roger Oberholtzer schrieb:
Has anyone else on this list actually done EXACTLY this:
1. Install OpenSUSE10.0 on a server
I use a boxed SuSE 10 on a MS IIS Installation Server. (Simply copied the DVD-Content.)
2. Use the YAST to set up an install server for the OpenSUSE 10.0 disks.
3. Used PXE to boot a client so it can do an install of OpenSUSE 10.0 from this server?
I`m not using PXE, but as i followed the Thread, that`s not the problem ;-)
I prefer http instead of nfs, cause I never had trouble with http.
I have tried http, and now it complains no route to host. They are connected! Otherwise the damn pxe boot would fail. Every other machine on the same network can easily access the install server http area! -- 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 20 Fax: Int +46 8-31 42 23
On Fri, 24 Feb 2006, Roger Oberholtzer wrote:
On Fri, 2006-02-24 at 10:24 +0100, Dirk Schreiner wrote:
Hi @all,
Roger Oberholtzer schrieb:
Has anyone else on this list actually done EXACTLY this:
1. Install OpenSUSE10.0 on a server
I use a boxed SuSE 10 on a MS IIS Installation Server. (Simply copied the DVD-Content.)
2. Use the YAST to set up an install server for the OpenSUSE 10.0 disks.
3. Used PXE to boot a client so it can do an install of OpenSUSE 10.0 from this server?
I`m not using PXE, but as i followed the Thread, that`s not the problem ;-)
I prefer http instead of nfs, cause I never had trouble with http.
I have tried http, and now it complains no route to host. They are connected! Otherwise the damn pxe boot would fail. Every other machine on the same network can easily access the install server http area!
I can only repeat my advice to use a 10.1 beta boot CD to debug this. It has some network tools included in the initrd. Steffen
Roger, I had seen similar problems with SuSE 9.3 on AMD64 machines. It seems to be a problem of the network card/network drivers. Have a look at the pxelinux pages for options on how to treat the network card BIOS. For me, adding "keeppxe" to the boot kernel command line options helped. Yours, Volkmar On Thu, 23 Feb 2006, Roger Oberholtzer wrote:
Has anyone else on this list actually done EXACTLY this:
1. Install OpenSUSE10.0 on a server
2. Use the YAST to set up an install server for the OpenSUSE 10.0 disks.
3. Used PXE to boot a client so it can do an install of OpenSUSE 10.0 from this server?
Anyone? If so, did you do any updates to the OpenSUSE 10.0 on the server before setting up the install server?
My problem in this thread is not solved. I can't believe this does not work. But I have yet to see what I have done wrong.
Maybe I should post to the general group?
-- Roger Oberholtzer
-- Volkmar Glauche - Department of Neurology volkmar.glauche@uniklinik-freiburg.de Universitaetsklinikum Freiburg Phone 49(0)761-270-5331 Breisacher Str. 64 Fax 49(0)761-270-5416 79106 Freiburg
participants (6)
-
Dirk Schreiner -
Gunreben, Peter (Peter) -
Roger Oberholtzer -
Steffen Winterfeldt -
Uwe Gansert -
Volkmar Glauche