CHKDSK went crazy on 200GB HD upon install!

[SurferBoy]

With the release of WinXP SP2, I decided to do a clean
reinstall. Oh, I wish I could go back in time to stop
myself!

My system: 60GB master HD (2 partitions), 200GB slave (1
partition) on a Promise Ultra100TX2 PCI controller card.
NTFS file system.

1. Ghosted the 60GB drive (actually just the 8GB c:
partition) to the 200GB drive.
2. Reinstalled WinXP Pro. Installation went without a
hitch.
3. Upon the first boot into Windows, chkdsk came up and
ran on the 200GB hard drive. Chkdsk went CRAZY, spewing
a huge list of index errors and recovering orphaned files
and various other things. The screen was scrolling like
mad. My heart sank.
4. Upon completion of the WinXP setup, I looked at the
200GB HD in Windows explorer. About 20GB or more of
stuff that was on the 200GB drive is missing. And much
of the stuff that IS there is now corrupted (including
the ghosted image of the c: drive!).

Here's what I think happened:
Unbeknownst to me, bare WinXP (without at least SP1) does
not support hard disks greater than 137GB. Apparently
though, not only does it not support the drives, it
actually attacks them; I think it chewed up the Master
File Table (MFT) or partition structure or something of
the kind. The file data is probably all still there on
the HD, but the pointers to the data have all been
screwed up. I disconnected the 200GB drive and finished
the installation to SP2.

Now, I'm stuck and don't know how best to proceed. I
don't want to make the problem any worse. I googled
around, and I have yet to find a solution. I'm actually
surprised this hasn't happened more often to people. I
have found some similar stories, such as, for instance,
http://www.windowsbbs.com/showthread.php?t=31921

Do I:
1. Re-connect the drive in WinXP SP2 and run scandisk or
Norton Disk Doctor to try to recover the original disk
structure? (I seriously doubt this will work)
2. Do I try some data recovery program like Ontrack Data
Recovery or GetDataBack?
3. Do I try some low-level program to try to
reconstruct, like SpinRite?
4. Is my "greater than 137 GB" theory about what caused
the long list of checkdisk problems even "correct"?

Any help or advice would be greatly appreciated!

 

[lobster]

True xp sp1 or above supports bigger hard drives anything
less no.
Your theroy on what happen to hard driver sound like
something it would do, to recover from it low level will
wipe the disk out, there might be a software that could
reconstruct the drive out there but don't have any help
there. Good luck

 

[Carey Frisch [MVP]]

I would suggest creating a "slipstreamed version" of Windows XP
with SP2 and perform a "clean install". The primary partition for
Windows XP should be at least 5% of your total hard drive, or 10GB.
You'll need to delete all existing partitions first before creating the
10GB (use 10240 to get a true 10GB partition) (10 x 1024).

Either one of the following utilities makes slipstreaming
(integrating) SP2 into Windows XP a breeze:

Windows Slipstreaming and Bootable CD Guide
http://www.msfn.org/articles.php?action=show&showarticle=49

Information on AutoStreamer 1.0
http://www.neowin.net/forum/index.php?showtopic=188337&st=0&#entry245

Windows XP Service Pack 2 - Direct Download
http://www.microsoft.com/downloads/...BE-3B8E-4F30-8245-9E368D3CDB5A&displaylang=en

Clean Install Windows XP
http://www.michaelstevenstech.com/cleanxpinstall.html

[Courtesy of MS-MVP Michael Stevens]

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default.aspx

---------------------------------------------------------------------------

:

| With the release of WinXP SP2, I decided to do a clean
| reinstall. Oh, I wish I could go back in time to stop
| myself!
|
| My system: 60GB master HD (2 partitions), 200GB slave (1
| partition) on a Promise Ultra100TX2 PCI controller card.
| NTFS file system.
|
| 1. Ghosted the 60GB drive (actually just the 8GB c:
| partition) to the 200GB drive.
| 2. Reinstalled WinXP Pro. Installation went without a
| hitch.
| 3. Upon the first boot into Windows, chkdsk came up and
| ran on the 200GB hard drive. Chkdsk went CRAZY, spewing
| a huge list of index errors and recovering orphaned files
| and various other things. The screen was scrolling like
| mad. My heart sank.
| 4. Upon completion of the WinXP setup, I looked at the
| 200GB HD in Windows explorer. About 20GB or more of
| stuff that was on the 200GB drive is missing. And much
| of the stuff that IS there is now corrupted (including
| the ghosted image of the c: drive!).
|
| Here's what I think happened:
| Unbeknownst to me, bare WinXP (without at least SP1) does
| not support hard disks greater than 137GB. Apparently
| though, not only does it not support the drives, it
| actually attacks them; I think it chewed up the Master
| File Table (MFT) or partition structure or something of
| the kind. The file data is probably all still there on
| the HD, but the pointers to the data have all been
| screwed up. I disconnected the 200GB drive and finished
| the installation to SP2.
|
| Now, I'm stuck and don't know how best to proceed. I
| don't want to make the problem any worse. I googled
| around, and I have yet to find a solution. I'm actually
| surprised this hasn't happened more often to people. I
| have found some similar stories, such as, for instance,
| http://www.windowsbbs.com/showthread.php?t=31921
|
| Do I:
| 1. Re-connect the drive in WinXP SP2 and run scandisk or
| Norton Disk Doctor to try to recover the original disk
| structure? (I seriously doubt this will work)
| 2. Do I try some data recovery program like Ontrack Data
| Recovery or GetDataBack?
| 3. Do I try some low-level program to try to
| reconstruct, like SpinRite?
| 4. Is my "greater than 137 GB" theory about what caused
| the long list of checkdisk problems even "correct"?
|
| Any help or advice would be greatly appreciated!

 

[Andy]

With the release of WinXP SP2, I decided to do a clean
reinstall. Oh, I wish I could go back in time to stop
myself!

My system: 60GB master HD (2 partitions), 200GB slave (1
partition) on a Promise Ultra100TX2 PCI controller card.
NTFS file system.

1. Ghosted the 60GB drive (actually just the 8GB c:
partition) to the 200GB drive.
2. Reinstalled WinXP Pro. Installation went without a
hitch.
3. Upon the first boot into Windows, chkdsk came up and
ran on the 200GB hard drive. Chkdsk went CRAZY, spewing
a huge list of index errors and recovering orphaned files
and various other things. The screen was scrolling like
mad. My heart sank.

At this point you should have aborted the operation by resetting the
computer. Actually you should have earlier prevented chkdsk from
running.
I had this happen once, but I did not let chkdsk run to completion.
Although I knew about this problem, I made the mistake of shutting my
eyes during the first setup phase, and when I opened my eyes after
dozing off for a short while, chkdsk was already running. I rebooted
into a working copy of Windows and looked at the drive. About half of
the folders were no longer there. I ran chkdsk without the /f. I don't
remember what chkdsk said about the state of the filesystem, but
apparently I liked what I saw, because I then ran chkdsk /f, and all
of the data on the drive ended up being restored.

4. Upon completion of the WinXP setup, I looked at the
200GB HD in Windows explorer. About 20GB or more of
stuff that was on the 200GB drive is missing. And much
of the stuff that IS there is now corrupted (including
the ghosted image of the c: drive!).

Here's what I think happened:
Unbeknownst to me, bare WinXP (without at least SP1) does
not support hard disks greater than 137GB. Apparently
though, not only does it not support the drives, it
actually attacks them; I think it chewed up the Master
File Table (MFT) or partition structure or something of
the kind. The file data is probably all still there on
the HD, but the pointers to the data have all been
screwed up. I disconnected the 200GB drive and finished
the installation to SP2.

Now, I'm stuck and don't know how best to proceed. I
don't want to make the problem any worse. I googled
around, and I have yet to find a solution. I'm actually
surprised this hasn't happened more often to people. I
have found some similar stories, such as, for instance,
http://www.windowsbbs.com/showthread.php?t=31921

Do I:
1. Re-connect the drive in WinXP SP2 and run scandisk or
Norton Disk Doctor to try to recover the original disk
structure? (I seriously doubt this will work)

If you don't want to make the problem worse, clone your 200GB hard
drive to another 200GB hard drive, and run chkdsk /f on the cloned
drive.

 

[SurferBoy]

Perhaps I wasn't clear enough in the original post. I
did complete the WinXP clean install and installed SP2.

My problem is with the 200GB slave disk, which was
corrupted by chkdsk when WinXP was in its original pre-
SP1 state. Currently, I have the 200GB drive
disconnected, as I do not want to do any further damage
until I know how best to proceed. So to summarize: I
want to correct the corruption that chkdsk caused on the
200GB drive during the first (pre-SP1) bootup.

Thanks!

-----Original Message-----
I would suggest creating a "slipstreamed version" of Windows XP
with SP2 and perform a "clean install". The primary partition for
Windows XP should be at least 5% of your total hard drive, or 10GB.
You'll need to delete all existing partitions first before creating the
10GB (use 10240 to get a true 10GB partition) (10 x 1024).

Either one of the following utilities makes slipstreaming
(integrating) SP2 into Windows XP a breeze:

Windows Slipstreaming and Bootable CD Guide
http://www.msfn.org/articles.php? action=show&showarticle=49

Information on AutoStreamer 1.0
http://www.neowin.net/forum/index.php? showtopic=188337&st=0&#entry245

Windows XP Service Pack 2 - Direct Download
http://www.microsoft.com/downloads/details.aspx? FamilyId=049C9DBE-3B8E-4F30-8245-
9E368D3CDB5A&displaylang=en

Clean Install Windows XP
http://www.michaelstevenstech.com/cleanxpinstall.html

[Courtesy of MS-MVP Michael Stevens]

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default. aspx

---------------------------------------------------------

------------------

:

| With the release of WinXP SP2, I decided to do a clean
| reinstall. Oh, I wish I could go back in time to stop
| myself!
|
| My system: 60GB master HD (2 partitions), 200GB slave (1
| partition) on a Promise Ultra100TX2 PCI controller card.
| NTFS file system.
|
| 1. Ghosted the 60GB drive (actually just the 8GB c:
| partition) to the 200GB drive.
| 2. Reinstalled WinXP Pro. Installation went without a
| hitch.
| 3. Upon the first boot into Windows, chkdsk came up and
| ran on the 200GB hard drive. Chkdsk went CRAZY, spewing
| a huge list of index errors and recovering orphaned files
| and various other things. The screen was scrolling like
| mad. My heart sank.
| 4. Upon completion of the WinXP setup, I looked at the
| 200GB HD in Windows explorer. About 20GB or more of
| stuff that was on the 200GB drive is missing. And much
| of the stuff that IS there is now corrupted (including
| the ghosted image of the c: drive!).
|
| Here's what I think happened:
| Unbeknownst to me, bare WinXP (without at least SP1) does
| not support hard disks greater than 137GB. Apparently
| though, not only does it not support the drives, it
| actually attacks them; I think it chewed up the Master
| File Table (MFT) or partition structure or something of
| the kind. The file data is probably all still there on
| the HD, but the pointers to the data have all been
| screwed up. I disconnected the 200GB drive and finished
| the installation to SP2.
|
| Now, I'm stuck and don't know how best to proceed. I
| don't want to make the problem any worse. I googled
| around, and I have yet to find a solution. I'm actually
| surprised this hasn't happened more often to people. I
| have found some similar stories, such as, for instance,
| http://www.windowsbbs.com/showthread.php?t=31921
|
| Do I:
| 1. Re-connect the drive in WinXP SP2 and run scandisk or
| Norton Disk Doctor to try to recover the original disk
| structure? (I seriously doubt this will work)
| 2. Do I try some data recovery program like Ontrack Data
| Recovery or GetDataBack?
| 3. Do I try some low-level program to try to
| reconstruct, like SpinRite?
| 4. Is my "greater than 137 GB" theory about what caused
| the long list of checkdisk problems even "correct"?
|
| Any help or advice would be greatly appreciated!
.

 

[Jim Macklin]

If the data is valuable, contact DriveSavers for advice.
CHKDSK finds lost clusters and saves each cluster with a
number and chk extension. You maybe able to open all the
hundreds of thousands/millions of clusters and determine
what the content is and re-assemble the original files. But
many are probably beyond economic recovery.
Do you have back-ups?

http://www.drivesavers.com/ They have lots of free
advice on their site.


--
The people think the Constitution protects their rights;
But government sees it as an obstacle to be overcome.


message | Perhaps I wasn't clear enough in the original post. I
| did complete the WinXP clean install and installed SP2.
|
| My problem is with the 200GB slave disk, which was
| corrupted by chkdsk when WinXP was in its original pre-
| SP1 state. Currently, I have the 200GB drive
| disconnected, as I do not want to do any further damage
| until I know how best to proceed. So to summarize: I
| want to correct the corruption that chkdsk caused on the
| 200GB drive during the first (pre-SP1) bootup.
|
| Thanks!
|
| >-----Original Message-----
| >I would suggest creating a "slipstreamed version" of
| Windows XP
| >with SP2 and perform a "clean install". The primary
| partition for
| >Windows XP should be at least 5% of your total hard
| drive, or 10GB.
| >You'll need to delete all existing partitions first
| before creating the
| >10GB (use 10240 to get a true 10GB partition) (10 x
| 1024).
| >
| >Either one of the following utilities makes
| slipstreaming
| >(integrating) SP2 into Windows XP a breeze:
| >
| >Windows Slipstreaming and Bootable CD Guide
| >http://www.msfn.org/articles.php?
| action=show&showarticle=49
| >
| >Information on AutoStreamer 1.0
| >http://www.neowin.net/forum/index.php?
| showtopic=188337&st=0&#entry245
| >
| >Windows XP Service Pack 2 - Direct Download
| >http://www.microsoft.com/downloads/details.aspx?
| FamilyId=049C9DBE-3B8E-4F30-8245-
| 9E368D3CDB5A&displaylang=en
| >
| >Clean Install Windows XP
| >http://www.michaelstevenstech.com/cleanxpinstall.html
| >
| >[Courtesy of MS-MVP Michael Stevens]
| >
| >--
| >Carey Frisch
| >Microsoft MVP
| >Windows XP - Shell/User
| >
| >Be Smart! Protect Your PC!
| >http://www.microsoft.com/athome/security/protect/default.
| aspx
| >
| >---------------------------------------------------------
| ------------------
| >
| >"SurferBoy" wrote:
| >
| >| With the release of WinXP SP2, I decided to do a clean
| >| reinstall. Oh, I wish I could go back in time to stop
| >| myself!
| >|
| >| My system: 60GB master HD (2 partitions), 200GB slave
| (1
| >| partition) on a Promise Ultra100TX2 PCI controller
| card.
| >| NTFS file system.
| >|
| >| 1. Ghosted the 60GB drive (actually just the 8GB c:
| >| partition) to the 200GB drive.
| >| 2. Reinstalled WinXP Pro. Installation went without
| a
| >| hitch.
| >| 3. Upon the first boot into Windows, chkdsk came up
| and
| >| ran on the 200GB hard drive. Chkdsk went CRAZY,
| spewing
| >| a huge list of index errors and recovering orphaned
| files
| >| and various other things. The screen was scrolling
| like
| >| mad. My heart sank.
| >| 4. Upon completion of the WinXP setup, I looked at
| the
| >| 200GB HD in Windows explorer. About 20GB or more of
| >| stuff that was on the 200GB drive is missing. And
| much
| >| of the stuff that IS there is now corrupted (including
| >| the ghosted image of the c: drive!).
| >|
| >| Here's what I think happened:
| >| Unbeknownst to me, bare WinXP (without at least SP1)
| does
| >| not support hard disks greater than 137GB. Apparently
| >| though, not only does it not support the drives, it
| >| actually attacks them; I think it chewed up the
| Master
| >| File Table (MFT) or partition structure or something
| of
| >| the kind. The file data is probably all still there
| on
| >| the HD, but the pointers to the data have all been
| >| screwed up. I disconnected the 200GB drive and
| finished
| >| the installation to SP2.
| >|
| >| Now, I'm stuck and don't know how best to proceed. I
| >| don't want to make the problem any worse. I googled
| >| around, and I have yet to find a solution. I'm
| actually
| >| surprised this hasn't happened more often to people.
| I
| >| have found some similar stories, such as, for
| instance,
| >| http://www.windowsbbs.com/showthread.php?t=31921
| >|
| >| Do I:
| >| 1. Re-connect the drive in WinXP SP2 and run scandisk
| or
| >| Norton Disk Doctor to try to recover the original disk
| >| structure? (I seriously doubt this will work)
| >| 2. Do I try some data recovery program like Ontrack
| Data
| >| Recovery or GetDataBack?
| >| 3. Do I try some low-level program to try to
| >| reconstruct, like SpinRite?
| >| 4. Is my "greater than 137 GB" theory about what
| caused
| >| the long list of checkdisk problems even "correct"?
| >|
| >| Any help or advice would be greatly appreciated!
| >.
| >