chkdsk -> crash /reboot

[Lew]

I'm having system problems which seem to center around my g: drive, an old
Quantum Fireball P/LM20.5 I'm running Windows Xp (Pro)/sp2. I use NTFS on
every drive. Here are some reproducible symptoms:

1. I start in safe mode w/command prompt
2. I run chkdsk g: /f
3. 1st step runs ok
4. Next step checking indexes stops after a few seconds and my machine
reboots.

So, is this drive savable? Can I get Windows to regenerate the drive indexes
without damaging the data on the drive? Suggestions?

-Lew

 

[Guest]

No there is lots of software that will recover data for you. The best one
that i know of is R-Studio 2.0, which has saved my backside many a time, you
can download a trial to check if it will work first

Cheers

Quintin


--
Quintin Rares
MVP wannabe
Owner of:
- The Technology Store Australia
- 2x Athlon 64 systems
- two tablet PCs - Toshiba M200 and the Acer c303Xmi
Beta tester of Office 11, Win update...

 

[Rick \Nutcase\ Rogers]

Hi,

Head to maxtor's site (they took over Quantum) and see if they have a drive
diagnostic available for it. This tool should give you an idea of the state
of the drive.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[cquirke (MVP Windows shell/user)]

I'm having system problems which seem to center around my g: drive, an old
Quantum Fireball P/LM20.5 I'm running Windows Xp (Pro)/sp2. I use NTFS on
every drive. Here are some reproducible symptoms:

1. I start in safe mode w/command prompt
2. I run chkdsk g: /f
3. 1st step runs ok
4. Next step checking indexes stops after a few seconds and my machine
reboots.

So, is this drive savable? Can I get Windows to regenerate the drive indexes
without damaging the data on the drive? Suggestions?

I'd get OUT of Windows and use BING (www.bootitng.com) to image that
NTFS partition from the sick HD to a new one, then try the new one
within the OS again. If that works, the old HD is prolly bad. If it
fails the same way, then the NTFS file system structure is likely
barfed to the point that it kills ChkDsk.

If the latter, I'd do a file-level evacuation either via the OS, or
from a Bart's PE CDR boot. The latter's kinder to the installation as
it runs in RAMdisk and is less likely to barf your C: if it resets.

Good luck finding interactive file system repair tools for NTFS.

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

Gone to bloggery: http://cquirke.blogspot.com