Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > NZ Computing > chkdsk destroys NTFS files

Reply
Thread Tools

chkdsk destroys NTFS files

 
 
Gurble
Guest
Posts: n/a
 
      03-05-2005
On Sat, 05 Mar 2005 20:59:13 +0000, anon <(E-Mail Removed)> had this to say:

>Gee, thanks Microsoft. After reinstalling Windows 2000 chkdsk decides it
>needs to check the NTFS partition. After two hours of waiting for the
>pointless f**king messages saying what it's doing scroll past the end
>result is that many of the files on this partition have been zeroed. Can
>you f**king believe that? And I made this partition NTFS because it was
>supposedly safer.


Yup, I've had the same thing happen with CHKDSK. It's unstable.

>Is there any way of recovering this data?


Not from Microsoft. Fortunately there are plenty of other companies
around that have a few more clues than MS.

Try R-Studio. If anything'll get it back, it will.
 
Reply With Quote
 
 
 
 
Peter Huebner
Guest
Posts: n/a
 
      03-05-2005
In article <(E-Mail Removed)>, http://www.velocityreviews.com/forums/(E-Mail Removed)
says...
>
> Yup, I've had the same thing happen with CHKDSK. It's unstable.
>
> >Is there any way of recovering this data?

>
> Not from Microsoft. Fortunately there are plenty of other companies
> around that have a few more clues than MS.


OS/2 did it to me. Power surge, computer reset, reboot ran chkdsk.
Chkdsk decided there were maybe crosslinks and proceeded to move all
files to the root directory of the drive, renaming them chkdsk0000,
chkdsk0001 et cetera - you get the picture.
Then it flooded its stack and crashed. 1500 files or so renamed to
meaningless dross, with no indication of what they had been. IBM
helpdesk didn't have a clue what to do about it.

I did: I installed a different operating system :-\ but I lost nearly
all my source code in that little incident. Had no backups since I was
still building the system up at the time.

Long time ago (nearly 15 years?), I own a UPS now, and I make backups
from the very start .

-P.
 
Reply With Quote
 
 
 
 
anon
Guest
Posts: n/a
 
      03-05-2005
Gee, thanks Microsoft. After reinstalling Windows 2000 chkdsk decides it
needs to check the NTFS partition. After two hours of waiting for the
pointless f**king messages saying what it's doing scroll past the end
result is that many of the files on this partition have been zeroed. Can
you f**king believe that? And I made this partition NTFS because it was
supposedly safer.

Is there any way of recovering this data?
 
Reply With Quote
 
whoisthis
Guest
Posts: n/a
 
      03-05-2005
In article <(E-Mail Removed). nz>,
Peter Huebner <(E-Mail Removed)> wrote:

> In article <(E-Mail Removed)>, (E-Mail Removed)
> says...
> >
> > Yup, I've had the same thing happen with CHKDSK. It's unstable.
> >
> > >Is there any way of recovering this data?

> >
> > Not from Microsoft. Fortunately there are plenty of other companies
> > around that have a few more clues than MS.

>
> OS/2 did it to me. Power surge, computer reset, reboot ran chkdsk.
> Chkdsk decided there were maybe crosslinks and proceeded to move all
> files to the root directory of the drive, renaming them chkdsk0000,
> chkdsk0001 et cetera - you get the picture.
> Then it flooded its stack and crashed. 1500 files or so renamed to
> meaningless dross, with no indication of what they had been. IBM
> helpdesk didn't have a clue what to do about it.


IIRC Microsoft wrote the original OS2 for IBM too.
 
Reply With Quote
 
Peter Huebner
Guest
Posts: n/a
 
      03-05-2005
In article <(E-Mail Removed)>, (E-Mail Removed)mer
says...
>
> IIRC Microsoft wrote the original OS2 for IBM too.
>


Yes, the HPFS was jointly developed and so presumably were the utilities
for it.
In fact, Microsoft had the option of using HPFS for Windows and WinNT
because they were joint owners of the rights to it, but they chose to go
the path of incompatibility even though all the boffins at the time
pointed out that HPFS was superior to Fat and NTFS ...
... well we all know that MS turned incompatibility into an artform
for many years, don't we <g>. )*

-P.



)* i.e. the art of putting the opposition out of business
 
Reply With Quote
 
Enkidu
Guest
Posts: n/a
 
      03-06-2005
Gurble wrote:
> On Sat, 05 Mar 2005 20:59:13 +0000, anon <(E-Mail Removed)> had this to say:
>
>
>>Gee, thanks Microsoft. After reinstalling Windows 2000 chkdsk decides it
>>needs to check the NTFS partition. After two hours of waiting for the
>>pointless f**king messages saying what it's doing scroll past the end
>>result is that many of the files on this partition have been zeroed. Can
>>you f**king believe that? And I made this partition NTFS because it was
>>supposedly safer.

>
> Yup, I've had the same thing happen with CHKDSK. It's unstable.
>

Rubbish! I've never had any problems with chkdsk in few
times that something has been *that* wrong with the hard
disk. If chkdsk automatically runs it means that something
is seriously wrong. The problems whatever they were already
there. Chkdsk merely found them. I suspect that whatever
caused the OP poster to reinstall 2000 was the cause of the
disk problems and chkdsk merely found them. It doesn't do
anything to files, except move them to the root directory
and change their names. If they now contain zeros it was
because they contained zeros before chkdsk ran.

Cheers,

Cliff

--

Barzoomian the Martian - http://barzoomian.blogspot.com
 
Reply With Quote
 
Gurble
Guest
Posts: n/a
 
      03-06-2005
On Sun, 06 Mar 2005 15:00:26 +1300, Enkidu <(E-Mail Removed)>
had this to say:

>Gurble wrote:
>> On Sat, 05 Mar 2005 20:59:13 +0000, anon <(E-Mail Removed)> had this to say:
>>
>>
>>>Gee, thanks Microsoft. After reinstalling Windows 2000 chkdsk decides it
>>>needs to check the NTFS partition. After two hours of waiting for the
>>>pointless f**king messages saying what it's doing scroll past the end
>>>result is that many of the files on this partition have been zeroed. Can
>>>you f**king believe that? And I made this partition NTFS because it was
>>>supposedly safer.

>>
>> Yup, I've had the same thing happen with CHKDSK. It's unstable.
>>

>Rubbish! I've never had any problems with chkdsk in few
>times that something has been *that* wrong with the hard
>disk. If chkdsk automatically runs it means that something
>is seriously wrong. The problems whatever they were already
>there. Chkdsk merely found them. I suspect that whatever
>caused the OP poster to reinstall 2000 was the cause of the
>disk problems and chkdsk merely found them. It doesn't do
>anything to files, except move them to the root directory
>and change their names. If they now contain zeros it was
>because they contained zeros before chkdsk ran.
>

Oh. Because you've never had any problems the "few times" you've run
it, it must be OK then...

Just ignore the fact that there are thousands of reports from people
who have had major problems with it.
 
Reply With Quote
 
My
Guest
Posts: n/a
 
      03-06-2005
On Sun, 06 Mar 2005 15:15:37 +1300, Gurble <(E-Mail Removed)> wrote:


>Just ignore the fact that there are thousands of reports from people
>who have had major problems with it.


Thousand of people like you who don't know what they are talking
about, your data was stuffed already.
You dont know what your talking about - related to roger?




 
Reply With Quote
 
mark
Guest
Posts: n/a
 
      03-06-2005
Enkidu <(E-Mail Removed)> wrote in news:422a6452$1
@news2.actrix.gen.nz:

> Gurble wrote:
>> On Sat, 05 Mar 2005 20:59:13 +0000, anon <(E-Mail Removed)> had this to say:
>>
>>
>>>Gee, thanks Microsoft. After reinstalling Windows 2000 chkdsk decides it
>>>needs to check the NTFS partition. After two hours of waiting for the
>>>pointless f**king messages saying what it's doing scroll past the end
>>>result is that many of the files on this partition have been zeroed. Can
>>>you f**king believe that? And I made this partition NTFS because it was
>>>supposedly safer.

>>
>> Yup, I've had the same thing happen with CHKDSK. It's unstable.
>>

> Rubbish! I've never had any problems with chkdsk in few
> times that something has been *that* wrong with the hard
> disk. If chkdsk automatically runs it means that something
> is seriously wrong. The problems whatever they were already
> there. Chkdsk merely found them. I suspect that whatever
> caused the OP poster to reinstall 2000 was the cause of the
> disk problems and chkdsk merely found them. It doesn't do
> anything to files, except move them to the root directory
> and change their names. If they now contain zeros it was
> because they contained zeros before chkdsk ran.
>
> Cheers,
>
> Cliff
>



*******s. I've had volumes with minor problems (eg., one directory corrupt,
able to read every other file) turn to complete custard after a chkdsk was
run over it. It looked as though the start of several THOUSAND files were
helpfully zeroed by chkdsk, and none of the tools I could lay my hands on
were able to undo the damage.

Bottom line: any disk "repair" tool without an undo feature isn't worth a
pile of dogs poo.
 
Reply With Quote
 
Enkidu
Guest
Posts: n/a
 
      03-06-2005
mark wrote:
> Enkidu <(E-Mail Removed)> wrote in news:422a6452$1
> @news2.actrix.gen.nz:
>
>>Rubbish! I've never had any problems with chkdsk in few
>>times that something has been *that* wrong with the hard
>>disk. If chkdsk automatically runs it means that something
>>is seriously wrong. The problems whatever they were already
>>there. Chkdsk merely found them. I suspect that whatever
>>caused the OP poster to reinstall 2000 was the cause of the
>>disk problems and chkdsk merely found them. It doesn't do
>>anything to files, except move them to the root directory
>>and change their names. If they now contain zeros it was
>>because they contained zeros before chkdsk ran.

>
> *******s. I've had volumes with minor problems (eg., one
> directory corrupt, able to read every other file) turn to
> complete custard after a chkdsk was run over it. It looked
> as though the start of several THOUSAND files were helpfully
> zeroed by chkdsk, and none of the tools I could lay my hands
> on were able to undo the damage.
>

You had a buggered disk to start with. You should have
copied the data off it before you ran chkdsk. I hope you had
backups.

Specialists recommend that you don't run chkdsk. Ever. But
that's not because it corrupts file systems. It doesn't. It
attempts to repair filesystems problems, but if the problem
is NOT a filesystem problem, but is a disk problem, then you
will end up with a corrupt disk and filesystem.

Example:

http://www.dataclinic.co.uk/scandisk...r-software.htm

I'd say that you have some disk problem and running chkdsk
was the last thing that you should have done.
>
> Bottom line: any disk "repair" tool without an undo feature
> isn't worth a pile of dogs poo.
>

chkdsk is not a disk repair tool. It is a filesystem repair
tool.

Cheers,

Cliff

--

Barzoomian the Martian - http://barzoomian.blogspot.com
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How to run CHKDSK on NTFS file system which crashes Windows? peter.capek@gmail.com Computer Support 5 03-31-2008 03:48 AM
Programmatic OleDB access destroys current Session daver@csh.rit.edu ASP .Net 6 06-30-2005 10:12 AM
Firefox Destroys my Computer margon21@hotmail.com Firefox 8 11-14-2004 10:42 PM
Install of SP1 to WinXP Pro destroys dual boot function of Win98/WinXPsystem Richard Owlett Computer Support 5 07-27-2004 07:49 AM
Creating a batch to determine if HD is NTFS if not format it NTFS Tech Computer Support 3 04-06-2004 06:19 PM



Advertisments