From: magnus@kalimax.net
Date: Wed Apr 06 2005 - 10:41:46 EDT
Hi all,
I managed to solve the problem just in time. Thanks Rob for posting
"boot-image from..." :)
This is very weird! can someone explain why this happens?
Output for working Solaris 10 boot:
Executing last command: boot net -v
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v
38600 Using RARP/BOOTPARAMS...
Internet address is: 192.168.4.6
hostname: xxx
Requesting Ethernet address for: 192.168.4.5
Found 192.168.4.5 @ 0:0:86:1f:f7:92
root server: aaa (192.168.4.5)
root directory: /opt/install/media/Solaris_10/Solaris_10/Tools/Boot
Size: 0x704c8+0x1b8d2+0x2e1ba Bytes
Output for non-working Solaris 9 boot:
Executing last command: boot net -v
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v
Timeout waiting for ARP/RARP packet
29200 Using RARP/BOOTPARAMS...
Internet address is: 192.168.4.6
hostname: xxx
Found 192.168.4.5 @ 0:0:86:1f:f7:92
root server: aaa (192.168.4.5)
root directory: /opt/install/media/Solaris_9/Solaris_9/Tools/Boot
panic - boot: Could not mount filesystem.
Program terminated
ok
I then replaced /tftpboot/inetboot.SUN4U.Solaris_9-1 with
/tftpboot/inetboot.SUN4U.Solaris_10-1 from the Solaris 10 tree, renamed
/tftpboot/inetboot.SUN4U.Solaris_10-1 to
/tftpboot/inetboot.SUN4U.Solaris_9-1
Voila!
Now works.
inetboot.SUN4U.Solaris_9-1 was not corrupt (must be some internal
bootimage bug related to Netra-T1?).
Old bootimage: "inetboot.SUN4U.Solaris_9-1", 152376 bytes, "sum" 3662 and
298.
New bootimage: "inetboot.SUN4U.Solaris_9-1" (Sol 10 image), 214880 bytes,
"sum" 53512 and 420.
By the way I was using latest Solaris 9/04, u7
/Magnus
On Wed, 06 Apr 2005 14:55:04 , <magnus@kalimax.net> sent:
Hi all,
I'm going to install a couple of servers using Jumpstart, but I've
run into a problem so I'm kinda in panic.
This is the net boot:
Executing last command: boot net - install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: - install
Timeout waiting for ARP/RARP packet
29200 panic - boot: Could not mount filesystem.
Program terminated
ok
I've setup the jumpstart server on my x86 PC, which is Solaris 10
final with JET 3.7.3. Since I'm jumpstarting Solaris 9 onto a SPARC
machine, I had to do copy_solaris_media over NFS, since I can't mount
the SPARC ISO-CD1 on my x86. The install server seems to be OK, at
least it didn't complain during setup.
The log entry from sniffing the JS server:
3266 1:15:25.48103 aaa -> xxx WHO C port=33345
3267 1:15:25.48427 aaa -> xxx WHO C port=33345
3268 1:15:25.48636 aaa -> xxx WHO C port=33345
3269 1:15:25.48748 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3270 1:15:25.49044 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3271 1:15:25.49283 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3272 1:15:25.49394 aaa -> xxx PORTMAP R GETPORT port=32775
3273 1:15:25.49541 aaa -> xxx PORTMAP R GETPORT port=32775
3274 1:15:25.49673 aaa -> xxx PORTMAP R GETPORT port=32775
3275 1:15:25.49867 aaa -> xxx PORTMAP R GETPORT port=32775
/etc/bootparams:
xxx root=aaa:/opt/install/media/Solaris_9/Solaris_9/Tools/Boot
install=192.168.4.5:/opt/install/media/Solaris_9 boottype=:in
sysid_config=192.168.4.5:/opt/jet/Clients/xxx
install_config=192.168.4.5:/opt/jet rootopts=:rsize
32768
term=:vt100
Any idea what could be wrong? It stops at 29200, wheres Solaris 10
runs further up to 38000 something.
Jumpstarting the Solaris 10 onto the same SPARC works perfectly,
using the exact same configuration files.
/Magnus
parent.updatecursor();
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:30 EDT