The beautiful dog chair that could count right up to 0x24000.

[reddragdiva]

I'm having severe problems net booting Sun machines.

We have two identical Netra T1-105 here. Call them box1 and box2. We want to upgrade them from Solaris 7 to Solaris 9. So we set up a boot server on box1 using the Solaris 9 12/02 CDs and installed box2 from it. This worked fine.

Now I've set up a boot server on box2 to upgrade or reinstall box1 (and various other boxes) from. It doesn't seem to work. When you do boot net - install on box1, it comes up with:

box1 # reboot "net - install"
Jan 12 15:20:50 box1 reboot: rebooted by root
/usr/opt/SUNWmd/sbin/mdlogd: going down on signal 15
/usr/opt/SUNWmd/sbin/mdlogd: going down on signal 15
Jan 12 15:20:50 box1 snmpdx: received signal 15
Jan 12 15:20:50 box1 rpcbind: rpcbind terminating on signal.
Jan 12 15:20:50 box1 syslogd: going down on signal 15
syncing file systems... done
rebooting...
Resetting ... 

Executing last command: boot net - install                            
Firmware Password: 
Boot device: /pci@1f,0/pci@1,1/network@1,1  File and args: - install
24000 boot: cannot open kernel/unix
Enter filename [kernel/unix]: 
boot: cannot open kernel/unix
Enter filename [kernel/unix]: 
boot: cannot open kernel/unix
Enter filename [kernel/unix]: 

Nothing will shift it from there. Enter anything you like, it'll just repeat the error message that it can't open it.

In the PROM on box1, boot-file is set to blank, as it should be. Haven't checked diag-switch.

I confirmed that rpc.bootparamd and in.tftpd are running on box2. I have also accessed box2 by tftp and NFS to check it's possible. Here are the contents of /tftpboot:

box2 # ls -l /tftpboot
total 296
lrwxrwxrwx   1 root     other         26 Jan 11 02:01 AC150007 -> inetboot.SUN4U.Solaris_9-1
lrwxrwxrwx   1 root     other         26 Jan 11 02:01 AC150007.SUN4U -> inetboot.SUN4U.Solaris_9-1
-rwxr-xr-x   1 root     other     131424 Jan 11 02:01 inetboot.SUN4U.Solaris_9-1
-rw-r--r--   1 root     other        314 Jan 11 02:01 rm.172.21.0.7
lrwxrwxrwx   1 root     other          1 Jan 11 02:01 tftpboot -> . 

We don't have other machines spare to test on at this time, nor can we easily reboot box2 for now.

As far as I can tell from checking the Usenet archive, the "boot: cannot open kernel/unix" message means the boot kernel sent over doesn't actually support the hardware in question. But that doesn't explain how I got box2 installed from box1 using Sol9 12/02 in the first place — the machines are identical.

Any ideas? I found one person on the Web with this precise problem, but he didn't get any responses. (I've emailed him to ask in any case.)

I must run a snoop on the subnet. (Traffic for and from box1 only, that subnet has the web servers on it!) I've also downloaded the Sol9 04/04 CDs in the meantime, though I'm not sure trying again with those will help and it's a bit much work for the sake of it.

Update: Now working after rebooting the boot/install server.

Comments

[http://users.livejournal.com/_nicolai_/]

For netboot it must also be shared with anon=0 in the mount options.
You'll be wanting a readonly export too.

[http://users.livejournal.com/_nicolai_/]

I mean for jumpstart net install it must be shared with anon=0

[reddragdiva]

o=ro,anon=0 - yep, as per TFM.

[http://users.livejournal.com/_nicolai_/]

Does the architecture you specified with add_install_client (or wrapper) match that of the actual machine and are boot bits for that architecture present on the server? If another machine of same architecture can boot from the server, then the latter is probably true.

[reddragdiva]

It SHOULD be. (Netra T1-105 is sun4u.) There aren't any other machines on that subnet I can do this to at this moment, annoyingly.