HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

Persistent POST (booting) System Alert message

 
SOLVED
Go to solution
Charles Egbon
Regular Advisor

Persistent POST (booting) System Alert message

Hi Guys,

Good Morning/Noon/Afternoon/Evening & Night!
Please, on my N-Class, I upgraded the CPU to eight (maximum) with a firmware update of 43.43. and Hp-ux 11.11. I have installed PHKL_30512 and other relevant patches.
Anytime I reboot the server, during the power on self test, there is always this “System Alert” message that keep on coming. The message has underneath ‘A/a: ack read of this entry….’ I normally strike key ‘a’ on the keyboard and the booting process will continue, however if I don’t strike key ‘a’ after some few minutes, the booting process will also continue. The excerpt of the alert message is thus:

ALERT LEVEL: 6 =Boot Possible, pending failure – action required

REASON FOR ALERT
SOURCE: 3 = PDH
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

Please, what must I do to solve this problem?

Thanks in antic
18 REPLIES 18
Eric Antunes
Honored Contributor

Re: Persistent POST (booting) System Alert message

Hi Charles,

Isn't there more info in /var/adm/syslog/syslog.log? Can you post the last 20 lines of it?

Best Regards,

Eric Antunes
Each and every day is a good day to learn.
RAC_1
Honored Contributor

Re: Persistent POST (booting) System Alert message

If I remember correctly PDH is one of the tests that is done at boot time. You may also want to do a SL on GSP and see if there are any errors.

Also following doc explains the details about PDH.
http://docs.hp.com/en/5990-8170A/ch05s28.html

If possible, you can get HP involved.

Anil
There is no substitute to HARDWORK
Andrew Rutter
Honored Contributor

Re: Persistent POST (booting) System Alert message

hi,

Go into the gsp (control b)and read the error logs.
You will continue to get the message until the system is happy you have read and the error logs.
You might need to read the last 6-10 entries to clear the error and stop the amber light flashing on the front of the server if it is.

If that doesnt clear it then check the hardware is all verified correctly proc/mem. Also You would have needed to install the processor support modules for the extra cpu's aswell.

Andy
Charles Egbon
Regular Advisor

Re: Persistent POST (booting) System Alert message

Hi Friends,

Thanks for your suggestions. I have been going through the log and I just can't figure the exact cause of the problem.
Here is the content of the syslog.log:

Jan 10 15:39:40 fsbnode1 syslogd: restart

Jan 10 15:39:40 fsbnode1 vmunix: gate64: sysvec_vaddr = 0xc0002000 for 2 pages

Jan 10 15:39:40 fsbnode1 vmunix: NOTICE: autofs_link(): File system was register

ed at index 3.

Jan 10 15:39:40 fsbnode1 vmunix: NOTICE: cachefs_link(): File system was registe

red at index 5.

Jan 10 15:39:40 fsbnode1 vmunix: NOTICE: nfs3_link(): File system was registered

at index 6.

Jan 10 15:39:40 fsbnode1 vmunix: 0 sba

Jan 10 15:39:40 fsbnode1 vmunix: 0/0 lba

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/0/0 btlan

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/1/0 c720

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/1/0.1 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/1/0.1.0 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/1/0.3 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/1/0.3.0 stape

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/1/0.7 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/1/0.7.0 sctl

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/2/0 c720

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/2/0.6 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/2/0.6.0 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/2/0.7 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/2/0.7.0 sctl

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/2/1 c720

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/2/1.6 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/2/1.6.0 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/2/1.7 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/2/1.7.0 sctl

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/4/0 asio0

Jan 10 15:39:40 fsbnode1 vmunix: 0/0/5/0 asio0

Jan 10 15:39:40 fsbnode1 vmunix: 0/1 lba

Jan 10 15:39:40 fsbnode1 vmunix: 0/2 lba

Jan 10 15:39:40 fsbnode1 vmunix: 0/2/0/0 td

Jan 10 15:39:40 fsbnode1 vmunix: td: claimed Tachyon XL2 Fibre Channel Mass Stor

age card at 0/2/0/0

Jan 10 15:39:40 fsbnode1 vmunix: 0/2/0/0.1 fcp

Jan 10 15:39:40 fsbnode1 vmunix: 0/2/0/0.1.3.0.0 fcparray

Jan 10 15:39:40 fsbnode1 vmunix: 0/2/0/0.1.3.0.0.0 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/2/0/0.1.3.0.0.0.0 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 0/2/0/0.1.3.0.0.0.1 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 0/2/0/0.1.3.0.0.0.2 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 0/2/0/0.1.3.255.0 fcpdev

Jan 10 15:39:40 fsbnode1 vmunix: 0/2/0/0.1.3.255.0.0 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/2/0/0.1.3.255.0.0.0 sctl

Jan 10 15:39:40 fsbnode1 vmunix: 0/4 lba

Jan 10 15:39:40 fsbnode1 vmunix: 0/4/0/0 btlan

Jan 10 15:39:40 fsbnode1 vmunix: 0/5 lba

Jan 10 15:39:40 fsbnode1 vmunix: 0/5/0/0 btlan

Jan 10 15:39:40 fsbnode1 vmunix: 0/8 lba

Jan 10 15:39:40 fsbnode1 vmunix: 0/8/0/0 igelan

Jan 10 15:39:40 fsbnode1 vmunix: 0/10 lba

Jan 10 15:39:40 fsbnode1 vmunix: 0/10/0/0 c720

Jan 10 15:39:40 fsbnode1 vmunix: 0/10/0/0.3 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/10/0/0.3.0 stape

Jan 10 15:39:40 fsbnode1 vmunix: 0/10/0/0.7 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/10/0/0.7.0 sctl

Jan 10 15:39:40 fsbnode1 vmunix: 0/12 lba

Jan 10 15:39:40 fsbnode1 vmunix: 0/12/0/0 c720

Jan 10 15:39:40 fsbnode1 vmunix: 0/12/0/0.0 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/12/0/0.0.0 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 0/12/0/0.0.2 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 0/12/0/0.0.3 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 0/12/0/0.7 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 0/12/0/0.7.0 sctl

Jan 10 15:39:40 fsbnode1 vmunix: 1 sba

Jan 10 15:39:40 fsbnode1 vmunix: 1/0 lba

Jan 10 15:39:40 fsbnode1 vmunix: 1/0/0/0 td

Jan 10 15:39:40 fsbnode1 vmunix: td: claimed Tachyon XL2 Fibre Channel Mass Stor

age card at 1/0/0/0

Jan 10 15:39:40 fsbnode1 vmunix: 1/2 lba

Jan 10 15:39:40 fsbnode1 vmunix: 1/2/0/0 igelan

Jan 10 15:39:40 fsbnode1 vmunix: 1/4 lba

Jan 10 15:39:40 fsbnode1 vmunix: 1/4/0/0 c720

Jan 10 15:39:40 fsbnode1 vmunix: 1/4/0/0.1 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 1/4/0/0.1.0 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 1/4/0/0.1.2 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 1/4/0/0.1.3 sdisk

Jan 10 15:39:40 fsbnode1 vmunix: 1/4/0/0.7 tgt

Jan 10 15:39:40 fsbnode1 vmunix: 1/4/0/0.7.0 sctl

Jan 10 15:39:40 fsbnode1 vmunix: 1/8 lba

Jan 10 15:39:40 fsbnode1 vmunix: 1/10 lba

Jan 10 15:39:40 fsbnode1 vmunix: 1/10/0/0 btlan

Jan 10 15:39:40 fsbnode1 vmunix: 1/12 lba

Jan 10 15:39:40 fsbnode1 vmunix: 1/12/0/0 btlan

Jan 10 15:39:40 fsbnode1 vmunix: 32 pbc

Jan 10 15:39:40 fsbnode1 vmunix: 33 processor

Jan 10 15:39:40 fsbnode1 vmunix: 36 pbc

Jan 10 15:39:40 fsbnode1 vmunix: 37 processor

Jan 10 15:39:40 fsbnode1 vmunix: 40 pbc

Jan 10 15:39:40 fsbnode1 vmunix: 41 processor

Jan 10 15:39:40 fsbnode1 vmunix: 44 pbc

Jan 10 15:39:40 fsbnode1 vmunix: 45 processor

Jan 10 15:39:40 fsbnode1 vmunix: 96 pbc

Jan 10 15:39:40 fsbnode1 vmunix: 97 processor

Jan 10 15:39:40 fsbnode1 vmunix: 100 pbc

Jan 10 15:39:40 fsbnode1 vmunix: 101 processor

Jan 10 15:39:40 fsbnode1 vmunix: 104 pbc

Jan 10 15:39:40 fsbnode1 vmunix: 105 processor

Jan 10 15:39:40 fsbnode1 vmunix: 108 pbc

Jan 10 15:39:40 fsbnode1 vmunix: 109 processor

Jan 10 15:39:40 fsbnode1 vmunix: 192 memory

Jan 10 15:39:40 fsbnode1 vmunix: btlan: Initializing 10/100BASE-TX card at 0/0/0

/0....

Jan 10 15:39:40 fsbnode1 vmunix:

Jan 10 15:39:40 fsbnode1 vmunix: System Console is on the Built-In Serial In

terface

Jan 10 15:39:40 fsbnode1 vmunix: igelan4: INITIALIZING HP A6825-60101 PCI 1000Ba

se-T Adapter at hardware path 1/2/0/0

Jan 10 15:39:40 fsbnode1 vmunix: btlan: Initializing 10/100BASE-TX card at 1/10/

0/0....

Jan 10 15:39:40 fsbnode1 vmunix: btlan: Initializing 10/100BASE-TX card at 1/12/

0/0....

Jan 10 15:39:40 fsbnode1 vmunix: btlan: Initializing 10/100BASE-TX card at 0/4/0

/0....

Jan 10 15:39:40 fsbnode1 vmunix: btlan: Initializing 10/100BASE-TX card at 0/5/0

/0....

Jan 10 15:39:40 fsbnode1 vmunix: igelan3: INITIALIZING HP A6825-60101 PCI 1000Ba

se-T Adapter at hardware path 0/8/0/0

Jan 10 15:39:40 fsbnode1 vmunix: Logical volume 64, 0x3 configured as ROOT

Jan 10 15:39:40 fsbnode1 vmunix: Logical volume 64, 0x2 configured as SWAP

Jan 10 15:39:40 fsbnode1 vmunix: Logical volume 64, 0x2 configured as DUMP

Jan 10 15:39:40 fsbnode1 vmunix: Swap device table: (start & size given in

512-byte blocks)

Jan 10 15:39:40 fsbnode1 vmunix: entry 0 - major is 64, minor is 0x2; st

art = 0, size = 36864000

Jan 10 15:39:40 fsbnode1 vmunix: Dump device table: (start & size given in

1-Kbyte blocks)

Jan 10 15:39:40 fsbnode1 vmunix: entry 0000000000000000 - major is 31, m

inor is 0x16000; start = 314208, size = 18432000

Jan 10 15:39:40 fsbnode1 vmunix: Starting the STREAMS daemons-phase 1

Jan 10 15:39:40 fsbnode1 vmunix: Create STCP device files

Jan 10 15:39:40 fsbnode1 vmunix: Starting the STREAMS daemons-phase 2

Jan 10 15:39:40 fsbnode1 vmunix: $Revision: vmunix: vw: -proj

selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80

_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $

Jan 10 15:39:40 fsbnode1 vmunix: Memory Information:

Jan 10 15:39:40 fsbnode1 vmunix: physical page size = 4096 bytes, logical pa

ge size = 4096 bytes

Jan 10 15:39:40 fsbnode1 vmunix: Physical: 16777216 Kbytes, lockable: 129619

96 Kbytes, available: 14887280 Kbytes

Jan 10 15:39:40 fsbnode1 vmunix:

Jan 10 15:39:42 fsbnode1 nettl[842]: nettl starting up.

Jan 10 15:39:50 fsbnode1 rpcbind: check_netconfig: Found CLTS loopback transport

Jan 10 15:39:50 fsbnode1 rpcbind: check_netconfig: Found COTS loopback transport

Jan 10 15:39:50 fsbnode1 rpcbind: check_netconfig: Found COTS ORD loopback trans

port

Jan 10 15:39:50 fsbnode1 rpcbind: init_transport: check binding for udp

Jan 10 15:39:50 fsbnode1 rpcbind: init_transport: check binding for tcp

Jan 10 15:39:50 fsbnode1 rpcbind: init_transport: check binding for ticlts

Jan 10 15:39:50 fsbnode1 rpcbind: init_transport: check binding for ticotsord

Jan 10 15:39:50 fsbnode1 rpcbind: init_transport: check binding for ticots

Jan 10 15:39:52 fsbnode1 inetd[1040]: Reading configuration

Jan 10 15:39:52 fsbnode1 inetd[1040]: ftp/tcp: Added service, server /usr/lbin/f

tpd

Jan 10 15:39:52 fsbnode1 inetd[1040]: telnet/tcp: Added service, server /usr/lbi

n/telnetd

Jan 10 15:39:52 fsbnode1 inetd[1040]: tftp/udp: Added service, server /usr/lbin/

tftpd

Jan 10 15:39:52 fsbnode1 inetd[1040]: login/tcp: Added service, server /usr/lbin

/rlogind

Jan 10 15:39:52 fsbnode1 inetd[1040]: shell/tcp: Added service, server /usr/lbin

/remshd

Jan 10 15:39:52 fsbnode1 inetd[1040]: exec/tcp: Added service, server /usr/lbin/

rexecd

Jan 10 15:39:52 fsbnode1 inetd[1040]: ntalk/udp: Added service, server /usr/lbin

/ntalkd

Jan 10 15:39:52 fsbnode1 inetd[1040]: ident/tcp: Added service, server /usr/lbin

/identd

Jan 10 15:39:52 fsbnode1 inetd[1040]: printer/tcp: Added service, server /usr/sb

in/rlpdaemon

Jan 10 15:39:52 fsbnode1 inetd[1040]: daytime/tcp: Added service, server interna

l

Jan 10 15:39:52 fsbnode1 inetd[1040]: daytime/udp: Added service, server interna

l

Jan 10 15:39:52 fsbnode1 inetd[1040]: time/tcp: Added service, server internal

Jan 10 15:39:52 fsbnode1 inetd[1040]: echo/tcp: Added service, server internal

Jan 10 15:39:52 fsbnode1 inetd[1040]: echo/udp: Added service, server internal

Jan 10 15:39:52 fsbnode1 inetd[1040]: discard/tcp: Added service, server interna

l

Jan 10 15:39:52 fsbnode1 inetd[1040]: discard/udp: Added service, server interna

l

Jan 10 15:39:52 fsbnode1 inetd[1040]: chargen/tcp: Added service, server interna

l

Jan 10 15:39:52 fsbnode1 inetd[1040]: chargen/udp: Added service, server interna

l

Jan 10 15:39:52 fsbnode1 inetd[1040]: kshell/tcp: Added service, server /usr/lbi

n/remshd

Jan 10 15:39:52 fsbnode1 inetd[1040]: klogin/tcp: Added service, server /usr/lbi

n/rlogind

Jan 10 15:39:52 fsbnode1 inetd[1040]: dtspc/tcp: Added service, server /usr/dt/b

in/dtspcd

Jan 10 15:39:52 fsbnode1 inetd[1040]: swat/tcp: Added service, server /opt/samba

/bin/swat

Jan 10 15:39:52 fsbnode1 inetd[1040]: registrar/tcp: Added service, server /etc/

opt/resmon/lbin/registrar

Jan 10 15:39:52 fsbnode1 inetd[1040]: recserv/tcp: Added service, server /usr/lb

in/recserv

Jan 10 15:39:52 fsbnode1 inetd[1040]: hacl-probe/tcp: Added service, server /opt

/cmom/lbin/cmomd

Jan 10 15:39:52 fsbnode1 inetd[1040]: hacl-cfg/udp: Added service, server /usr/l

bin/cmclconfd

Jan 10 15:39:52 fsbnode1 inetd[1040]: hacl-cfg/tcp: Added service, server /usr/l

bin/cmclconfd

Jan 10 15:39:52 fsbnode1 inetd[1040]: instl_boots/udp: Added service, server /op

t/ignite/lbin/instl_bootd

Jan 10 15:39:52 fsbnode1 inetd[1040]: omni/tcp: Added service, server /opt/omni/

/lbin/inet

Jan 10 15:39:52 fsbnode1 inetd[1040]: rpc.cmsd/udp: Added service, server /usr/d

t/bin/rpc.cmsd

Jan 10 15:39:52 fsbnode1 inetd[1040]: rpc.ttdbserver/tcp: Added service, server

/usr/dt/bin/rpc.ttdbserver

Jan 10 15:39:52 fsbnode1 inetd[1040]: Thru with configuration

Jan 10 15:39:52 fsbnode1 inetd[1040]: Configuration complete

Jan 10 15:40:09 fsbnode1 cimserver[1409]: Listening on HTTPS port 5989.

Jan 10 15:40:09 fsbnode1 cimserver[1409]: Listening on local connection socket.

Jan 10 15:40:09 fsbnode1 cimserver[1409]: Started HP WBEM Services for HP-UX ver

sion A.01.05.08.

Jan 10 15:40:09 fsbnode1 pwgrd: Started at Mon Jan 10 15:40:09 2005, pid = 1446

Jan 10 15:40:15 fsbnode1 diagmond[1506]: started

Jan 10 15:40:15 fsbnode1 /usr/sbin/envd[1509]: restart, and read the configurati

on file

Jan 10 15:40:21 fsbnode1 syslog: ArmServr Started

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1838]: Setting STREAMS-HEAD high water v

alue to 131072.

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1844]: nfsd do_one mpctl succeeded: ncpu

s = 8.

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1844]: nfsd do_one pmap 2

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1844]: nfsd do_one pmap 3

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1846]: nfsd do_one bind 0

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1847]: nfsd do_one bind 1

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1849]: nfsd do_one bind 2

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1850]: nfsd do_one bind 3

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1852]: nfsd do_one bind 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1854]: nfsd do_one bind 5

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1844]: nfsd do_one bind 7

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1855]: nfsd do_one bind 6

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1850]: Return from t_optmgmt(XTI_DISTRIB

UTE) 0

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1849]: Return from t_optmgmt(XTI_DISTRIB

UTE) 0

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1850]: nfsd 3 1 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1856]: nfsd 3 0 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1849]: nfsd 2 1 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1857]: nfsd 2 0 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1854]: Return from t_optmgmt(XTI_DISTRIB

UTE) 0

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1855]: Return from t_optmgmt(XTI_DISTRIB

UTE) 0

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1846]: Return from t_optmgmt(XTI_DISTRIB

UTE) 0

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1858]: nfsd 5 0 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1854]: nfsd 5 1 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1844]: Return from t_optmgmt(XTI_DISTRIB

UTE) 0

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1852]: Return from t_optmgmt(XTI_DISTRIB

UTE) 0

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1855]: nfsd 6 1 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1859]: nfsd 6 0 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1846]: nfsd 0 1 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1860]: nfsd 0 0 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1844]: nfsd 7 1 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1861]: nfsd 7 0 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1847]: Return from t_optmgmt(XTI_DISTRIB

UTE) 0

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1862]: nfsd 4 0 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1852]: nfsd 4 1 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1847]: nfsd 1 1 sock 4

Jan 10 15:40:49 fsbnode1 /usr/sbin/nfsd[1863]: nfsd 1 0 sock 4

Jan 10 15:40:51 fsbnode1 prngd[1913]: prngd 0.9.26 (12 Jul 2002) started up for

user root

Jan 10 15:40:51 fsbnode1 prngd[1913]: have 6 out of 2048 filedescriptors open

Jan 10 09:40:51 fsbnode1 krsd[1917]: Delay time is 300 seconds

Jan 10 17:29:14 fsbnode1 LVM[23413]: /sbin/lvlnboot -v vg00

Jan 10 17:29:14 fsbnode1 LVM[23416]: /sbin/lvlnboot -v vg00

Jan 10 17:29:14 fsbnode1 LVM[23422]: lvlnboot -v

Jan 10 17:29:15 fsbnode1 LVM[23435]: /sbin/lvlnboot -v vg00

Jan 10 17:29:15 fsbnode1 LVM[23438]: /sbin/lvlnboot -v vg00

Jan 11 09:06:42 fsbnode1 ftpd[11573]: FTP LOGIN FROM 10.91.1.90 [10.91.1.90], or

acle

Jan 11 09:29:39 fsbnode1 ftpd[11573]: exiting on signal 14

Jan 11 15:02:52 fsbnode1 LVM[16177]: /sbin/lvlnboot -v vg00

Jan 11 15:02:52 fsbnode1 LVM[16180]: /sbin/lvlnboot -v vg00

Jan 11 15:02:52 fsbnode1 LVM[16186]: lvlnboot -v

Jan 11 19:25:17 fsbnode1 ftpd[19286]: FTP LOGIN FROM 10.91.1.90 [10.91.1.90], or

acle

Jan 11 19:25:50 fsbnode1 ftpd[19286]: FTP session closed

Jan 11 19:40:54 fsbnode1 su: - td oracle--root

Jan 11 19:41:24 fsbnode1 su: + td oracle-root

Jan 11 19:41:14 fsbnode1 su: - td oracle--root

Eric Antunes
Honored Contributor

Re: Persistent POST (booting) System Alert message

Hi Charles,

Your syslog.log seems to be normal...

Please do:

#ioscan -fn > ioscan_result.txt

and attach the ioscan_result.txt here when replying.

Best Regards,

Eric Antunes
Each and every day is a good day to learn.
Charles Egbon
Regular Advisor

Re: Persistent POST (booting) System Alert message

Hi Eric,

Thanks for your suggestions. The ioscan details are attached herewith.

Cheers.

Charles
Eric Antunes
Honored Contributor

Re: Persistent POST (booting) System Alert message

Charles,

You have a hardware problem with your tape drive. From ioscan:

...
target 1 0/0/1/0.3 tgt NO_HW DEVICE
tape 0 0/0/1/0.3.0 stape NO_HW DEVICE HP C1537A
/dev/rmt/0m /dev/rmt/c0t3d0BESTn
/dev/rmt/0mb /dev/rmt/c0t3d0BESTnb
/dev/rmt/0mn /dev/rmt/c0t3d0DDS
/dev/rmt/0mnb /dev/rmt/c0t3d0DDSb
/dev/rmt/c0t3d0BEST /dev/rmt/c0t3d0DDSn
/dev/rmt/c0t3d0BESTb /dev/rmt/c0t3d0DDSnb
...

When you see NO_HW (NO HardWare) in the "S/W State" column it is because the hardware is no longer responding... So if you'll need the tape for backups, you have to call HP support to substitute it.

Best Regards,

Eric
Each and every day is a good day to learn.
Charles Egbon
Regular Advisor

Re: Persistent POST (booting) System Alert message

Eric,

Yea! once in while, I normally swap that tape drive to do backup in another similar machine.
But, I think that is absolutely by the way. I don't think that should be the cause of the problem.
Or what do you think?

Cheers.

Charles.
Eric Antunes
Honored Contributor

Re: Persistent POST (booting) System Alert message

Yes, that maybe the cause of you issue. Aren't those 2 servers in the same network? If yes, you can use the tape of a remote server in the same network with SAM, for example...

Best Regards,

Eric Antunes
Each and every day is a good day to learn.
Charles Egbon
Regular Advisor

Re: Persistent POST (booting) System Alert message

Eric,

I rebooted the system with the tape installed and the Alert message still comes on. I reboot again, same thing.

Thanks ...

Charles
Andrew Rutter
Honored Contributor

Re: Persistent POST (booting) System Alert message

hi charles,

As I said earlier, did you read the logs in the gsp and what did they say?
control B
SL
E
N to filter

This may give you an indication to any problem.

And until you have read them you will get the error.

Andy
Eric Antunes
Honored Contributor

Re: Persistent POST (booting) System Alert message

Yes,

Check GSP logs like Andy said, acknowledge the error messages and restart it. If it continues after that, you must see if the tape drive is well connected...
Each and every day is a good day to learn.
Cheryl Griffin
Honored Contributor

Re: Persistent POST (booting) System Alert message

Check the GSP console log but also you stated there is one message that is underneath another message on the screen. Try disabling these Alert Messages from displaying on the console, as outlined in ITRC Knowledge Base document KBRC00007966. Reboot and check the console again during boot for the messages that were overwritten by Alerts.
"Downtime is a Crime."
Charles Egbon
Regular Advisor

Re: Persistent POST (booting) System Alert message

Hi Guys,

Thanks for all your suggestion. I have check the GSP console log again and again. I think a fair option is really to disable this alert messages. Cheryl said something about that. But I was not able to exactly get the ITRC Knowledge Base document KBRC00007966.
Please, I need the procedure on how to disable "Alert Messages".

Cheers.

Charles
Andrew Rutter
Honored Contributor
Solution

Re: Persistent POST (booting) System Alert message

here you go

Date: 9/8/01
Document description: How to troubleshoot an Alert Level 12
Document id: KBRC00007966


*edited to comply with forum guidelines

It is against forum guidelines to post the contents of Knowledge Base documents in this forum.
Andrew Rutter
Honored Contributor

Re: Persistent POST (booting) System Alert message

hi,

the doc cheryl mentioned is above, just use the bits for disabling the error.
Not the full document as its for different alert level

andy
Charles Egbon
Regular Advisor

Re: Persistent POST (booting) System Alert message

Hi Rutter,

Please accept my huge tones of hugs. Thanks a great deal. I think, this is going to give me some temporary sleep.

Other guys, thanks a million for all the suggestion.

Cheers.

Charles.
Charles Egbon
Regular Advisor

Re: Persistent POST (booting) System Alert message

Hi Rutter,

Please, could you resend the procedure for disabling the alert messages to my email box: freepurchase@yahoo.com
I didn't quite get it before it was edited on the forum.

I will appreciate it greatly.

Cheers.

Charles