Jump to content
James Harris

Chipset Driver update broke Retrospect

Recommended Posts

I have run Retrospect on this machine using two backup sets on two separate USB drives for about a year and a half without any issues.  I installed an update to my motherboard's chipset drivers and since then, I get write errors almost immediately after starting a backup.  Tried different ports & different cables.  What is even more interesting is I copied a few TB using GoodSync & TeraCopy with verify on & both ran flawlessly,  It appears to be some type of conflict between Retrospect & the version of these drivers.  At this point, I have stopped running Retrospect after spending many hours trying to find the cause.  If anyone has any suggestions, let me know.  Since I can't rollback chipset drivers, I think my only options are to wipe/re-install Windows or wait for a new version of the chipset drivers or Retrospect & cross my fingers.  Since Retrospect is just one prong of my backup strategy, at this point, I am not willing to redo my entire OS installation.

Here is a sample log:


+    Recycle backup using Data at 3/2/2020 1:21 PM (Execution unit 1)
        3/2/2020 1:21:53 PM: Finished scanning backup set data files
    To Backup Set Backup Set A...
    3/2/2020 1:21:08 PM: Recycle backup: The Backup Set was reset

-    3/2/2020 1:21:08 PM: Copying data on Data (I:)
        3/2/2020 1:23:05 PM: Found: 86,121 files, 8,105 folders, 352.6 GB
        3/2/2020 1:23:06 PM: Finished matching
    3/2/2020 1:23:06 PM: Selector "All Files" was used to select 86,121 files out of 86,121.
        3/2/2020 1:23:07 PM: Copying: 86,121 files (352.6 GB) and 0 hard links
        [*] MapError: unknown Windows error 483
        [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000000.rdb, osErr 483, error -1001
        [*] MapError: unknown Windows error 483
        [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000000.rdb, osErr 483, error -1001
        [*] xopFlush: flush failed, error -102 (trouble communicating)
        [*] xopFlush: flush failed, error -102 (trouble communicating)
        Trouble writing: "1-Backup Set A" (629145600), error -102 (trouble communicating)
        Trouble writing media:
            "1-Backup Set A"
        error -102 (trouble communicating)
        [*] MapError: unknown Windows error 483
        [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000001.rdb, osErr 483, error -1001
        [*] MapError: unknown Windows error 483
        [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000001.rdb, osErr 483, error -1001
        [*] xopFlush: flush failed, error -102 (trouble communicating)
        [*] xopFlush: flush failed, error -102 (trouble communicating)
        Trouble writing: "1-Backup Set A" (1258291200), error -102 (trouble communicating)
        Trouble writing media:
            "1-Backup Set A"
        error -102 (trouble communicating)
        [*] MapError: unknown Windows error 483
        [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000002.rdb, osErr 483, error -1001
        [*] MapError: unknown Windows error 483
        [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000002.rdb, osErr 483, error -1001
        [*] xopFlush: flush failed, error -102 (trouble communicating)
        [*] xopFlush: flush failed, error -102 (trouble communicating)
        Trouble writing: "1-Backup Set A" (1887436800), error -102 (trouble communicating)
        Trouble writing media:
            "1-Backup Set A"
        error -102 (trouble communicating)
        [*] MapError: unknown Windows error 483
        [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000003.rdb, osErr 483, error -1001
        [*] MapError: unknown Windows error 483
        [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000003.rdb, osErr 483, error -1001
        [*] xopFlush: flush failed, error -102 (trouble communicating)
    3/2/2020 1:23:57 PM: Execution stopped by operator        Remaining: 80289 files, 350.7 GB
        Completed: 5832 files, 1.9 GB
        Performance: 2274.7 MB/minute
        Duration: 00:02:49 (00:01:59 idle/loading/preparing)

        3/2/2020 1:23:57 PM: Compressing catalog file
 

Share this post


Link to post
Share on other sites

You don't say what version of Retrospect you are running, nor Windows. Are they the latest of both?

Are you backing up from/to USB devices? Take those out of the testing by using RS to back up a small folder on your system disk to a new disk set on the same drive.

More data == better bug report == more chance of a quick fix.

Share this post


Link to post
Share on other sites

Latest versions of both...all updates applied

As the log says "Trouble writing", I am backing up TO the disks.

I have tried different folders.  Seems like it goes fine for around the first gig & then errors start popping u,p

Share this post


Link to post
Share on other sites
3 hours ago, James Harris said:

I have tried different folders.

Different folders, but still using an external drive? Or different folders on the system drive? Just trying to eliminate USB from the equation.

Also, soon after my last post I got an announcement about RSv17 -- so you could grab the trial and try that.

Share this post


Link to post
Share on other sites

R17 has same problem.  Backing up to NAS works without error.  That, and due to the fact that it did work before the chipset drivers update, it is definitely an USB problem.  I guess I'll just wait for the next chipset driver update & see what happens

Share this post


Link to post
Share on other sites
5 hours ago, James Harris said:

Latest versions of both...all updates applied

That will not be very informative 6 months (or more) from now. ;) 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×