Backup Reports Disk Errors At End of Backup

Discussion in 'Paragon Drive Backup Product Line' started by i_am_jim, Apr 20, 2015.

  1. i_am_jim

    i_am_jim Registered Member

    Joined:
    Sep 27, 2010
    Posts:
    29
    After 2+ hours, at end of Clone Backup, Paragon Disk Manager reports disk errors on source disk. Does this repeatedly! I have used this utility several (many?) times in the past with no problems on the same disk and operating system. Windows 8 reports no disk errors on drive.

    Whato_O?
     
  2. Robin A.

    Robin A. Registered Member

    Joined:
    Feb 25, 2006
    Posts:
    2,279
    First step would be to run chkdsk.
     
  3. i_am_jim

    i_am_jim Registered Member

    Joined:
    Sep 27, 2010
    Posts:
    29
    First Microsoft says there is no need on Windows 8 because it does routine checking. But I did anyway and it reported no errors.
     
  4. John2222

    John2222 Registered Member

    Joined:
    Sep 27, 2005
    Posts:
    140
    Did you run the full chkdsk scan? chkdsk c: /r and then check y when asked if to run during restart. Then restart your pc.
    the /r option causes windows to read every sector checking for errors.
     
  5. i_am_jim

    i_am_jim Registered Member

    Joined:
    Sep 27, 2010
    Posts:
    29
    No, I just ran chkdsk with no arguments. I thought that allowed it to check everything since it's read only.
     
  6. John2222

    John2222 Registered Member

    Joined:
    Sep 27, 2005
    Posts:
    140
    When you run chkdsk with no arguments, Windows checks the file structure, index, pointers etc. but not the actual sectors. That's why it only takes a minute or so to run. If there is a bad sector, it won't be detected by just chkdsk c: The chkdsk c: /r also reads all sectors and attempts to recover bad sectors (can take an hour or so on large disk). The results are in the Windows log which you can find after windows restarts:
    This PC /right click
    Manage
    Event Viewer/Windows Logs/Applications
    Then look for Winit entry for the chkdsk results.

    https://technet.microsoft.com/en-us/magazine/ee872425.aspx
     
  7. i_am_jim

    i_am_jim Registered Member

    Joined:
    Sep 27, 2010
    Posts:
    29
    I ran with /r option and it stopped at 10% for 7 and a half hours and finally completed. Once it left 10% it went almost immediately to 100%. Scared me though. I thought I'd lost my Win8 installation.

    I have no idea what it means but this is the log:

    Fault bucket -218740401, type 5
    Event Name: StartupRepairOnline
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 6.3.9600.16384
    P2: 6.3.9600.16384
    P3: LENOVO
    P4: 123
    P5: 0
    P6: AutoFailover
    P7: 1
    P8: unknown
    P9:
    P10:

    Attached files:

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_6.3.9600.16384_6474e1cfafef24183e5a24ebbe330cc045629c_00000000_01054660

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 765a52ea-e7d7-11e4-bf81-7427ea647e8a
    Report Status: 0
    Hashed bucket: 0c747d5cde23b68eab595a8dd19bd2c7
     
  8. John2222

    John2222 Registered Member

    Joined:
    Sep 27, 2005
    Posts:
    140
    I don't know what that error log means either. Maybe someone else here can explain.

    Did you get the results of the chkdsk c: /r from the Application Log? It is an event id 1001, Wininit and should look something like this (below). If there were errors in yours, the program attempts to correct them. You can try the backup again now, but what you copied appears to be some other Windows error.

    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is OS.

    A disk check has been scheduled.
    Windows will now check the disk.

    Stage 1: Examining basic file system structure ...
    331520 file records processed. File verification completed.
    5145 large file records processed. 0 bad file records processed.
    Stage 2: Examining file name linkage ...
    424618 index entries processed. Index verification completed.
    0 unindexed files scanned. 0 unindexed files recovered.
    Stage 3: Examining security descriptors ...
    Cleaning up 192 unused index entries from index $SII of file 0x9.
    Cleaning up 192 unused index entries from index $SDH of file 0x9.
    Cleaning up 192 unused security descriptors.
    Security descriptor verification completed.
    46550 data files processed. CHKDSK is verifying Usn Journal...
    40338808 USN bytes processed. Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    239447039 KB total disk space.
    96966036 KB in 256580 files.
    159276 KB in 46551 indexes.
    0 KB in bad sectors.
    447935 KB in use by the system.
    65536 KB occupied by the log file.
    141873792 KB available on disk.

    4096 bytes in each allocation unit.
    59861759 total allocation units on disk.
    35468448 allocation units available on disk.

    Windows has finished checking your disk.
    Please wait while your computer restarts.
     
  9. garioch7

    garioch7 Registered Member

    Joined:
    Nov 17, 2011
    Posts:
    61
    Location:
    Canada
    That is a scary result indeed from a chkdsk /r run. Like John2222 said, you should have a nice chkdsk report like he posted above in your Event Viewer. I am guessing impending hard drive failure, which would explain the unsuccessful clone. I would immediately run the hard drive diagnostic utility appropriate for your make of hard drive. They are available at the manufacturer's website. You can also take a wander over to the Bleeping Computer Forums for Windows 8.1 and post that log file that you got, and some of the pros there will attempt to assist you diagnose what is going on. That log is beyond my knowledge level, except to know enough that chkdsk stalling for 7 hours at 10 percent and then suddenly finishing is NOT normal behaviour for chkdsk. I doubt this is a Paragon issue. Sounds like hard drive hardware issue.

    Hope this helps. Have a great day.

    Regards,
    -Phil
     
  10. John2222

    John2222 Registered Member

    Joined:
    Sep 27, 2005
    Posts:
    140
    i_am_jim, Were you able to run a full backup without errors after the chkdsk?

    I don't think the error you posted above came from the chkdsk program. I wonder if you opened the Windows Logs/System and saw one or more errors? And that is what you posted.

    The chkdsk results are recorded in the Windows Logs/Application section.

    However, anytime you have strange problems it is a good idea to check the system log. I agree with garioch7 that you may have an impending hard drive failure, or some other system error related to i/o to or from the disk drive.

    Here is one comment I found from Google searching for the error you originally posted above: Fault bucket type 5 Event Name: StartupRepairOnline
    https://social.msdn.microsoft.com/F...ting-fault-bucket-3743235631-type-5?forum=wpf
     
Loading...