scsi error

[Sarjerao]

I am seeing this message in my syslog,
can you help me out to find out which device giving problem.
for your reference see the syslog message....
vmunix: SCSI: bp: 0000000052a07c00
May 22 00:13:48 tr vmunix:
May 22 00:13:48 tr vmunix: SCSI: bp: 0000000052a07c00
May 22 00:13:48 tr vmunix: dev: cd020000
May 22 00:13:48 tr vmunix: cdb: 12 00 00 00 80 00
May 22 00:13:48 tr vmunix: residual: 80
May 22 00:13:48 tr vmunix: status: (400) None -- Incomplete
May 22 10:12:51 tr vmunix:
May 22 10:12:51 tr vmunix: SCSI: bp: 0000000048fc5000
May 22 10:12:51 tr vmunix: dev: cd020000
May 22 10:12:51 tr vmunix: cdb: 12 00 00 00 80 00
May 22 10:12:51 tr vmunix: residual: 80
May 22 10:12:51 tr vmunix: status: (400) None -- Incomplete

[Devender Khatana]

Hi,

Possibally one of two things either your SCSI CDROM/DVDROM or any disk in VG with minor no. 020000.

HTH,
Devender

[Naveej.K.A]

Hi,

Check this thread..
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=53961

As per this thread, the device is on bus 02 (it doesn't mean C2t0d0). It could very well be a CDROM drive as Dev has suggested.

Regards,
Naveej

[Sarjerao]

there is no any cdrom/dvd connect to this system.
for ref see ioscan o/p

disk 0 10/0.3.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c0t3d0 /dev/rdsk/c0t3d0
disk 7 10/0.15.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c0t15d0 /dev/rdsk/c0t15d0
disk 1 10/8.1.0 sdisk CLAIMED DEVICE DGC C2300WDR10
/dev/dsk/c1t1d0 /dev/rdsk/c1t1d0
disk 2 10/8.1.1 sdisk CLAIMED DEVICE DGC C2300WDR10
/dev/dsk/c1t1d1 /dev/rdsk/c1t1d1
disk 3 10/8.1.2 sdisk CLAIMED DEVICE DGC C2300WDR1
/dev/dsk/c1t1d2 /dev/rdsk/c1t1d2
disk 4 10/8.1.3 sdisk CLAIMED DEVICE DGC C2300WDR5
/dev/dsk/c1t1d3 /dev/rdsk/c1t1d3
disk 5 10/8.1.4 sdisk CLAIMED DEVICE DGC C2300WDR5
/dev/dsk/c1t1d4 /dev/rdsk/c1t1d4

[Naveej.K.A]

Hi,

Check which devices are on external SCSI bus 02 and you can easily find out the controller instance number from the ioscan output...so the device is cxxt0d0

Regards,
--Naveej

[Mark Nieuwboer]

Hi,

Do you have perfiew, if so use this tool.
A piece of hardware doesn't come trough his self test. You have a hardware problem.
I don't know which device it could easily be a bus drive.

grtz. Mark

[Devender Khatana]

Hi,

It is very difficult to say from this ioscan output but for sure one of drives is having problems. Use stm in GUI mode and check drives by running the info tool. Try indivisual disks first rather them the one from storage etc. Also check for stale extents if you have some LVM level mirroring.

HTH,
Devender

[Ermin Borovac]

I think device is a tape drive, judging by device major number (first two digits "cd" in "cd020000").

cd (hex) = 205 (dec)

# lsdev 205
Character Block Driver Class
205 -1 stape tape

[Sarjerao]

Hi Ermin
I think you are right, preveously dat drive was connected but I don't have any old ioscan output. But don't understand why ginving error now.

[Suraj Singh_1]

Is the DAT drive still connected to the system?

May be some of your application are trying to access the DAT drive, and if it is not connected, system is logging the errors in syslog.log.

Regards,
Suraj

[Devender Khatana]

Hi,

Device files for previously connected DAT drive might be still lying in ioscan with state No H/W if not removed. You can find this my "ioscan -fnC tape" command. If some file exists and you are not using that drive then try removing device file using " rmsf -H H/W PATH).

But I do not think this message is for a device connected earlier.

HTH,
Devender

[Sarjerao]

Hi
there is no any tape device connected and even not showing in ioscan also.
This error flashes not frequently but some 8 days frequency.
How I can find which device causing this porblem.

[Stephen Keane · Accepted solution]

# ll -R /dev | grep 205 | grep 0x020000

If this comes back with no rows, then you don't have a device with a major number of 205 (hex 0xCD) and a minor number of 0x020000 as was reported in your syslog
May 22 00:13:48 tr vmunix: dev: cd020000

Something is trying to issue a SCSI Inquiry command with a return data size of 128 bytes to a device with major number 205 and minor number 0x020000. (cdb 12 00 00 00 80 00)

Whatever is doing this, is poorly coded, I would have expected it to have at least checked if the device existed before throwing a SCSI inquiry at it. It's probably using a generic SCSI interface, so hasn't detected that the device file no longer exists.

[Adisuria Wangsadinata_1]

Hi Sarjerao,

Do cross check between '/etc/lvmtab' and 'ioscan -nfCdisk', this to make sure there are no harddisk missing.

For 'dev : cd020000', usually the device file will be 'c2t0d0' or 'c32t0d0' (since 20 hex = 32 dec). So with this, maybe you can check both device file on your system.

May I know your machine model ?
Can you give me the complete ioscan from your system ?

Sometimes the issue like this can be resolved by SCSI patches, so check also your SCSI patches on your system.

Other posibility is the SCSI port without the SCSI terminator.

Hope this can help you.

Cheers,
AW

[Sarjerao]

Hi Stephen
ll -R /dev | grep 205 | grep 0x020000
crw-rw-rw- 2 bin bin 205 0x020000 Apr 15 09:19 0m
crw-rw-rw- 2 bin bin 205 0x020000 Apr 15 09:19 c2t0d0BEST
which points to tape drive only. Now I can ignore this message.
Only for curiosity,
there is no tape drive and ioscan -tape also shows nothing. why this error throwing is syslog

[Ermin Borovac]

Please try

# /sbin/rmsf -a /dev/rmt/0m
# /sbin/rmsf -a /dev/rmt/c2t0d0BEST

This should remove device files from /dev/rmt and device definition from /etc/ioconfig. Hopefully that will stop syslog errors.

[Stephen Keane]

Either you don't physically have a tape drive attached to the system or one is attached but not switched on or is offline. This is why ioscan can't detect one.

You do still have the device files for a tape drive, which you could remove if you wished.

Something still thinks you have a tape drive and is trying to issue a SCSI inquiry command to it. It may be some sort of auditing or diagnostics software. From the syslog, it appears to be something in the kernel, as it is reporting itself as vmunix.