Volume attach fails with ERROR_FLT_VOLUME_NOT_FOUND. iSCSI issue?

NTFSD
1

We have a strange problem at a customer site (live server, of course!) My
filter driver htdafd loads OK, and the Instance setup callback is called for
the expected things, apart from the D: drive. It attaches OK to the C:
drive, and refuses LanmanRedirector, RdpDr, the CD etc OK (as intended - it
only works on NTFS volumes.) The D: drive just isn’t offered AFAICS.

‘fltmc volumes’ shows…

C: \Device\HarddiskVolume1
D: \Device\HarddiskVolume2

So I experiment…

‘fltmc detach htdafd C:’ detaches C: OK
‘fltmc attach htdafd \Device\HarddiskVolume1’ re-attaches it
but
‘fltmc attach htdafd \Device\HarddiskVolume2’ fails with error 0x801f0014 -
The system could not find the specified volume.

Note that attempting this with the non-existent \Device\HarddiskVolume3
gives a different error - 0x80070003 - The system cannot find the path
specified.

Also note that ‘fltmc attach htdafd \Device\RdpDr’ fails, as expected with
0x801f000f - Do not attach the filter to the volume at this time. This is
the code htdafd returns when IT rejects a volume/device.

So what is it about the D drive that means it cannot be filtered, yet shows
up in ‘fltmc volumes’? The only odd thing I can see about the D drive is
that it is an iSCSI connected LUN on an Equallogic box, using the Microsoft
iSCSI initiator.

Tests on my own systems have worked OK with iSCSI, albeit to a NetApp
filer - I don’t have an Equallogic to hand.

Any ideas, anybody?

Thanks,

John

2

Forgot to state the OS. This is Windows Server 2003 R2 SP2 32-bit. iSCSI
initiator appears to be up to date.

  • John

“John Leonard” wrote in message
news:xxxxx@ntfsd…
> We have a strange problem at a customer site (live server, of course!) My
> filter driver htdafd loads OK, and the Instance setup callback is called
> for the expected things, apart from the D: drive. It attaches OK to the C:
> drive, and refuses LanmanRedirector, RdpDr, the CD etc OK (as intended -
> it only works on NTFS volumes.) The D: drive just isn’t offered AFAICS.
>
> ‘fltmc volumes’ shows…
>
> C: \Device\HarddiskVolume1
> D: \Device\HarddiskVolume2
>
> So I experiment…
>
> ‘fltmc detach htdafd C:’ detaches C: OK
> ‘fltmc attach htdafd \Device\HarddiskVolume1’ re-attaches it
> but
> ‘fltmc attach htdafd \Device\HarddiskVolume2’ fails with error
> 0x801f0014 - The system could not find the specified volume.
>
> Note that attempting this with the non-existent \Device\HarddiskVolume3
> gives a different error - 0x80070003 - The system cannot find the path
> specified.
>
> Also note that ‘fltmc attach htdafd \Device\RdpDr’ fails, as expected with
> 0x801f000f - Do not attach the filter to the volume at this time. This is
> the code htdafd returns when IT rejects a volume/device.
>
> So what is it about the D drive that means it cannot be filtered, yet
> shows up in ‘fltmc volumes’? The only odd thing I can see about the D
> drive is that it is an iSCSI connected LUN on an Equallogic box, using the
> Microsoft iSCSI initiator.
>
> Tests on my own systems have worked OK with iSCSI, albeit to a NetApp
> filer - I don’t have an Equallogic to hand.
>
> Any ideas, anybody?
>
> Thanks,
>
> John
>
>
>

3

>Tests on my own systems have worked OK with iSCSI, albeit to a NetApp

filer
Tell them to buy a NetApp filer :slight_smile:

Harish

-----Original Message-----
From: John Leonard [mailto:xxxxx@bhead.co.uk]
Sent: Thursday, February 18, 2010 5:15 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Volume attach fails with ERROR_FLT_VOLUME_NOT_FOUND.
iSCSI issue?

We have a strange problem at a customer site (live server, of course!)
My
filter driver htdafd loads OK, and the Instance setup callback is called
for
the expected things, apart from the D: drive. It attaches OK to the C:
drive, and refuses LanmanRedirector, RdpDr, the CD etc OK (as intended -
it
only works on NTFS volumes.) The D: drive just isn’t offered AFAICS.

‘fltmc volumes’ shows…

C: \Device\HarddiskVolume1
D: \Device\HarddiskVolume2

So I experiment…

‘fltmc detach htdafd C:’ detaches C: OK
‘fltmc attach htdafd \Device\HarddiskVolume1’ re-attaches it
but
‘fltmc attach htdafd \Device\HarddiskVolume2’ fails with error
0x801f0014 -
The system could not find the specified volume.

Note that attempting this with the non-existent \Device\HarddiskVolume3
gives a different error - 0x80070003 - The system cannot find the path
specified.

Also note that ‘fltmc attach htdafd \Device\RdpDr’ fails, as expected
with
0x801f000f - Do not attach the filter to the volume at this time. This
is
the code htdafd returns when IT rejects a volume/device.

So what is it about the D drive that means it cannot be filtered, yet
shows
up in ‘fltmc volumes’? The only odd thing I can see about the D drive is

that it is an iSCSI connected LUN on an Equallogic box, using the
Microsoft
iSCSI initiator.

Tests on my own systems have worked OK with iSCSI, albeit to a NetApp
filer - I don’t have an Equallogic to hand.

Any ideas, anybody?

Thanks,

John

NTFSD is sponsored by OSR

For our schedule of debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

4

> >Tests on my own systems have worked OK with iSCSI, albeit to a NetApp

>filer
Tell them to buy a NetApp filer :slight_smile:

Not good to say this. :slight_smile:

Anyways, the OP could start off by figuring out the exact function in the
call stack that returned the error. And then figuring out what check did it
fail for?

Regards,
Ayush Gupta
AI Consulting

5

> Tests on my own systems have worked OK with iSCSI, albeit to a NetApp

filer - I don’t have an Equallogic to hand.

Ask them to install the most fresh firmware for the Equallogic box.

Some SAN/NAS boxes are extremely lame. For instance, I saw a NAS box whose’s CIFS server code returned “file not found” if the file exists, but the user has no permissions to it. Yes, “file not found” instead of “access denied”.

Due to this lame box, we now need to ask the interactive user for a password to access the share on file not found errors.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com