1825759 Members
2223 Online
109687 Solutions
New Discussion

vmunix messages

 
SOLVED
Go to solution
Rene Hermann_1
Advisor

vmunix messages

We had the following vmunix messages in syslog.log:

Nov 22 01:06:09 host vmunix: 0/6/0/0.3.7 sctl
...
Nov 22 01:16:11 host vmunix: SCSI: Request Timeout; Abort -- lbolt: 350924184, dev: cd 063040, io_id: 6ad8253

Has the first message something to do with the second message? And how can I find out what device is dev: cd063040 ?
And whats the reason for this message?

Thank you.
Rene
# cd pub # more beer
7 REPLIES 7
Karthik S S
Honored Contributor

Re: vmunix messages

Hi,

I think this error is something to do with SCSI ID Conflict. Do a dmesg and see if you are receiving any similar messages. Do a ioscan -fnC disk to make sure that no SCSI IDs are conflicting.

Karthik
For a list of all the ways technology has failed to improve the quality of life, please press three. - Alice Kahn
Chris Wilshaw
Honored Contributor

Re: vmunix messages

These timeouts often occur if a disk is unable to respond to a read/write request within the default timeout period, so it may not be a major problem.

This can be corrected by running

pvchange -t 60 /dev/dsk/

If it was a hardware problem, you would probably start to experience performance problems on the system. ioscan would possibly hang, or show the device with NO_HW
Rene Hermann_1
Advisor

Re: vmunix messages

There are no disks at this HW-Path. There is an Ultrium Drive and some unknown Hardware. I show you the output from ioscan -fun:

ext_bus 6 0/6/0/0 c720 CLAIMED INTERFACE SCSI C895 Ultra2 Wide LVD
tape 2 0/6/0/0.3.0 stape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/2m /dev/rmt/c6t3d0BEST
/dev/rmt/2mb /dev/rmt/c6t3d0BESTb
/dev/rmt/2mn /dev/rmt/c6t3d0BESTn
/dev/rmt/2mnb /dev/rmt/c6t3d0BESTnb
ctl 9 0/6/0/0.3.7 sctl NO_HW DEVICE
ctl 7 0/6/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c6t7d0


Thanks for any further help.

Rene
# cd pub # more beer
T G Manikandan
Honored Contributor

Re: vmunix messages

The messages are the SCSI reset due to a device which is not responding to the specific timeout period.

The system would reset the SCSI bus and try again and again.

check for the SCSI connections.

//
Just check whether you have proper termination.
//

Do you have any extra messages in the /var/adm/syslog/syslog.logfile.
Does your ioscan take a long time?

Thanks
T G Manikandan
Honored Contributor
Solution

Re: vmunix messages

Rene Hermann_1
Advisor

Re: vmunix messages

There are no other syslog-messages and no problems with ioscan.

I asked our customer to check the connection to the Ultrium tape drive.

Thanks.

Rene
# cd pub # more beer
Balakumar M
Frequent Advisor

Re: vmunix messages

Hi,
First check the disk have any error ( error led)
As Mani said, check weather terminated properly, and also check the SCSI cable connection.

have a look at dmesg out put.

regards,
Bala
Life is a continues learning process