- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: Persistent POST (booting) System Alert message
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2005 11:00 PM
тАО01-10-2005 11:00 PM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2005 11:17 PM
тАО01-10-2005 11:17 PM
Re: Persistent POST (booting) System Alert message
Isn't there more info in /var/adm/syslog/syslog.log? Can you post the last 20 lines of it?
Best Regards,
Eric Antunes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2005 12:11 AM
тАО01-11-2005 12:11 AM
Re: Persistent POST (booting) System Alert message
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2005 08:21 AM
тАО01-11-2005 08:21 AM
Re: Persistent POST (booting) System Alert message
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2005 08:21 PM
тАО01-11-2005 08:21 PM
Re: Persistent POST (booting) System Alert message
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2005 08:52 PM
тАО01-11-2005 08:52 PM
Re: Persistent POST (booting) System Alert message
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2005 03:58 AM
тАО01-12-2005 03:58 AM
Re: Persistent POST (booting) System Alert message
Thanks for your suggestions. The ioscan details are attached herewith.
Cheers.
Charles
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2005 04:08 AM
тАО01-12-2005 04:08 AM
Re: Persistent POST (booting) System Alert message
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2005 04:34 AM
тАО01-12-2005 04:34 AM
Re: Persistent POST (booting) System Alert message
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2005 07:56 PM
тАО01-12-2005 07:56 PM
Re: Persistent POST (booting) System Alert message
Best Regards,
Eric Antunes