Ioscan Hang

[Salm]

Hi

Our Backup server model rp5470 is hang . when we use ioscan command.I can not inerrupt and have to close the session.I can run other comand. only having problem with ioscan .
OS : 11.11 .

I also noticed ewhen dothe VGdisplay , shows lots of vgs not avticated.seems not realted to above ioscan issue . just write it down,

[Steven E. Protter]

Shalom,

dmesg

xstm/cstm/mstm start looking for a bad disk. This or a connection problem with fiber/scsi normally causes this issue.

sEP

[Salm]

I will appreciate if you clear little bit more ??/

[Salm]

Hi ,
Thanks for your reply.

Can you clear you answer little bit more ??

[Pupil_1]

use the dmesg command to see the latest message and decide on what to do.

[Bill Hassell]

If you run the ioscan command with -k, then it will not hang. However, you have very serious disk connection problems. If the disks are connected by fibre cables, you probably have configuration problems. The file /var/adm/syslog/syslog.log is probably full of errors.

[Khairy]

hi salm,

what other poster requested is to execute the hpux diagnostic tools (cstm/stm).

Please post the following output. From there we could determine whether you have hardware prob.

# echo "Map SelAll Information ; wait InfoLog Quit OK" | cstm > /tmp/devicelist

ioscan hangs could be hardware prob. It could be I/O cards or disks. Cstm output above will give us more info about your hardware condition.

Rgds

[whiteknight]

Salm,

if you see a lot of vg not activated, may be you can try

#vgchange -a y -> see got what type of errors.

if got errors, I would think connection loose or some kind of hardware fault.

check also/var/opt/resmon/log/event.log

WK

[F Verschuren]

Are there vumunix messages in the systlog, sounds like ore a scsi problem (broken disk, broken not terminated backup meduim, duble hartware path, etc... there can be a lot going wrong if ioscan hangs....

stap 1 check for vmunix message what is broken.
stap 2 check stm to see if everyting is working fine
stap 3 check if the problem started after a hartware change.
stap 4 check `dmesg` for errors
Stap 5 ask a hartware engeneer to fix the problem.