Prev: Vista QOS testing
Next: Problem with Microsoft Update for BisonCam, NB Pro driver
From: Ernie Billing on 9 Aug 2007 19:04
We have an intermittent problem with FltGetVolumeFromName() not finding a
volume on a USB drive by its drive letter. Return code is
STATUS_FLT_VOLUME_NOT_FOUND. It'll fail for a while, and then work for a
while.

Has been seen on two systems: one XP, one Windows Server 2003. Slightly
different in one way though. On the XP machine, "fltmc volumes" does not
show the USB drive (E:) but the drive can be browsed through Explorer. On
the server, fltmc volumes does show the drive (its on a mount point.) I've
tried attaching minispy to these devices and it fails w/ the same error.

Anyone have any ideas?

From: Anton Bassov on 10 Aug 2007 01:34
Unless USB disk presents itself as a basic disk to the system, there are no
logical volumes (i.e. the ones managed by Ftdisk.sys) mounted on its
partitions - Ftdisk.sys is out of play for it. Instead, both driver letter
and volume ID correspond to the disk partition itself (i.e. and object
crereated by Disk.sys). However, if it presents itself a a basic disk, then
it is treated exactly like hard disk, so that volumes are mounted on it.

This is why, depending on the particular disk that is plugged into USB port,
you may get different results...

Anton Bassov

"Ernie Billing" wrote:

> We have an intermittent problem with FltGetVolumeFromName() not finding a
> volume on a USB drive by its drive letter. Return code is
> STATUS_FLT_VOLUME_NOT_FOUND. It'll fail for a while, and then work for a
> while.
>
> Has been seen on two systems: one XP, one Windows Server 2003. Slightly
> different in one way though. On the XP machine, "fltmc volumes" does not
> show the USB drive (E:) but the drive can be browsed through Explorer. On
> the server, fltmc volumes does show the drive (its on a mount point.) I've
> tried attaching minispy to these devices and it fails w/ the same error.
>
> Anyone have any ideas?
>
From: Ernie Billing on 10 Aug 2007 12:16
The drive is reported in the Disk Management snap in as a basic disk. I've
attempted to attach minispy to it through both its mount point and its
\device\.. path:

fltmc attach minispy c:\mp
fltmc attach minispy \device\harddiskvolume3

both fail with 0x801f0014, The system could not find the volume specified

But "fltmc volumes" reports both.

"Anton Bassov" wrote:

> Unless USB disk presents itself as a basic disk to the system, there are no
> logical volumes (i.e. the ones managed by Ftdisk.sys) mounted on its
> partitions - Ftdisk.sys is out of play for it. Instead, both driver letter
> and volume ID correspond to the disk partition itself (i.e. and object
> crereated by Disk.sys). However, if it presents itself a a basic disk, then
> it is treated exactly like hard disk, so that volumes are mounted on it.
>
> This is why, depending on the particular disk that is plugged into USB port,
> you may get different results...
>
> Anton Bassov
>
> "Ernie Billing" wrote:
>
> > We have an intermittent problem with FltGetVolumeFromName() not finding a
> > volume on a USB drive by its drive letter. Return code is
> > STATUS_FLT_VOLUME_NOT_FOUND. It'll fail for a while, and then work for a
> > while.
> >
> > Has been seen on two systems: one XP, one Windows Server 2003. Slightly
> > different in one way though. On the XP machine, "fltmc volumes" does not
> > show the USB drive (E:) but the drive can be browsed through Explorer. On
> > the server, fltmc volumes does show the drive (its on a mount point.) I've
> > tried attaching minispy to these devices and it fails w/ the same error.
> >
> > Anyone have any ideas?
> >
 | 
Pages: 1
Prev: Vista QOS testing
Next: Problem with Microsoft Update for BisonCam, NB Pro driver