Netra t1 105 keeps going into init 0 everynight without reason

Question

I have Solaris 9 installed on a netra t1 105 which goes into half every night. I have turned off the power management and the logs in /var/adm/messages does not show anything unusual.
<div class="pre"><pre>Oct 19 14:16:25 dev-sol9 pseudo: &#91;ID 129642 kern.info&#93; pseudo-device: vol0
Oct 19 14:16:25 dev-sol9 genunix: &#91;ID 936769 kern.info&#93; vol0 is /pseudo/vol@0
Oct 19 14:17:22 dev-sol9 sendmail&#91;184&#93;: &#91;ID 702911 mail.alert&#93; unable to qualify my own domain name (dev-sol9) -- using short name
Oct 19 14:17:22 dev-sol9 sendmail&#91;183&#93;: &#91;ID 702911 mail.alert&#93; unable to qualify my own domain name (dev-sol9) -- using short name
Oct 20 09:21:30 dev-sol9 genunix: &#91;ID 540533 kern.notice&#93; ^MSunOS Release 5.9 Version Generic_118558-14 64-bit
Oct 20 09:21:30 dev-sol9 genunix: &#91;ID 943905 kern.notice&#93; Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.</pre></div>
<div class="pre"><pre>bash-2.05# eeprom
tpe-link-test?=true
scsi-initiator-id=7
keyboard-click?=false
keymap: data not available.
watchdog-timeout=65535
watchdog-enable?=false
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,-
cpci-probe-list=0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f
pcia-probe-list=1
pcib-probe-list=1,2,3
mfg-mode=off
diag-level=max
d7s-flipped?=false
#power-cycles=332
system-board-serial#: data not available.
system-board-date: data not available.
last-poweroff-cause=0
env-monitor=enabled
shutdown-temperature=72
warning-temperature=67
fcode-debug?=false
output-device=ttya
input-device=ttya
load-base=16384
auto-boot-retry?=false
use-boot-table?=false
boot-command=boot
auto-boot?=true
watchdog-reboot?=false
diag-file: data not available.
diag-device=net
boot-file: data not available.
boot-device=disk:b disk:a disk net
local-mac-address?=false
net-timeout=0
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
silent-mode?=false
use-nvramrc?=true
nvramrc=devalias ide-cdrom /pci@1f,0/pci@1/pci@1/ide@e/cdrom@2:f
security-mode=none
security-password: data not available.
security-#badlogins=1074790400
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
hardware-revision: data not available.
last-hardware-update: data not available.
diag-switch?=false</pre></div>

Answer 1

On second read Bill i see that as well.
This is going to be unrelated but your boot-device looks a bit strange as well. You are referencing different slices on the same disk, and then referencing the disk itself and then net.
boot-device=disk:b disk:a disk net
You would be ok with referencing disk and then net if the server is not mirrored. If the system is mirrored then you would want to reference that disk as well.
either :boot-device=disk net
or: boot-device=disk disk<number> net
But the next time it does it, you could try trying sync and trying to create a crash file. Once you have the crash files you can get these analysed.
As well as this pass the server through diagnostics 3 or 4 times and check the console outputs fro details.