netra t1 105 keeps going into init 0 everynight without reason

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: [ID 129642 kern.info] pseudo-device: vol0

Oct 19 14:16:25 dev-sol9 genunix: [ID 936769 kern.info] vol0 is /pseudo/vol@0

Oct 19 14:17:22 dev-sol9 sendmail[184]: [ID 702911 mail.alert] unable to qualify my own domain name (dev-sol9) -- using short name

Oct 19 14:17:22 dev-sol9 sendmail[183]: [ID 702911 mail.alert] unable to qualify my own domain name (dev-sol9) -- using short name

Oct 20 09:21:30 dev-sol9 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Version Generic_118558-14 64-bit

Oct 20 09:21:30 dev-sol9 genunix: [ID 943905 kern.notice] 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>

[2843 byte] By [jlim0930] at [2007-11-25 22:38:27]
# 1
have you actually tried physically uninstalling the power management packages?
stumoor at 2007-7-5 14:08:51 > top of Java-index,Sun Hardware,Other Sun Hardware...
# 2

... and I'm having a little difficulty understanding your description of the issue.

Does it actually go all the way down to the OK prompt, and you have to boot it to recover?

(that's what init 0 means)

If that is what you are seeing, then does it happen at the same time each day/night?

Bill at 2007-7-5 14:08:51 > top of Java-index,Sun Hardware,Other Sun Hardware...
# 3

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.

stumoor at 2007-7-5 14:08:51 > top of Java-index,Sun Hardware,Other Sun Hardware...
# 4
My question was more about the actual perceived issue. If it's dropping to OBP then it's not a power management problem. Note the input and output devices, for a system with LOM ? <b>man kbd</b>
Bill at 2007-7-5 14:08:51 > top of Java-index,Sun Hardware,Other Sun Hardware...
# 5
Yeah saw that. A sync if it happens again might help him if it shows anything in the crash dump.
stumoor at 2007-7-5 14:08:51 > top of Java-index,Sun Hardware,Other Sun Hardware...
# 6

when i come back to this machine every morning it is in the ok prompt status.

when i check the logs there is nothing listed as far as power management or any kind of faults.

so far this have been happening for 2 nights in a row after a fresh sol 9 installation

jlim0930 at 2007-7-5 14:08:51 > top of Java-index,Sun Hardware,Other Sun Hardware...
# 7

Good.Now I have a better understanding of what may be happening.

The symptoms are not suggestive of anything to do with power management.

As I hinted above, review the man pages for <u>kbd</u> and check on the connection of the cabling to your TTYa port.

Search these Hardware forums, using keyword "kbd".

Bill at 2007-7-5 14:08:51 > top of Java-index,Sun Hardware,Other Sun Hardware...