Filter Manager not notifying instance setup for dynamic disk volume

I’ve looked through the forum and found some discussion on this issue about 2yrs ago but saw no resolution. I am sorry to say that I too are now in this situation.

As best as I have been able to ascertain from the trace output from my minifilter running on a customer’s system which I do not have direct access to – My instance setup routine is not being called for this particular dynamic disk volume which seems to be mounted OK and which shows up under the “fltmc volumes” command - complete with drive letter assigned. I have not been able to reproduce this problem in our lab with all sorts of dynamic volumes (if that is indeed the problem).

If relavent – This is a WS03 SP1 system with a Dell CERC SCSI RAID controller and 2 partitions (C & D). The D volume is dynamic.

Besides Ken Galipeau (Hi Ken!) has anyone else run across this problem? Have a solution/workaround? Or, has it been fixed in WS03 SP2?

/ted

More info on this. Doing a “fltmc volumes” command shows 5 volume objects. However, my filter instance setup entry is only called 4 times!

Here’s the volume list:

C: \Device\HarddiskVolume1
\Device\LanmanRedirector
D: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1
\Device\RdpDr
\Device\HarddiskVolumeShadowCopy2021

I am going to have the customer attempt to manually attach the D: volume to the filter today (after I build a version which allows this). Stay tuned.

/ted