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

[Yogeeraj_1]

Dear experts!

I found the following messages in my syslog last night:

SCSI: dev = 0xbc040100 provided only 0 bytes of inquiry data.
SCSI: dev = 0xbc040200 provided only 0 bytes of inquiry data.
SCSI: dev = 0xbc040300 provided only 0 bytes of inquiry data.
SCSI: dev = 0xbc040400 provided only 0 bytes of inquiry data.
SCSI: dev = 0xbc040500 provided only 0 bytes of inquiry data.
SCSI: dev = 0xbc040600 provided only 0 bytes of inquiry data.
SCSI: dev = 0xbc040700 provided only 0 bytes of inquiry data.



what could that be?

thanking you in advance for your replies

kind regards
yogeeraj

[RAC_1]

Seems to be a disk. Check which one.

ll -R /dev | grep '0xbc040400'

[Yogeeraj_1]

hi RAC,

thank you for your reply

i don't get any output from:
ll -R /dev/|grep 'bc'

Note that the system is connected to a shared SAN.

kind regards
yogeeraj

[Arunvijai_4]

Hi Yogee,

I would rather try to run

# ioscan -fnC disk to check all the disks are claimed and available

-Arun

[RAC_1]

0xbc means 188. So it is a disk device.
/usr/sbin/lsdev -c 188 reports following.

Character Block Driver Class
188 31 sdisk disk

So it looks like, one of the disks may have problem.

[Sameer_Nirmal]

Hi Yogeeraj,

The SCSI disk devices reported are c4t0d[1-7]. The messages indicates scsi inquiry data could not be obtained from the disk devices.

Check the h/w status of those disks using
# ioscan -fnC disk
# diskinfo -v

By the way, what the SAN setup comprise of?

[Yogeeraj_1]

hi,

More information:

1 have 2 rp5430 (server1 and server2) connected to a single SAN in direct attached mode.

Each server is connect to one controller of the SAN.

Note that server1 is not reporting any problem. so i believe that the likelihood of a disk crash is very unprobable.

Attached the output of ioscan on both servers.

thanks you for your guidances.

kind regards
yogeeraj

[RAC_1]

ioscand does not report disks on c4 controller for which you getting messages.
Check FC cards.

ioscan -fnCfc
ioscan -fnCext_bus

fcmsutil on FC cards.

fcmsutil /dev/tdx stat

[Yogeeraj_1]

hi

the fc cards look ok.

Server2:>ioscan -fnC fc
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
fc 0 0/12/0/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
/dev/td0


Server2:>ioscan -fnC ext_bus
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide LVD
ext_bus 1 0/0/1/1 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide Single-Ended
ext_bus 2 0/0/2/0 c720 CLAIMED INTERFACE SCSI C87x Ultra Wide Single-Ended
ext_bus 3 0/0/2/1 c720 CLAIMED INTERFACE SCSI C87x Fast Wide Single-Ended
ext_bus 5 0/12/0/0.8.0.0.0 fcparray CLAIMED INTERFACE FCP Array Interface
ext_bus 4 0/12/0/0.8.0.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
SLX2:>


attached also the fcmsutil report

kind regards
yogeeraj

[RAC_1]

All looks OK, then are these current messages? Did you check the time stap on messages?? Also is STM showing all ok for disks visible to both systems?

[Yogeeraj_1]

hi,

the messages are current.

(see attachment)

In fact, i had restarted the server on sunday 19th of march 2006.

Also, i had previously observed that each time the server is restarted the messages appear on the syslog file. Then, i never occurs again... until next restart of course.

But this time, i was doing some major operations on datafiles on the file system and when checking the syslog, i came across these messages. I am really worried that something is going wrong this time!

please guide


kind regards
yogeeraj

[RAC_1]

Where are these disks from?? XP, EMC, Clarion? Do insf -ev again, see if you see disks from server2. Is correct zoing in place for SAN?

[Ermin Borovac]

These are probably some old disk device files that do not have corresponding devices in ioscan.

To find which disks

# ll /dev/*dsk | grep 040.00

Verify that device files don't appear in ioscan -fkn.

Remove old device files

# rmsf /dev/*dsk/cxtxdx

After you remove them you should not be getting this message any longer.

[Sameer_Nirmal]

The data you provided here doesn't show any reference to device file c4t0d[1-7].

I guess you have those corresponding device files in /dev/rdsk and /dev/dsk for those devices. Check if those files have any association with a actual h/w using
# lssf

Do you any message in dmesg on server 2?

Run STM logtool
Create a file having following contents
#Print the formatted logtool to /tmp directory
#
# Syntax: 'cstm -f logtool.txt'
#
ru
logtool
rs
saveas
/tmp/logtool.summary
done
fl
/var/stm/logs/os
saveas
/tmp/logtool.formatted
done
quit
ok
quit
ok

Then run the command given above
# cstm -f logtool.txt
Check the summary file for any errors.

Is there any associated between the two servers using the storage? Cluster or pathing s/w etc?

It may be possible those devices files were used previously and not used any more on server 2. If it is confirmed those files are not in use, you can delete them using
# rmsf -a /dev/rdsk/c4t0d1 etc.

[Yogeeraj_1]

RAC> Where are these disks from?? XP, EMC, Clarion? Do insf -ev again, see if you see disks from server2. Is correct zoning in place for SAN?

SAN is from LSI logic.
Attached more details about the disks etc
Additional info. We were once running the system with a connection to a FC hub and due to some weird problems we had to move to a direct-attached configuration.

[Yogeeraj_1]

Ermin> These are probably some old disk device files that do not have corresponding devices in ioscan.
Ermin> To find which disks
Ermin> # ll /dev/*dsk | grep 040.00
Ermin> Verify that device files don't appear in ioscan -fkn.
Ermin> Remove old device files
Ermin> # rmsf /dev/*dsk/cxtxdx
Ermin> After you remove them you should not be getting this message any longer.

Server2:>ll /dev/*dsk | grep 040.00
brw-r----- 1 bin sys 31 0x040000 Aug 26 2002 c4t0d0
brw-r----- 1 bin sys 31 0x040100 Aug 26 2002 c4t0d1
brw-r----- 1 bin sys 31 0x040200 Aug 26 2002 c4t0d2
brw-r----- 1 bin sys 31 0x040300 Aug 26 2002 c4t0d3
brw-r----- 1 bin sys 31 0x040400 Aug 26 2002 c4t0d4
brw-r----- 1 bin sys 31 0x040500 Aug 26 2002 c4t0d5
brw-r----- 1 bin sys 31 0x040600 Aug 26 2002 c4t0d6
brw-r----- 1 bin sys 31 0x040700 Aug 26 2002 c4t0d7
crw-r--r-- 1 bin sys 188 0x040000 Aug 26 2002 c4t0d0
crw-r--r-- 1 bin sys 188 0x040100 Aug 26 2002 c4t0d1
crw-r--r-- 1 bin sys 188 0x040200 Aug 26 2002 c4t0d2
crw-r--r-- 1 bin sys 188 0x040300 Aug 26 2002 c4t0d3
crw-r--r-- 1 bin sys 188 0x040400 Aug 26 2002 c4t0d4
crw-r--r-- 1 bin sys 188 0x040500 Aug 26 2002 c4t0d5
crw-r--r-- 1 bin sys 188 0x040600 Aug 26 2002 c4t0d6
crw-r--r-- 1 bin sys 188 0x040700 Aug 26 2002 c4t0d7
Server2:>

There is no occurrences of such device files in the ioscan -fkn
(see attachment)
is it *safe* to run rmsf /dev/*dsk/c4t0d[0-7] while this server is in operation?

[RAC_1 · Accepted solution]

These seem to be old devices. so run lssf on them, and see hardware path. Most probabally, they would show ??? there. then you can safely remove them.

[Yogeeraj_1]

Sameer Nirmal> The data you provided here doesn't show any reference to device file c4t0d[1-7].
Sameer Nirmal>
Sameer Nirmal> I guess you have those corresponding device files in /dev/rdsk and /dev/dsk for those devices. Check if those files have any association with a actual h/w using
Sameer Nirmal> # lssf
Sameer Nirmal>

As you can see in my reply to to RAC, there is not references to the device file c4t0d[1-7]

Server2:>lssf /dev/dsk/c4t0d0
sdisk card instance 4 SCSI target 0 SCSI LUN 0 section 0 at address ??? /dev/dsk/c4t0d0
Server2:>lssf /dev/dsk/c4t0d1
sdisk card instance 4 SCSI target 0 SCSI LUN 1 section 0 at address ??? /dev/dsk/c4t0d1
Server2:>lssf /dev/dsk/c4t0d2
sdisk card instance 4 SCSI target 0 SCSI LUN 2 section 0 at address ??? /dev/dsk/c4t0d2
Server2:>lssf /dev/dsk/c4t0d3
sdisk card instance 4 SCSI target 0 SCSI LUN 3 section 0 at address ??? /dev/dsk/c4t0d3
Server2:>lssf /dev/dsk/c4t0d4
sdisk card instance 4 SCSI target 0 SCSI LUN 4 section 0 at address ??? /dev/dsk/c4t0d4
Server2:>lssf /dev/dsk/c4t0d5
sdisk card instance 4 SCSI target 0 SCSI LUN 5 section 0 at address ??? /dev/dsk/c4t0d5
Server2:>lssf /dev/dsk/c4t0d6
sdisk card instance 4 SCSI target 0 SCSI LUN 6 section 0 at address ??? /dev/dsk/c4t0d6
Server2:>lssf /dev/dsk/c4t0d7
sdisk card instance 4 SCSI target 0 SCSI LUN 7 section 0 at address ??? /dev/dsk/c4t0d7
Server2:>



Sameer Nirmal> Do you any message in dmesg on server 2?
Sameer Nirmal>
On server 2 - Yes
On Server 1 - NO

[Yogeeraj_1]

Sameer Nirmal> Run STM logtool
Sameer Nirmal> Create a file having following contents
Sameer Nirmal> #Print the formatted logtool to /tmp directory
Sameer Nirmal> #
Sameer Nirmal> # Syntax: 'cstm -f logtool.txt'
Sameer Nirmal> #
Sameer Nirmal> ru
Sameer Nirmal> logtool
Sameer Nirmal> rs
Sameer Nirmal> saveas
Sameer Nirmal> /tmp/logtool.summary
Sameer Nirmal> done
Sameer Nirmal> fl
Sameer Nirmal> /var/stm/logs/os
Sameer Nirmal> saveas
Sameer Nirmal> /tmp/logtool.formatted
Sameer Nirmal> done
Sameer Nirmal> quit
Sameer Nirmal> ok
Sameer Nirmal> quit
Sameer Nirmal> ok
Sameer Nirmal>
Sameer Nirmal> Then run the command given above
Sameer Nirmal> # cstm -f logtool.txt
Sameer Nirmal> Check the summary file for any errors.
Sameer Nirmal>

The summary report does not seem to contain latest information. The last entry processed by STM is Nov 29, 2005!

Server2:tmp>more logtool.summary
.... server2.mydomain.mu : x.x.x.x ....

-- Logtool Utility: View Raw Summary --

Summary of: /var/stm/logs/os/log3.raw.cur

Date/time of first entry: Thu Sep 2 12:56:54 2004

Date/time of last entry: Tue Nov 29 09:48:48 2005



Number of LPMC entries: 1
Number of System Overtemp entries: 0
Number of LVM entries: 0
Number of Logger Event entries: 0

Number of I/O Error entries: 713


Device paths for which entries exist:

(6) 0/12/0/0.8.0.2.0.0.5
(113) 0/12/0/0.8.0.0.0.0.5
(156) 0/12/0/0.8.0.0.0.0.4
(114) 0/12/0/0.8.0.0.0.1.2
(324) 0/12/0/0

Products for which entries exist:

(210) SCSI Disk
(179)
(324) Fibre Channel Interface

Product Qualifiers for which entries exist:

(210) STKOPENstorage
(179)
(324) HP5158A_Tachyon_TL

Logger Events for which entries exist:

(389) sdisk
(324) td
Server2:tmp>

[Yogeeraj_1]

Sameer Nirmal> Is there any associated between the two servers using the storage? Cluster or pathing s/w etc?
Sameer Nirmal>
Sameer Nirmal> It may be possible those devices files were used previously and not used any more on server 2. If it is confirmed those files are not in use,
Sameer Nirmal> you can delete them using
Sameer Nirmal> # rmsf -a /dev/rdsk/c4t0d1 etc.

No. the two servers are running independently. No clusters. No Pathing software is being use.

I guess it is safe to proceed with the following:
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

[Sameer_Nirmal]

I guess the reason of appearing those devices files is justified by the entries in the ioscan and what you said about previous FC hub connection. The ioscan shows the entries ( for FC communication )as
ext_bus 4 0/12/0/0.8.0.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 15 0/12/0/0.8.0.255.0.0 tgt CLAIMED DEVICE
ctl 4 0/12/0/0.8.0.255.0.0.0 sctl CLAIMED DEVICE STK OPENstorage D173
/dev/rscsi/c4t0d0
And those device files might have been created for luns created that time.
There are no h/w paths beneath above entries in ioscan for those luns as there is no such connection ( FC HUB ) anymore.
You can safely remove those device files.

[Yogeeraj_1]

Thanks Sameer for you reply!

There are also some other device files c4t2dx are visible too!

Server2:>ll /dev/*dsk/c4*
brw-r----- 1 bin sys 31 0x040000 Aug 26 2002 /dev/dsk/c4t0d0
brw-r----- 1 bin sys 31 0x040100 Aug 26 2002 /dev/dsk/c4t0d1
brw-r----- 1 bin sys 31 0x040200 Aug 26 2002 /dev/dsk/c4t0d2
brw-r----- 1 bin sys 31 0x040300 Aug 26 2002 /dev/dsk/c4t0d3
brw-r----- 1 bin sys 31 0x040400 Aug 26 2002 /dev/dsk/c4t0d4
brw-r----- 1 bin sys 31 0x040500 Aug 26 2002 /dev/dsk/c4t0d5
brw-r----- 1 bin sys 31 0x040600 Aug 26 2002 /dev/dsk/c4t0d6
brw-r----- 1 bin sys 31 0x040700 Aug 26 2002 /dev/dsk/c4t0d7
brw-r----- 1 bin sys 31 0x042000 Aug 23 2002 /dev/dsk/c4t2d0
brw-r----- 1 bin sys 31 0x042100 Aug 23 2002 /dev/dsk/c4t2d1
brw-r----- 1 bin sys 31 0x042200 Aug 23 2002 /dev/dsk/c4t2d2
brw-r----- 1 bin sys 31 0x042300 Aug 23 2002 /dev/dsk/c4t2d3
brw-r----- 1 bin sys 31 0x042400 Aug 23 2002 /dev/dsk/c4t2d4
brw-r----- 1 bin sys 31 0x042500 Aug 23 2002 /dev/dsk/c4t2d5
brw-r----- 1 bin sys 31 0x042600 Aug 23 2002 /dev/dsk/c4t2d6
brw-r----- 1 bin sys 31 0x042700 Aug 23 2002 /dev/dsk/c4t2d7
crw-r--r-- 1 bin sys 188 0x040000 Aug 26 2002 /dev/rdsk/c4t0d0
crw-r--r-- 1 bin sys 188 0x040100 Aug 26 2002 /dev/rdsk/c4t0d1
crw-r--r-- 1 bin sys 188 0x040200 Aug 26 2002 /dev/rdsk/c4t0d2
crw-r--r-- 1 bin sys 188 0x040300 Aug 26 2002 /dev/rdsk/c4t0d3
crw-r--r-- 1 bin sys 188 0x040400 Aug 26 2002 /dev/rdsk/c4t0d4
crw-r--r-- 1 bin sys 188 0x040500 Aug 26 2002 /dev/rdsk/c4t0d5
crw-r--r-- 1 bin sys 188 0x040600 Aug 26 2002 /dev/rdsk/c4t0d6
crw-r--r-- 1 bin sys 188 0x040700 Aug 26 2002 /dev/rdsk/c4t0d7
crw-r--r-- 1 bin sys 188 0x042000 Aug 23 2002 /dev/rdsk/c4t2d0
crw-r--r-- 1 bin sys 188 0x042100 Aug 23 2002 /dev/rdsk/c4t2d1
crw-r--r-- 1 bin sys 188 0x042200 Aug 23 2002 /dev/rdsk/c4t2d2
crw-r--r-- 1 bin sys 188 0x042300 Aug 23 2002 /dev/rdsk/c4t2d3
crw-r--r-- 1 bin sys 188 0x042400 Aug 23 2002 /dev/rdsk/c4t2d4
crw-r--r-- 1 bin sys 188 0x042500 Aug 23 2002 /dev/rdsk/c4t2d5
crw-r--r-- 1 bin sys 188 0x042600 Aug 23 2002 /dev/rdsk/c4t2d6
crw-r--r-- 1 bin sys 188 0x042700 Aug 23 2002 /dev/rdsk/c4t2d7
Server2:>

are they also invalid?

please guide me further.

thanking you in advance for your reply

kind regards
yogeeraj

[Sameer_Nirmal]

The device files c4t2dx should have been created for another set of 8 luns like c4t0dx earlier.

c4t0dx indicates target 0 with luns from 0 to 7 ( 8 luns per target for "fcpdev")
If you create more than 8 luns after that the target number would change and will have another 8 luns.

So you can safely remove c4t2dx files as well as their h/w devices doesn't exist anymore.

[Yogeeraj_1]

hi again,

attached the output from the SAN utility software which display the SAN volumes mapping to device files.

seems like only c5txdx on server 2 and c6txdx on server 1 are in use... so why is it that only c4t0dx is giving these messages? (why not c4t2dx, etc ??)

thank you for further clarifications

kind regards
yogeeraj

[Yogeeraj_1]

file attached