Startup Error : IO Subsystem

[Rajiv Thakur]

Hi

I restarted my HP Unix Server and got the following error :-

The diagnostic logging facility has started receiving excesiive errors from IO subsystem.
IO error entries will be lost unitil cause of excessive IO logging is corrected.
If demlog daemon is not active us DIAGSYSTEM
commnand in SYSDIAG to start it.
If Demlog Daemon is active use Logtool utility in Sysdiag to determine which IO subsystems is logging Excessive errors.

If you want any other information please let me know.

My system is hung at this point, could you please suggest what should be done.

regards

[PVR]

hi,

if u can access the # prompt, pls check whether syslogd daemon is running or not

# ps -ef | grep syslogd. If not pls start it using
# /sbin/init.d/diagnostics start

If u can't access console(if the system in hung state during startup) press control and \ and then check the following log files for more details;
/var/adm/syslog/syslog.log
/etc/rc.clog

[Mic V.]

Every time I've seen this it's been an indication of a hardware problem, typically a disk that's going/gone bad.

You can check several places to see what's going on: the 'dmesg' command, the /var/adm/syslog/syslog.log file, the EMS log...

At this point I would try to reboot the system (coordinate with others/management if needed). If completely hung, you can reboot via ^B at the console, log into GSP if you're prompted for it, then at the "CM>" prompt type "rs", hit enter, type "y", enter. This is like CTRL-ALT-DELETE on a PC. (Note certain types of systems need help to enable ^B, such as the key in "service" position or a toggle on the back of a D.)

If you have attached SCSI devices or hot-swap, I would try to re-seat them in case a connection is loose and is causing the problem.

Once you can identify the hardware path, get a hardware person to check it out.

Good luck.

[Rajiv Thakur]

Hi

Thanks for your replies.I appreciate.
When i restart my system, it hangs and even by pressing B or \ , it doesnt come out of the Hang position so that i can check the log files etc. and find out the problem.
I have done it twice already.

regards
Rajiv.

[Steven E. Protter]

power switch your hung sysem.

bring it back up at the console

interupt at the 10 second prompt.

sea



If you don't see your boot disks or the right number of disks, you've had a hardware failure and need to call hardware or check the scsi connections for obvious flaws.


SEP

[John Carr_2]

Hi

what is your system ?

do I understand that you have powered the system down and up again ?

if you are able to do this powerdown again and power on hit the space bar to interrupt the boot cycle.

now try to get the system to single user mode type "bo" it will ask if you if you wish to interact with IPL answer YES. now type "hpux -is" if you get to the hash prompt you are in now type "mount -a" and go look at the error log files

:-) John.