chkdsk destroys NTFS files

Discussion in 'NZ Computing' started by Gurble, Mar 5, 2005.

  1. Gurble

    Gurble Guest

    On Sat, 05 Mar 2005 20:59:13 +0000, anon <> 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.
    Gurble, Mar 5, 2005
    #1
    1. Advertising

  2. In article <>,
    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.
    Peter Huebner, Mar 5, 2005
    #2
    1. Advertising

  3. Gurble

    anon Guest

    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?
    anon, Mar 5, 2005
    #3
  4. Gurble

    whoisthis Guest

    In article <>,
    Peter Huebner <> wrote:

    > In article <>,
    > 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.
    whoisthis, Mar 5, 2005
    #4
  5. In article <>, 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
    Peter Huebner, Mar 5, 2005
    #5
  6. Gurble

    Enkidu Guest

    Gurble wrote:
    > On Sat, 05 Mar 2005 20:59:13 +0000, anon <> 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
    Enkidu, Mar 6, 2005
    #6
  7. Gurble

    Gurble Guest

    On Sun, 06 Mar 2005 15:00:26 +1300, Enkidu <>
    had this to say:

    >Gurble wrote:
    >> On Sat, 05 Mar 2005 20:59:13 +0000, anon <> 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.
    Gurble, Mar 6, 2005
    #7
  8. Gurble

    My Guest

    On Sun, 06 Mar 2005 15:15:37 +1300, Gurble <> 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?
    My, Mar 6, 2005
    #8
  9. Gurble

    mark Guest

    Enkidu <> wrote in news:422a6452$1
    @news2.actrix.gen.nz:

    > Gurble wrote:
    >> On Sat, 05 Mar 2005 20:59:13 +0000, anon <> 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
    >



    Bollocks. 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.
    mark, Mar 6, 2005
    #9
  10. Gurble

    Enkidu Guest

    mark wrote:
    > Enkidu <> 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.

    >
    > Bollocks. 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-chkdsk-disk-checking-repair-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
    Enkidu, Mar 6, 2005
    #10
  11. Gurble

    SchoolTech Guest

    In article <> in nz.comp on Sat, 05 Mar 2005
    20:59:13 +0000, anon <> says...
    > 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?


    From a stuffed HDD, no. Since this is the most likely reason a ChkDsk is
    forced.

    Had this with a machine this week, XP became corrupted and would not
    boot. After formatting and reinstall ChkDsk kept running at startup so I
    replaced the drive, no further problems.
    SchoolTech, Mar 6, 2005
    #11
  12. Gurble

    SchoolTech Guest

    In article <422a6452$> in nz.comp on Sun, 06 Mar
    2005 15:00:26 +1300, Enkidu <> says...
    > Gurble wrote:
    > > On Sat, 05 Mar 2005 20:59:13 +0000, anon <> 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.


    Yes, this is what we had happen last week on a Windows XP machine.
    Windows bootup refused to continue because of missing files and a BartsPE
    boot CD was unable to read the disk.

    The HDD was replaced and now the machine is working well.
    SchoolTech, Mar 6, 2005
    #12
  13. Gurble

    Bob McLellan Guest

    This scenario sems to happen when you get a restart while in the middle
    of doing an initial chkdsk.

    Enkidu wrote:
    > Gurble wrote:
    >
    >> On Sat, 05 Mar 2005 20:59:13 +0000, anon <> 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
    >
    Bob McLellan, Mar 7, 2005
    #13
  14. Gurble

    My Guest

    On Mon, 07 Mar 2005 07:45:01 +0000, Bob McLellan <>
    wrote:

    >This scenario sems to happen when you get a restart while in the middle
    >of doing an initial chkdsk.

    well there you go, computer restarts,.
    flakey hardware
    My, Mar 7, 2005
    #14
  15. Gurble

    mark Guest

    Enkidu <> wrote in
    news:422ad352$:

    > mark wrote:
    >> Enkidu <> 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.

    >>
    >> Bollocks. 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,



    Bollocks. The disk was, and still is, fine physically.

    These were logical errors, and chkdsk turned a situation of one
    directory that couldn't be browsed into one where thousands of files
    were unrecoverable.


    > then you will end up with a corrupt disk and filesystem.
    >
    > Example:
    >
    > http://www.dataclinic.co.uk/scandisk-chkdsk-disk-checking-repair-

    softwa
    > re.htm
    >
    > I'd say that you have some disk problem



    You'd be wrong too.


    > and running chkdsk was the last thing that you should have done.



    Yes, I should have thought no undo feature, don't go there, even if it
    is a Microsoft supplied tool for a Microsoft operating system. Tough
    lesson.


    >> 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.



    OFFS, don't be such a pedant.


    > Cheers,
    >
    > Cliff
    >
    mark, Mar 7, 2005
    #15
  16. Gurble

    MarkH Guest

    anon <> wrote in news::

    > 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?


    Surely restoring the data from the last good backup is the logical solution
    here?

    I've never heard anyone (not even MS) suggest that NTFS is so safe that you
    don't need backups of important data.



    --
    Mark Heyes (New Zealand)
    See my pics at www.gigatech.co.nz (last updated 20-Jan-05)
    "There are 10 types of people, those that
    understand binary and those that don't"
    MarkH, Mar 8, 2005
    #16
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Replies:
    8
    Views:
    504
    Steve Franklin
    Nov 14, 2004
  2. Richard Owlett
    Replies:
    5
    Views:
    877
    Wilhelm Tell
    Jul 27, 2004
  3. Kevin

    Floppy drive destroys disks

    Kevin, Dec 22, 2004, in forum: Computer Support
    Replies:
    4
    Views:
    562
    Dr. Harvie Wahl-Banghor
    Dec 22, 2004
  4. Terry Pinnell

    Thumbs Plus destroys EXIF?

    Terry Pinnell, Dec 2, 2004, in forum: Digital Photography
    Replies:
    20
    Views:
    727
    J├╝rgen Eidt
    Dec 11, 2004
  5. Replies:
    5
    Views:
    1,922
Loading...

Share This Page