So my w2100z is fully installed, but not fully functional. I learned some valuable lessons along the way, and I'm not yet done. Things brought back to the surface:

• Don't forget to edit your menu.lst if your system is headless. I did it for the install media, I should do it for the system.
• If you break the root mirror, that can leave your menu.lst pointing to the wrong side of the pool. I.e., there are I expect a copy of the boot targets for each side of the mirror. Combine these two lessons and you have a system that looks dead.
• Just because you think the Sun Ray Server install code rocks and it has always been easy, don't forget to backup your settings.

And the big one, sometimes it is better to go to bed than futz with things just a bit longer.

I've tried both Sun Ray Software 4 Update 3 Beta for Solaris 10 5/08 X86 and Sun Ray Software 4 09/07. In both cases I've got the 26D error. I know that the firmware on the DTU is being changed between releases and the server software knows about the DTU.

I've tried the following things to get this working:

• Read the manual, restart the installation.
• Opened up my netservices via Sun Ray on OpenSolaris Work-around. - even though my system should have had the fix for this in place.
• Not made heads or tails over this entry Sun Ray on OpenSolaris 2008.05.
• Clear the Xserver for a Headless Sun Ray Servers (OSD 26) - which is by the way, a very good example of how to clear up confusion in a manual.

And I left it there with the last one. I'm about to restart. I think that perhaps fixing my menu.lst has caused this issue or I have to face the fact that I upgraded to too modern a build. But since I never had this problem before and I don't have my hands on the prior configurations, I'll try to get it working.

Strike part of that, I do have /etc/dt/config archived off and it shows I never did the Xserver thing:

[th199096@warlock config]> ls -la
total 26
drwxr-xr-x   2 root     other          6 Sep 25 12:41 .
drwxr-xr-x   3 root     other          3 Mar 29  2008 ..
-r--r--r--   1 root     sys         1577 Aug  1  2007 README.SUNWut
lrwxrwxrwx   1 root     root          34 Sep 29 02:58 Xconfig -> /tmp/SUNWut/config/xconfig/Xconfig
-r--r--r--   1 root     root        5868 Mar 29  2008 Xconfig.SUNWut.prototype
lrwxrwxrwx   1 root     root          35 Sep 29 02:58 Xservers -> /tmp/SUNWut/config/xconfig/Xservers

Okay, I fixed that back out and I told grub not to boot to the console. But I didn't tell eeprom(1M):

[root@warlock ~]> eeprom
ata-dma-enabled=1
atapi-cd-dma-enabled=1
ttyb-rts-dtr-off=false
ttyb-ignore-cd=true
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttyb-mode=9600,8,n,1,-
ttya-mode=9600,8,n,1,-
lba-access-ok=1
prealloc-chunk-size=0x2000
keyboard-layout=US-English
console=ttya
boot-file=bootadm: kernel command on line 64 not recognized.
boot-args=bootadm: kernel command on line 64 not recognized.
[root@warlock ~]> eeprom console=text
[root@warlock ~]>

By the way, if this is horked, so am I. :->

Okay, I'm horked. I have to come up in failsafe mode. Now how do I fix my eeprom? Luckily, is it?, I've had to do this in the past - eeprom hosed on an x86. And it has the sed command I will need because I refuse to learn how to configure my terminal! And I've saved above what the real value should be!

# pwd
/a/boot/solaris
# sed 's/text/ttya/' bootenv.rc > xxx
# diff bootenv.rc xxx
39c39
< setprop console 'text'
---
> setprop console 'ttya'
# cp xxx bootenv.rc
# reboot
Creating boot_archive for /a

So I'm not getting X on the headed headless server (i.e., I've attached a monitor). I get output there until the OS takes over.

What is in my /var/dt/Xerrors?

Fatal server error:
could not open default font 'fixed'
XIO:  fatal IO error 146 (Connection refused) on X server ":2.0"^M
      after 0 requests (0 known processed) with 0 events remaining.^M
failed to set default font path '/usr/openwin/lib/X11/fonts/Type1/,/usr/openwin/lib/X11/fonts/Type1/sun/,/usr/openwin/lib/X11/fonts/F3bitmaps/,/
usr/openwin/lib/X11/fonts/Speedo/,/usr/openwin/lib/X11/fonts/misc/,/usr/openwin/lib/X11/fonts/75dpi/,/usr/openwin/lib/X11/fonts/100dpi/,/usr/ope
nwin/lib/X11/fonts/TrueType'
One of the directories in the list above does not exist
or it does not contain a valid 'fonts.dir' file

Okay, lets take care of that! All of them existed and none had a valid 'fonts.dir' file. And now:

Fatal server error:
could not open default font 'fixed'
XIO:  fatal IO error 146 (Connection refused) on X server ":2.0"^M
      after 0 requests (0 known processed) with 0 events remaining.^M

I'm really coming to suspect X is the thing horked on this system.

Notes

It looks like something, perhaps eeprom touched my menu.lst and added a new and default setting for me:

title Diagnostic Partition
        rootnoverify (hd0,0)
        chainloader +1
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
title Solaris bootenv rc
findroot pool_rpool
kernel$ /platform/i86pc/kernel/$ISADIR/unix -B console=ttya bootadm: kernel command on line 64 not recognized.
-B bootadm: kernel command on line 64 not recognized.
module$ /platform/i86pc/$ISADIR/boot_archive
#---------------------END BOOTADM--------------------
#BOOTADM RC SAVED DEFAULT: 0

Which yields:

krtld: Unused kernel arguments: `bootadm: kernel command on line 64 not recognized.'.
SunOS Release 5.11 Version snv_99 64-bit
Copyright 1983-2008 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
NOTICE: mount: not a UFS magic number (0x0)
Cannot mount root on /ramdisk:a fstype ufs

panic[cpu0]/thread=fffffffffbc293a0: vfs_mountroot: cannot mount root

fffffffffbc48dc0 genunix:vfs_mountroot+356 ()
fffffffffbc48df0 genunix:main+e6 ()
fffffffffbc48e00 unix:_locore_start+92 ()

skipping system dump - no dump device configured
SunOS Release 5.11 Version snv_99 64-bit
Copyright 1983-2008 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Hostname: warlock
Reading ZFS config: done.
Mounting ZFS filesystems: (8/8)

I've got the head on it, so I'm going to reinstall and see if I can at least get X working on it.