Thanks to.. Matthew Darcy Julie Peers Umesh Potbhare Zaigui Wang Especially Matthew for his on going help and Julie for solving the problem. ############################################ Hi Colin When your jumpstart calls for a boot device -normally c0t0d0s2 You will see on screen You must ensure c0t0d0s2 resides in machine otherwise fatal error occurs. Boot your system to single user and run format and see what number disk is Could be c1t0d0s2-that could be the error Come back if still confused Regards Julie ############################################ Soloution.... I added another disk to make sure that hardware path c0t0d0s2 was taken. I then re-tried the boot net - install and got the following error... fatal system fault: WARNING: Uncorrectable ECC Memory Error WARNING: Uncorrected SIMM at: J0303 Physical Address = (ASI:0x0)0x4000000 Watchdog Reset I replaced the memory and it is now working. ############################################ Some useful things to check from Matt.... thats a good way of doing it - that works to adding the mac to host name and then the hostname to ip in the same way hostname.hme0 sets the ip for hme0. I still think the problem is to do with the client not seeing the boot image. I am thinking..........but stuck at this minute, its hard with out a jumpstart server infront of me. -----Original Message----- From: Colin Haffenden [mailto:chaffend@msxi-euro.com] Sent: Wednesday, October 30, 2002 4:42 PM To: matthew.darcy@hp.com Subject: RE: Jumpstart fatal system Hi Matt, According to the sun blueprints by adding the ip address and hostname to /etc/hosts and mac address and hostname to /etc/ethers the add_install_client script will use these files to create the /etc/bootparams file and the Jumpstart server is now configured to supply a client with an IP Address. I agree that getting another sparc is not a good resolution. I'm having trouble getting a spare anyway! Thanks, Colin. >>> "DARCY,MATTHEW (HP-UnitedKingdom,ex2)" <matthew.darcy@hp.com> 10/30/02 04:18pm >>> Hi Colin, I think I notice something here. I am SURE you must have a profile for your machine, ie a profile that matches the the client name / hardware revision. this binds and IP to mac address, now I can't remember if this is needed to just boot the system or to boot and install the system, I think it is to boot the system ie. boot of the network, broadcasts mac address to network, jumpstart server picks it up and assigns an IP based on the mac address it has in its list, then allows it to mount the boot image, you shouldn't be able to mount the boot image without an IP address assigned the to mac address. Again this is from memory so I can't remember where you set the ip address, I think it is in the profile. I find it hard to believe that the response is try another sparc ???? if you read your first message, it boots but can't see the boot image so trys to reboot again. This does not suggest a hardware error to me. Matt. -----Original Message----- From: Colin Haffenden [mailto:chaffend@msxi-euro.com] Sent: Wednesday, October 30, 2002 4:10 PM To: matthew.darcy@hp.com Subject: RE: Jumpstart fatal system Matt, No problem your help is very much appreciated, also this is the first time I've setup jumpstart so all info is useful! Answers to your questions... 1). add_install_client -c, This I got from the sun blueprints, also the man page says that it is the server. 2) Where can I find the install list? 3) Both files seem ok and have relevant info. 4) the subnet in the sysidcfg file has the same subnet (255.255.255.0) but I haven't set the ip anywhere yet except by adding it to the jumpstart servers host file. 5) mac address is correct 6) mounted the /jumpstart directory with no problems from another server. 7) rebooted the machine checked all shares and still no joy. I did notice that the add_install_client adds a share for... /jumpstart/OS/Solaris_8_20-02/Solaris_8/Tools/Boot I had to remove this, re-share /jumpstart and re-run add_install_client otherwise it gave an error say a sub directory of /jumpstart was already being shared. I can't see anything relating to the client in syslog/messages. I'm getting a few messages from people saying try another sparc. I'm trying to "aquire" one at the moment to try that. I'll let you know how I get on. Thanks, Colin. >>> "DARCY,MATTHEW (HP-UnitedKingdom,ex2)" <matthew.darcy@hp.com> 10/30/02 03:24pm >>> couple of points, I don't have a jumpstart server at hand at this moment so a bit of this is from memory so sorry if it is teaching you to suck eggs. 1.) isn't add_install_client -c the client workstation name not the boot server ?? 2.) this isn't related to the workstation not net booting but do you have a sun4m install defined in your install list. 3.)manually check /etc/bootparams and /etc/ethers and make sure that the information matches what you expect. 4.)are you setting the client ip address that is on the same subnet as your jumpstart server 5.) make sure /etc/ethers has the correct client mac address. 6.) make sure NFS is working, try mounting the jumpstart share onto the jumpstart server via NFS for a test, ie onto /a for example 7.) make sure you have rebooted your jumpstart server AFTER you got the IP conflict when you where testing earlier. If I was at the other office I could help you with my own working jumpstart server but this is from memory, so hope some of its usefull. also check the syslog / meesages to see if you can see the client workstation doing anything on the jumpstart server ? Matt. -----Original Message----- From: Colin Haffenden [mailto:chaffend@msxi-euro.com] Sent: Wednesday, October 30, 2002 3:15 PM To: matthew.darcy@hp.com Subject: RE: Jumpstart fatal system Tried the boot -r and then boot net, same problem. the add_install_client i have done as follows.... # pwd /jumpstart/OS/Solaris_8_20-02/Solaris_8/Tools # ./add_install_client -c server01:/jumpstart -p server01:/jumpstart client01 sun4m making /tftpboot enabling tftp in /etc/inetd.conf updating /etc/bootparams copying inetboot to /tftpboot /etc/bootparams and /etc/ethers are populated and tftp is enabled in inetd.conf. Thanks, Colin. >>> "DARCY,MATTHEW (HP-UnitedKingdom,ex2)" <matthew.darcy@hp.com> 10/30/02 03:02pm >>> do t boot -r then a boot net the boot -r will rebuild your devices thus making sure it boots from the right hardware path, then boot net will just network boot it and ignore the install routine - so you can just tell if your workstation is failing on booting the network image OR the install routine. I am taking you have added the client to the jumpstart server with the "add_install_client" script ?? thus making sure /etc/ethers /etc/bootparams are populated with the client request, and tftp is enabled in inetd ??? Is NFS running on the jumpstart server ?? Matt -----Original Message----- From: Colin Haffenden [mailto:chaffend@msxi-euro.com] Sent: Wednesday, October 30, 2002 2:55 PM To: matthew.darcy@hp.com Subject: RE: Jumpstart fatal system Matthew, I shared my /jumpstart directory with the following command... # share -F nfs -o ro,anon=0 -d "Jumpstart Directory" /jumpstart # shareall I have been following the jumpstart sun blueprint. Also the client used to have the same ip address as my jumpstart server. When it boots I get an ip address conflict so it looks like my crossover connection is ok... Any more ideas? Thanks, Colin. >>> "DARCY,MATTHEW (HP-UnitedKingdom,ex2)" <matthew.darcy@hp.com> 10/30/02 02:50pm >>> looks like it can't see your boot server. do you have the boot images shared via nfs and are the share permisions set to anonymous ############################################ Original message.. ############################################ Hi, I am configuring and testing jumpstart for the first time. I have run the check script and all is ok. I am using a crossover cable between 2 sparc 20's. I am using Solaris 8. When I try the command... ok> boot net - install I get the following output... SPARCstation 20 (1 X 390Z50), No Keyboard ROM Rev, 2.15, 80MB memory installed, Serial #3465993. Ethernet address 8:0:20:20:75:a, Host ID: 73234e309 Rebooting with command: net - install Boot device: /iommu/sbus/ledma@f,200010/le@f,c00000 File and args: - install 20c00 SunOS Release 5.8 Version Generic_108528-13 32-bit Copyright 1983-2001 Sun Microsytems, Inc. All rights reserved. whoami: no domain name Configuring /dev and /devices fatal system fault: Watchdog Reset Type help for more information ok Does anyone have any idea what this means and what I can do about it? Thanks in advance, Colin ############################################ _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Thu Oct 31 04:15:45 2002
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:57 EST