Messages in Syslog.log: SCSI: dev = 0xbc040[x]00 provided only 0 bytes of inquiry data

[Sameer_Nirmal]

The SAN utility s/w mapping output and ioscan results are the same. The servers are indeed using c5txdx and c6txdx devices from the storage.

The reason the issue occured for c4t0dx because of those entries in ioscan. Those entries are still exist in the kernel and in /etc/ioconfig. That's why you see the messages given in syslog are from vmunix (kernel). Kernel would try to query through device driver which scsi driver in this case, the devices in that path which goes down from the FC card till 0/12/0/0.8.0.255.0.0.0.
The lun reference should have been gotten from the FC name server.

[Yogeeraj_1]

Dear sameer,

thank you for these clarifications.

Am proceeding with the following commands:
rmsf -a /dev/rdsk/c4t0d0
rmsf -a /dev/rdsk/c4t0d1
rmsf -a /dev/rdsk/c4t0d2
rmsf -a /dev/rdsk/c4t0d3
rmsf -a /dev/rdsk/c4t0d4
rmsf -a /dev/rdsk/c4t0d5
rmsf -a /dev/rdsk/c4t0d6
rmsf -a /dev/rdsk/c4t0d7


rmsf -a /dev/dsk/c4t0d0
rmsf -a /dev/dsk/c4t0d1
rmsf -a /dev/dsk/c4t0d2
rmsf -a /dev/dsk/c4t0d3
rmsf -a /dev/dsk/c4t0d4
rmsf -a /dev/dsk/c4t0d5
rmsf -a /dev/dsk/c4t0d6
rmsf -a /dev/dsk/c4t0d7

How do i go about upding the kernel such that these references no longer exists?

In fact, the FC card is now directly connected to the SAN and the HUB willl never be used again.

thank you for you time and precious guidance.

kind regards
yogeeraj

[Yogeeraj_1]

also, running:
rmsf -a /dev/rdsk/c4t2d0
rmsf -a /dev/rdsk/c4t2d1
rmsf -a /dev/rdsk/c4t2d2
rmsf -a /dev/rdsk/c4t2d3
rmsf -a /dev/rdsk/c4t2d4
rmsf -a /dev/rdsk/c4t2d5
rmsf -a /dev/rdsk/c4t2d6
rmsf -a /dev/rdsk/c4t2d7

rmsf -a /dev/dsk/c4t2d0
rmsf -a /dev/dsk/c4t2d1
rmsf -a /dev/dsk/c4t2d2
rmsf -a /dev/dsk/c4t2d3
rmsf -a /dev/dsk/c4t2d4
rmsf -a /dev/dsk/c4t2d5
rmsf -a /dev/dsk/c4t2d6
rmsf -a /dev/dsk/c4t2d7


kind regards
yogeeraj

[Yogeeraj_1]

hi again,

While running the rmsf command, the following warning message is displayed:
# rmsf -a /dev/rdsk/c4t0d0
Warning: No device associated with "/dev/rdsk/c4t0d0"


is this ok?

thanking you in advance for you replies

kind regards
yogeeraj

[RAC_1]

Do you have xpinfo or pvlist tool? Particularly, pvlist tool? Run pvlist, if disk still present on SAN, it will show. But I think, you can just rmsf and remove it. The warnign you see is OK.

[Yogeeraj_1]

hi,

now the following errors are popping-in into the syslog:

Mar 23 19:29:07 Server2 vmunix: SCSI: dev = 0xbc040100 provided only 0 bytes of inquiry data.
Mar 23 19:29:07 Server2 vmunix: dd_open must call scsi_init_inquiry_data -- dev: bc040100
Mar 23 19:29:08 Server2 vmunix: SCSI: dev = 0xbc040200 provided only 0 bytes of inquiry data.
Mar 23 19:29:08 Server2 vmunix: dd_open must call scsi_init_inquiry_data -- dev: bc040200
Mar 23 19:29:08 Server2 vmunix: SCSI: dev = 0xbc040300 provided only 0 bytes of inquiry data.
Mar 23 19:29:08 Server2 vmunix: dd_open must call scsi_init_inquiry_data -- dev: bc040300
Mar 23 19:29:08 Server2 vmunix: SCSI: dev = 0xbc040400 provided only 0 bytes of inquiry data.
Mar 23 19:29:08 Server2 vmunix: dd_open must call scsi_init_inquiry_data -- dev: bc040400
Mar 23 19:29:08 Server2 vmunix: SCSI: dev = 0xbc040500 provided only 0 bytes of inquiry data.
Mar 23 19:29:08 Server2 vmunix: dd_open must call scsi_init_inquiry_data -- dev: bc040500
Mar 23 19:29:08 Server2 vmunix: SCSI: dev = 0xbc040600 provided only 0 bytes of inquiry data.
Mar 23 19:29:08 Server2 vmunix: dd_open must call scsi_init_inquiry_data -- dev: bc040600
Mar 23 19:29:08 Server2 vmunix: SCSI: dev = 0xbc040700 provided only 0 bytes of inquiry data.
Mar 23 19:29:08 Server2 vmunix: dd_open must call scsi_init_inquiry_data -- dev: bc040700

any solutions?

kind regards
yogeeraj

[Sameer_Nirmal]

Yogeeraj,

Did you remove those device files?
Are these messages are appearing continuously or after doing something?

[Yogeeraj_1]

hi sameer,

thank you for your reply.

I am being very cautious. I have only removed the device file for c4t0d0.

# ll /dev/rdsk/c4t0d0
/dev/rdsk/c4t0d0 not found
# ll /dev/rdsk/c4t0d1
crw-r--r-- 1 bin sys 188 0x040100 Aug 26 2002 /dev/rdsk/c4t0d1
#

and these message have occurred only once.

At that time, there was not anything scheduled.

please guide.

kind regards
yogeeraj

[RAC_1]

You have two sets of files. raw disks and block disks device files. Did you try pvlist utility?? (Even though it is not necessary). You can safely remove the files.

[Sameer_Nirmal]

In order to get rid of those messages, you need to remove those files.

To be very specific, the scsi driver uses raw device files for device inquiry command etc. Thus removing raw devices files would definatly stop the messages in syslog.
# rmsf -a

[Yogeeraj_1]

hi RAC and Sameer,

thank you for the advice.

proceed with removal of the files and will monitor further henceforth --- just in case any error crops up.

# ll /dev/*dsk/c4t*
/dev/*dsk/c4t* not found
#


thanks again. Most appreciated your expert advices.

kind regards
yogeeraj