Paragon Backup and Recovery 0x12016 not resolving with chkdsk

Discussion in 'Paragon Drive Backup Product Line' started by Chumby, May 15, 2011.

Thread Status:
Not open for further replies.
  1. Chumby

    Chumby Registered Member

    Joined:
    May 15, 2011
    Posts:
    2
    The facts:

    Dell Dimension 8300
    250 Gig drive created with two drives paired with RAID (as from factory)
    Windows XP
    Paragon Backup & Recovery Free

    Keep getting the "Can't read volume data" error 0x12016. Ran chkdsk /r three times so far. How many times before I need to think of trying something else?

    Thanks all!!
     
  2. SIW2

    SIW2 Registered Member

    Joined:
    Sep 6, 2009
    Posts:
    1,572
    Does chkdsk keep repairing - or is it all clear?

    That sounds like a windows VSS error.

    Can you try Paragon Hot backup instead? Under Tools >Settings

    Otherwise - if you can make an image using Paragon boot disc - that would indicate a problem with windows itself.
     
    Last edited: May 17, 2011
  3. Chumby

    Chumby Registered Member

    Joined:
    May 15, 2011
    Posts:
    2
    Thanks for the answer SIW2,

    I spent some time in Event Viewer and found that after three or four runs of chkdsk, I still have 4k of bad sectors. No recent VSS errors (did get one when I ran microsoft backup a few weeks ago).

    Ran Western Digital (WD) Disk diagnostics and it is offering to repair my bad sectors...the caveat being that it will delete what is in those sectors.

    Do I risk it on a 250 gig disk drive? It's "only" 4k!! Is there a disk repair utility with a lower loss rate, or even a save rate?

    Haven't tried the Paragon Hot setting; that's next before the disk repair.
     
  4. SIW2

    SIW2 Registered Member

    Joined:
    Sep 6, 2009
    Posts:
    1,572
    Try Paragon Hot backup and see if it will do the job.

    Otherwise - you need to repair those sectors.

    As far as I know - there isn't any alternative to losing what is in the sectors that are repaired.
     
Loading...
Thread Status:
Not open for further replies.