G
Guest
To those interested in helping me recover from a HDD failure, thank you for
your time. After coming back from a weekend when I turned my computer off,
it no longer would boot to my typical installation of Win XP Prox32bit. Upon
loading my secondary installation on another physical disk, I noticed that in
disk management, my other dynamic disk was showing up as "failed" and a new
disk had shown up that was basic and all free space.
To fill you in, I have two hard drives, both dynamic (first mistake), and
each drive has a mix of simple, striped, and spanned volumes. This secondary
windows installation is on a simple volume, and I have important data on a
simple volume on my failed drive.
I ran dmdiag.exe and found that my failed drive has a partition hex of 0x0F.
According to KB 320283, this is the same as 0x05 (extended partition) and
uses Logical Block Address Int 0x13 extensions. At this point I am no longer
concerned with how the MBR was changed. I am however, interested in changing
it back to recover my data and never to use dynamic disks again (not to
mention establish a backup plan). I have downloaded DiskProbe.exe and
examined my boot sectors. Comparing my "good drive" to my bad one, there
seems to be quite a few differences. I would cut and paste the info, but it
seems that diskprobe doesn't allow for notepad exportation, etc. I have no
clue what hexadecimal has to do with anything and it has always confused the
crap out of me. I have a theory. I read in KB 329707 that... "Dynamic disks
offer advantages over basic disks, which use the original MS-DOS-style master
boot record (MBR) partition tables to store primary and logical disk
partitioning information. Dynamic disks use a private region of the disk to
maintain a Logical Disk Manager (LDM) database, which contains volume types,
offsets, memberships, and drive letters of each volume. The LDM database is
also replicated, so each dynamic disk knows about every other dynamic disk
configuration. This feature makes dynamic disks more reliable and recoverable
than basic disks." I know this is true because I can still see the volumes
of my failed drive, it will not however recognize that HD as matching with
the missing HD. So my theory is this: I should be able to read the sector on
my good HD that contains the LDM database, then copy that information to my
failed HD, and it will be recognized as dynamically linked again.
If this will not work for me, please let me know... even if you may not have
a better alternative. I am having trouble understanding MS's description of
how to fix my problem as stated in KB 236086 due to what I consider an
inadequate description of how to modify in hex.
Thanks again.
your time. After coming back from a weekend when I turned my computer off,
it no longer would boot to my typical installation of Win XP Prox32bit. Upon
loading my secondary installation on another physical disk, I noticed that in
disk management, my other dynamic disk was showing up as "failed" and a new
disk had shown up that was basic and all free space.
To fill you in, I have two hard drives, both dynamic (first mistake), and
each drive has a mix of simple, striped, and spanned volumes. This secondary
windows installation is on a simple volume, and I have important data on a
simple volume on my failed drive.
I ran dmdiag.exe and found that my failed drive has a partition hex of 0x0F.
According to KB 320283, this is the same as 0x05 (extended partition) and
uses Logical Block Address Int 0x13 extensions. At this point I am no longer
concerned with how the MBR was changed. I am however, interested in changing
it back to recover my data and never to use dynamic disks again (not to
mention establish a backup plan). I have downloaded DiskProbe.exe and
examined my boot sectors. Comparing my "good drive" to my bad one, there
seems to be quite a few differences. I would cut and paste the info, but it
seems that diskprobe doesn't allow for notepad exportation, etc. I have no
clue what hexadecimal has to do with anything and it has always confused the
crap out of me. I have a theory. I read in KB 329707 that... "Dynamic disks
offer advantages over basic disks, which use the original MS-DOS-style master
boot record (MBR) partition tables to store primary and logical disk
partitioning information. Dynamic disks use a private region of the disk to
maintain a Logical Disk Manager (LDM) database, which contains volume types,
offsets, memberships, and drive letters of each volume. The LDM database is
also replicated, so each dynamic disk knows about every other dynamic disk
configuration. This feature makes dynamic disks more reliable and recoverable
than basic disks." I know this is true because I can still see the volumes
of my failed drive, it will not however recognize that HD as matching with
the missing HD. So my theory is this: I should be able to read the sector on
my good HD that contains the LDM database, then copy that information to my
failed HD, and it will be recognized as dynamically linked again.
If this will not work for me, please let me know... even if you may not have
a better alternative. I am having trouble understanding MS's description of
how to fix my problem as stated in KB 236086 due to what I consider an
inadequate description of how to modify in hex.
Thanks again.