Hi all,

We have an application (written in C/C++) for management of SCSI storage
devices. Through this application, we are creating a logical drive (LD) using
two physical disks and this LD should show up in the list of volumes in
Windows. The job of exposing the newly created LD to Windows is done by the
device driver for the RAID controller. So after this is successfully done,
one can right click on My Computer, then Manage -> Disk Management, and can
see the new LD there.

The problem is, in some cases (that is, for some version of the application)
this newly created LD is not getting exposed to Windows. To reiterate, the
application as such does not expose the LD to Windows (it is done by the
driver). But we noticed that with the same driver version, a different
version of the application causes this problem. So the problem _might_ be
with the application. In particular, the device driver does not get any
error, but is not receiving READ/WRITE/READ_CAPACITY calls for the LD
created. Is this possible to happen because the application is doing
something wrong (perhaps, locking up some resource)? Under what situation can
such a thing happen?

The system is a Windows Server 2003 Enterprise Edition with Xeon processor.
Any help is appreciated. If this is not a right forum for this topic, please
direct me to the right one. Thank you.

On Thu, 29 Dec 2005 16:31:02 -0800, "orbital"
<orbital@discussions.microsoft.com> wrote:

In the failure case have you tried using the disk manager to rescan?
This can sometimes help in the case where the problem is that the bus
driver has not forced a re-enumeration.

Also you should look in device manager to see if your logical disk has
shown up as a disk device. If it hasn't then you need to look deeper
into why it hasn't shown up. If the device has shown up but has an
error condition, that would be a major clue as to what has gone wrong.




=====================
Mark Roddy DDK MVP
Windows Vista/2003/XP/2000 Consulting
Device and Filesystem Drivers
Hollis Technology Solutions 603-321-1032
www.hollistech.com

Hi Mark

"Mark Roddy" wrote:

I had tried re-scanning.. didn't help.

I will try this and let you know. But can you please elaborate what you mean
by looking deeper. I am not a driver person (I work at the application
layer), so I am still wondering what might have the application done wrong
which is causing this problem.

Thanks for your help.

On Fri, 30 Dec 2005 12:29:02 -0800, "orbital"
<orbital@discussions.microsoft.com> wrote:

I mean that you are going to have to understand what is going on at
the device level, most likely through the use of a debugger. This may
eventually lead you back to some application issue. If you plunked me
down at a system and asked me to figure out what was wrong I would
start by attaching a kernel debugger and taking a look at the device
configuration for the failure case and for the success case, and that
would perhaps get me pointed at where the problem is.


=====================
Mark Roddy DDK MVP
Windows Vista/2003/XP/2000 Consulting
Device and Filesystem Drivers
Hollis Technology Solutions 603-321-1032
www.hollistech.com