dmesg error

[Kenn Chen_1]

My syslog and dmesg contents below error message :- what is it error about and is it critical to my server ? N class with HPUX 11.0
==>

vmunix: SCSI: Attempt to access partially open device -- dev: bc0ac000^M
vmunix: SCSI: Attempt to access partially open device -- dev: bc0ad000^M
vmunix: SCSI: Attempt to access partially open device -- dev: bc0ae000^M
vmunix: SCSI: Attempt to access partially open device -- dev: bc0a2000^M
vmunix: SCSI: Attempt to access partially open device -- dev: bc0a3000^M
vmunix: SCSI: Attempt to access partially open device -- dev: bc0a4000^M
vmunix: SCSI: Attempt to access partially open device -- dev: bc0a5000^M
vmunix: SCSI: Attempt to access partially open device -- dev: bc0a6000^M
vmunix: SCSI: Attempt to access partially open device -- dev: bc0a7000^M

[Steve Steel]

Hi

This type of error can be generated when vgscan is run.It is a placeholder and since it has no importance will hopefully be suppressed one day.



Steve Steel

[Steve Steel]

Hi

Attempt to access partially open device

This patch
Patch Name: PHKL_24004

Patch Description: s700_800 11.00 SCSI IO Subsystem Cumulative Patch

Creation Date: 01/06/05

Post Date: 01/06/12

Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00

Or an eventual replacement and its dependencies will suppress the message

Steve Steel

[T G Manikandan · Accepted solution]

//*

What do partially open device SCSI messages in syslog.log mean? DocId: AUSRCKBRC00000687 Updated: 4/13/00 9:19:43 PM

PROBLEM
Periodically on some systems you will see messages like the following appearing
in /var/adm/syslog/syslog.log:

Jan 11 16:06:01 hp1 vmunix: SCSI: Attempt to access partially open device --
dev: bc094000
Jan 11 16:06:01 hp1 vmunix: SCSI: Attempt to access partially open device --
dev: bc094000
Jan 11 16:06:01 hp1 vmunix: SCSI: Attempt to access partially open device --
dev: bc096000
RESOLUTION
The kernel SCSI driver when it opens a device sends the INQUIRY,
START_STOP_UNIT, TEST_UNIT_READY and READ_CAPACITY SCSI commands to start
the device and get the characteristics and the capacity of the device.

If any of the above SCSI commands fail and the device is a raw device the
kernel will print a message like the ones above. This is done so commands
like diskinfo and mediainit can still open devices even though they may not
be ready.

An example would be a CDROM drive without a CDROM in it. For the diskinfo
command some of the SCSI commands will fail because there is no media (e.g.
READ_CAPACITY cannot return the amount of data on the CDROM if there is no
CDROM in the drive) but the INQUIRY command will work (i.e. even if the
CDROM does not have disk in it it will still reply with information to an
INQUIRY command). The mount command will not cause these errors because
the kernel mounts the CDROM, no programs attempt to open the device file.

Disk arrays can also create these messages. Disk arrays can have luns created
that have no device associated with them. See Document A5469587 for
information about this message and EMC BCVs, other disk arrays can also
cause these messages to be seen.

The attempt to access partially open device messages typically do not
indicate any problems that need attention, unless the device being complained
about SHOULD have a real device associated with it. In that case since
the disk array is not reporting some of the information needed by HPUX
the problem would most likely reside in the array.


*//