hello all,
can someone tell me where windows stores information about it’s basic
volumes? I a not asking about the system volume information folder, but the
place (maybe a registry) where it stores the volume properties like size,
type etc?
thanks
AP
A P wrote:
can someone tell me where windows stores information about it’s basic
volumes? I a not asking about the system volume information folder,
but the place (maybe a registry) where it stores the volume properties
like size, type etc?
Why would that be in the registry? That kind of thing is dynamic – it
doesn’t need to survive from boot to boot. You would go fetch that
information from the volumes during system start up and store it in memory.
I don’t know that it’s not in the registry, but I don’t see any reason
why it would need to persist.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
tim,
yes i understand mount manager enumeraes these devices, but the GUID remains
constant. so is this information stored in the disk smewhere? outside the FS
usable space?
thanks
AP
On Sat, Mar 5, 2011 at 4:58 AM, Tim Roberts wrote:
> A P wrote:
> >
> > can someone tell me where windows stores information about it’s basic
> > volumes? I a not asking about the system volume information folder,
> > but the place (maybe a registry) where it stores the volume properties
> > like size, type etc?
>
> Why would that be in the registry? That kind of thing is dynamic – it
> doesn’t need to survive from boot to boot. You would go fetch that
> information from the volumes during system start up and store it in memory.
>
> I don’t know that it’s not in the registry, but I don’t see any reason
> why it would need to persist.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars 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
>
Which GUID are you referring to ?
Thanks,
Alex.
>yes i understand mount manager enumeraes these devices, but the GUID remains constant. so is this >information stored in the disk smewhere? outside the FS usable space?
Microsoft likely keeps such information in Register but I doubt you could access it. For example HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\Volume contains information about volumes but you could not look “Properties” key for a volume.
Use a standard way to get this information. You could this information from both - user space and kernel. Why do you need to get it from register?
Igor Sharovar
alex, igor,
thanks for the answers.
I am talking aboiut the *\?\Volume{*7603f260-142a-11d4-ac67-806d6172696f*
}* kind of GUIDS. They never change one mount manager exposes them, even
with a ssytem reboot. So where dooes this persist, also how does the mount
manager find out whether it is a basic volume or a dynamic one? Are these
information stored somewhere?
**
thanks
ap
On Sat, Mar 5, 2011 at 5:56 AM, wrote:
> >yes i understand mount manager enumeraes these devices, but the GUID
> remains constant. so is this >information stored in the disk smewhere?
> outside the FS usable space?
> Microsoft likely keeps such information in Register but I doubt you could
> access it. For example
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\Volume contains
> information about volumes but you could not look “Properties” key for a
> volume.
> Use a standard way to get this information. You could this information from
> both - user space and kernel. Why do you need to get it from register?
>
> Igor Sharovar
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars 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
>
The partition type for both MBR and GPT disks is used to determine
‘basic’ vs ‘dynamic’ volumes.
HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices maps volume GUIDs to on disk
partition signatures.
Mark Roddy
On Sat, Mar 5, 2011 at 8:47 AM, A P wrote:
> alex, igor,
>
> thanks for the answers.
>
> I am talking aboiut the \?\Volume{7603f260-142a-11d4-ac67-806d6172696f?}<br>> kind of GUIDS. They never change one mount manager exposes them, even with a
> ssytem reboot. So where dooes this persist, also how does the mount manager
> find out whether it is a basic volume or a dynamic one? Are these
> information stored somewhere?
>
>
>
> thanks
>
> ap
>
> On Sat, Mar 5, 2011 at 5:56 AM, wrote:
>>
>> >yes i understand mount manager enumeraes these devices, but the GUID
>> > remains constant. so is this >information stored in the disk smewhere?
>> > outside the FS usable space?
>> Microsoft likely keeps such information in Register but I doubt you could
>> access it. For example
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\Volume contains
>> information about volumes but you could not look “Properties” key for a
>> volume.
>> Use a standard way to get this information. You could this information
>> from both - user space and kernel. Why do you need to get it from register?
>>
>> Igor Sharovar
>>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars 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
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars 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
Mark,
thanks for trying to explain. Which entry in the partition table will
determine this? MBR partitions entres are 16 bytes long, do you mean to say
that the partition type (NTFS/FAT) has different numeral values for basic
and dynamic volumes? If so, what is the NTFS and FAT value one will see for
a dynamic volume?
AP
On Sun, Mar 6, 2011 at 12:26 AM, Mark Roddy wrote:
> The partition type for both MBR and GPT disks is used to determine
> ‘basic’ vs ‘dynamic’ volumes.
> HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices maps volume GUIDs to on disk
> partition signatures.
>
> Mark Roddy
>
>
>
> On Sat, Mar 5, 2011 at 8:47 AM, A P wrote:
> > alex, igor,
> >
> > thanks for the answers.
> >
> > I am talking aboiut the
> \?\Volume{7603f260-142a-11d4-ac67-806d6172696f }<br>> > kind of GUIDS. They never change one mount manager exposes them, even
> with a
> > ssytem reboot. So where dooes this persist, also how does the mount
> manager
> > find out whether it is a basic volume or a dynamic one? Are these
> > information stored somewhere?
> >
> >
> >
> > thanks
> >
> > ap
> >
> > On Sat, Mar 5, 2011 at 5:56 AM, wrote:
> >>
> >> >yes i understand mount manager enumeraes these devices, but the GUID
> >> > remains constant. so is this >information stored in the disk smewhere?
> >> > outside the FS usable space?
> >> Microsoft likely keeps such information in Register but I doubt you
> could
> >> access it. For example
> >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\Volume contains
> >> information about volumes but you could not look “Properties” key for a
> >> volume.
> >> Use a standard way to get this information. You could this information
> >> from both - user space and kernel. Why do you need to get it from
> register?
> >>
> >> Igor Sharovar
> >>
> >>
> >>
> >> —
> >> NTDEV is sponsored by OSR
> >>
> >> For our schedule of WDF, WDM, debugging and other seminars 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
> >
> > — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> > other seminars 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
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars 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
>
You won’t, dynamic volumes are somewhat different.
IIRC the value in the partition table is 0x42. On reading this the
partition manager will read the proprietary LDM database within the
partition to determine the structure of the dynamic volume. When
it’s happy that all elements are available it will signal the volume
manager of the volume arrival. Then the file system recognisers are
called to determine what the file system on the volume actually is
before loading the appropriate file system.
Actually, the MBR partition entry values even for basic partitions
are really no more than a hint for the o/s. The final arbiter of
knowing what file system is on the volume are the file system recognisers.
The main use of the partition entry values is to help the boot
loader, the o/s can be far more accommodating. That’s one reason why
with the initial implementation of dynamic volumes you couldn’t use a
dynamic volume as a boot volume.
Mark
At 19:18 05/03/2011, A P wrote:
Mark,
thanks for trying to explain. Which entry in the partition table
will determine this? MBR partitions entres are 16 bytes long, do you
mean to say that the partition type (NTFS/FAT) has different numeral
values for basic and dynamic volumes? If so, what is the NTFS and
FAT value one will see for a dynamic volume?AP
On Sun, Mar 6, 2011 at 12:26 AM, Mark Roddy
<mailto:xxxxxxxxxx@hollistech.com> wrote:
>The partition type for both MBR and GPT disks is used to determine
>‘basic’ vs ‘dynamic’ volumes.
>HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices maps volume GUIDs to on disk
>partition signatures.
>
>Mark Roddy
>
>
>
>On Sat, Mar 5, 2011 at 8:47 AM, A P
><mailto:xxxxxxxxxx@gmail.com> wrote:
> > alex, igor,
> >
> > thanks for the answers.
> >
> > I am talking aboiut the \?\Volume{7603f260-142a-11d4-ac67-806d6172696f }<br>> > kind of GUIDS. They never change one mount manager exposes them,
> even with a
> > ssytem reboot. So where dooes this persist, also how does the mount manager
> > find out whether it is a basic volume or a dynamic one? Are these
> > information stored somewhere?
> >
> >
> >
> > thanks
> >
> > ap
> >
> > On Sat, Mar 5, 2011 at 5:56 AM,
> <mailto:xxxxxxxxxx@hotmail.com> wrote:
> >>
> >> >yes i understand mount manager enumeraes these devices, but the GUID
> >> > remains constant. so is this >information stored in the disk smewhere?
> >> > outside the FS usable space?
> >> Microsoft likely keeps such information in Register but I doubt you could
> >> access it. For example
> >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\Volume contains
> >> information about volumes but you could not look “Properties” key for a
> >> volume.
> >> Use a standard way to get this information. You could this information
> >> from both - user space and kernel. Why do you need to get it
> from register?
> >>
> >> Igor Sharovar
> >>
> >>
> >>
> >> —
> >> NTDEV is sponsored by OSR
> >>
> >> For our schedule of WDF, WDM, debugging and other seminars visit:
> >> http:http://www.osr.com/seminars
> >>
> >> To unsubscribe, visit the List Server section of OSR Online at
> >>
> http:http://www.osronline.com/page.cfm?name=ListServer
> >
> > — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> > other seminars visit:
> http:http://www.osr.com/seminars To
> unsubscribe, visit the
> > List Server section of OSR Online at
> >
> http:http://www.osronline.com/page.cfm?name=ListServer
>
>—
>NTDEV is sponsored by OSR
>
>For our schedule of WDF, WDM, debugging and other seminars visit:
>http:http://www.osr.com/seminars
>
>To unsubscribe, visit the List Server section of OSR Online at
>http:http://www.osronline.com/page.cfm?name=ListServer</http:></http:></http:></http:></http:></http:></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>
If a partition table entry of type 0x42 is present in the legacy partition
table, then windows ignores the legacy partition table and uses a
proprietary partition table and a proprietary partitioning scheme (LDM or
DDM). As the Microsoft KnowledgeBase writes: *Pure dynamic disks (those not
containing any hard-linked partitions) have only a single partition table
entry (type 42) to define the entire disk. Dynamic disks store their volume
configuration in a database located in a 1-MB private region at the end of
each dynamic disk.*
*
*
*http://www.win.tue.nl/~aeb/partitions/partition_types-1.html\*
***
*
On Sun, Mar 6, 2011 at 1:18 AM, Mark S. Edwards wrote:
> You won’t, dynamic volumes are somewhat different.
>
> IIRC the value in the partition table is 0x42. On reading this the
> partition manager will read the proprietary LDM database within the
> partition to determine the structure of the dynamic volume. When it’s happy
> that all elements are available it will signal the volume manager of the
> volume arrival. Then the file system recognisers are called to determine
> what the file system on the volume actually is before loading the
> appropriate file system.
>
> Actually, the MBR partition entry values even for basic partitions are
> really no more than a hint for the o/s. The final arbiter of knowing what
> file system is on the volume are the file system recognisers.
>
> The main use of the partition entry values is to help the boot loader, the
> o/s can be far more accommodating. That’s one reason why with the initial
> implementation of dynamic volumes you couldn’t use a dynamic volume as a
> boot volume.
>
> Mark
>
>
> At 19:18 05/03/2011, A P wrote:
>
> Mark,
>
> thanks for trying to explain. Which entry in the partition table will
> determine this? MBR partitions entres are 16 bytes long, do you mean to say
> that the partition type (NTFS/FAT) has different numeral values for basic
> and dynamic volumes? If so, what is the NTFS and FAT value one will see for
> a dynamic volume?
>
> AP
>
> On Sun, Mar 6, 2011 at 12:26 AM, Mark Roddy wrote:
> The partition type for both MBR and GPT disks is used to determine
> ‘basic’ vs ‘dynamic’ volumes.
> HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices maps volume GUIDs to on disk
> partition signatures.
>
> Mark Roddy
>
>
>
> On Sat, Mar 5, 2011 at 8:47 AM, A P wrote:
> > alex, igor,
> >
> > thanks for the answers.
> >
> > I am talking aboiut the \?\Volume{7603f260-142a-11d4-ac67-806d6172696f
> }<br>> > kind of GUIDS. They never change one mount manager exposes them, even
> with a
> > ssytem reboot. So where dooes this persist, also how does the mount
> manager
> > find out whether it is a basic volume or a dynamic one? Are these
> > information stored somewhere?
> >
> >
> >
> > thanks
> >
> > ap
> >
> > On Sat, Mar 5, 2011 at 5:56 AM, < xxxxx@hotmail.com> wrote:
> >>
> >> >yes i understand mount manager enumeraes these devices, but the GUID
> >> > remains constant. so is this >information stored in the disk smewhere?
> >> > outside the FS usable space?
> >> Microsoft likely keeps such information in Register but I doubt you
> could
> >> access it. For example
> >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\Volume contains
> >> information about volumes but you could not look “Properties” key for a
> >> volume.
> >> Use a standard way to get this information. You could this information
> >> from both - user space and kernel. Why do you need to get it from
> register?
> >>
> >> Igor Sharovar
> >>
> >>
> >>
> >> —
> >> NTDEV is sponsored by OSR
> >>
> >> For our schedule of WDF, WDM, debugging and other seminars 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
> >
> > — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> > other seminars 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
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars 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
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars 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
>
–
- amitr0
Thanks all…
like a ‘hidden partition’, can there be a hidden volume too? one that disk
manager wont pick up? are there ioctls/irps to achieve this?
thanks
AP
On Sun, Mar 6, 2011 at 1:47 AM, amitr0 wrote:
> If a partition table entry of type 0x42 is present in the legacy partition
> table, then windows ignores the legacy partition table and uses a
> proprietary partition table and a proprietary partitioning scheme (LDM or
> DDM). As the Microsoft KnowledgeBase writes: Pure dynamic disks (those
> not containing any hard-linked partitions) have only a single partition
> table entry (type 42) to define the entire disk. Dynamic disks store their
> volume configuration in a database located in a 1-MB private region at the
> end of each dynamic disk.
> *
> *
> http://www.win.tue.nl/~aeb/partitions/partition_types-1.html
> ***
> *
> On Sun, Mar 6, 2011 at 1:18 AM, Mark S. Edwards wrote:
>
>> You won’t, dynamic volumes are somewhat different.
>>
>> IIRC the value in the partition table is 0x42. On reading this the
>> partition manager will read the proprietary LDM database within the
>> partition to determine the structure of the dynamic volume. When it’s happy
>> that all elements are available it will signal the volume manager of the
>> volume arrival. Then the file system recognisers are called to determine
>> what the file system on the volume actually is before loading the
>> appropriate file system.
>>
>> Actually, the MBR partition entry values even for basic partitions are
>> really no more than a hint for the o/s. The final arbiter of knowing what
>> file system is on the volume are the file system recognisers.
>>
>> The main use of the partition entry values is to help the boot loader, the
>> o/s can be far more accommodating. That’s one reason why with the initial
>> implementation of dynamic volumes you couldn’t use a dynamic volume as a
>> boot volume.
>>
>> Mark
>>
>>
>> At 19:18 05/03/2011, A P wrote:
>>
>> Mark,
>>
>> thanks for trying to explain. Which entry in the partition table will
>> determine this? MBR partitions entres are 16 bytes long, do you mean to say
>> that the partition type (NTFS/FAT) has different numeral values for basic
>> and dynamic volumes? If so, what is the NTFS and FAT value one will see for
>> a dynamic volume?
>>
>> AP
>>
>> On Sun, Mar 6, 2011 at 12:26 AM, Mark Roddy wrote:
>> The partition type for both MBR and GPT disks is used to determine
>> ‘basic’ vs ‘dynamic’ volumes.
>> HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices maps volume GUIDs to on disk
>> partition signatures.
>>
>> Mark Roddy
>>
>>
>>
>> On Sat, Mar 5, 2011 at 8:47 AM, A P wrote:
>> > alex, igor,
>> >
>> > thanks for the answers.
>> >
>> > I am talking aboiut the \?\Volume{7603f260-142a-11d4-ac67-806d6172696f
>> }<br>>> > kind of GUIDS. They never change one mount manager exposes them, even
>> with a
>> > ssytem reboot. So where dooes this persist, also how does the mount
>> manager
>> > find out whether it is a basic volume or a dynamic one? Are these
>> > information stored somewhere?
>> >
>> >
>> >
>> > thanks
>> >
>> > ap
>> >
>> > On Sat, Mar 5, 2011 at 5:56 AM, < xxxxx@hotmail.com> wrote:
>> >>
>> >> >yes i understand mount manager enumeraes these devices, but the GUID
>> >> > remains constant. so is this >information stored in the disk
>> smewhere?
>> >> > outside the FS usable space?
>> >> Microsoft likely keeps such information in Register but I doubt you
>> could
>> >> access it. For example
>> >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\Volume
>> contains
>> >> information about volumes but you could not look “Properties” key for a
>> >> volume.
>> >> Use a standard way to get this information. You could this information
>> >> from both - user space and kernel. Why do you need to get it from
>> register?
>> >>
>> >> Igor Sharovar
>> >>
>> >>
>> >>
>> >> —
>> >> NTDEV is sponsored by OSR
>> >>
>> >> For our schedule of WDF, WDM, debugging and other seminars 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
>> >
>> > — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging
>> and
>> > other seminars 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
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars 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
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars 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
>>
>
>
>
> –
>
> - amitr0
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars 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