Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Macrium Reflect Win7 back up fails - 0x80042301


  • Please log in to reply
7 replies to this topic

#1 Expert Novice

Expert Novice

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Local time:12:56 AM

Posted 05 March 2012 - 03:04 PM

When attempting to make a back up image of my local drives Macrium Reflect free edition gives error code 0x80042301. A google search of the error code took me to this page which tells me... 'The windows snapshot component VSS will fail if a disk with a non standard sector size is attached to your system, even if this disk is either being backed up or used to store the image files. This can be an internal disk or one connected by USB or eSata. These disks are fortunately rare, and are typically found only in sizes of 1TB or above.'

Looking in System Information reveals my Seagate Expansion 3tb external drive to which I'm trying to save the back up image has a non standard byte/sector of 4096. According to the page noted above anything other than 512 is considered non standard.

Ok, fair enough, but I have previously made and restored successful back ups with the Seagate using Macrium and as far as I can see nothing has changed since then. Obviously something is different though but I don't know where else to look so could someone suggest where on my machine I might look to find why this has started happening when all was previosly well and what I might try to get my back up working again. Is it possible to reformat the Seagate drive so it has a bytes/sector of 512?

Posted below is the log from Macrium. You can see the error right at the bottom.

Machine is a Hp g6 laptop running Windows 7 Home Premium.

Thanks for reading.


- Mark all writers as succesfully backed up...
Completing the backup (BackupComplete) ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
(Gathering writer metadata...)
(Waiting for the asynchronous operation to finish...)
Initialize writer metadata ...
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
Discover directly excluded components ...
- Excluding writer '' since it has no selected components for restore.
- Excluding writer '' since it has no selected components for restore.
- Excluding writer 'Shadow Copy Optimization Writer' since it has no selected components for restore.
- Excluding writer 'MSSearch Service Writer' since it has no selected components for restore.
Discover components that reside outside the shadow set ...
Discover all excluded components ...
Discover excluded writers ...
Discover explicitly included components ...
Verifying explicitly specified writers/components ...
Select explicitly included components ...
* Writer 'Task Scheduler Writer':
- Add component \TasksStore
* Writer 'VSS Metadata Store Writer':
- Add component \WriterMetadataStore
* Writer 'Performance Counters Writer':
- Add component \PerformanceCounters
* Writer 'Registry Writer':
- Add component \Registry
* Writer 'COM+ REGDB Writer':
- Add component \COM+ REGDB
* Writer 'WMI Writer':
- Add component \WMI
Creating shadow set {a3d65079-ee05-4ced-ab02-81c6c7844327} ...
- Adding volume \\?\Volume{d58171e8-41d4-11e1-82f5-806e6f6e6963}\ [C:\] to the shadow set...
Preparing for backup ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Creating the shadow (DoSnapshotSet) ...
(Waiting for the asynchronous operation to finish...)
(Gathering writer metadata...)
(Waiting for the asynchronous operation to finish...)
Initialize writer metadata ...
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
Discover directly excluded components ...
- Excluding writer '' since it has no selected components for restore.
- Excluding writer '' since it has no selected components for restore.
- Excluding writer 'MSSearch Service Writer' since it has no selected components for restore.
- Excluding writer 'Shadow Copy Optimization Writer' since it has no selected components for restore.
Discover components that reside outside the shadow set ...
Discover all excluded components ...
Discover excluded writers ...
Discover explicitly included components ...
Verifying explicitly specified writers/components ...
Select explicitly included components ...
* Writer 'Task Scheduler Writer':
- Add component \TasksStore
* Writer 'VSS Metadata Store Writer':
- Add component \WriterMetadataStore
* Writer 'Performance Counters Writer':
- Add component \PerformanceCounters
* Writer 'Registry Writer':
- Add component \Registry
* Writer 'WMI Writer':
- Add component \WMI
* Writer 'COM+ REGDB Writer':
- Add component \COM+ REGDB
Creating shadow set {246471ee-c5a9-4efd-a407-c2ecfe95ff26} ...
- Adding volume \\?\Volume{d58171e8-41d4-11e1-82f5-806e6f6e6963}\ [C:\] to the shadow set...
- Adding volume \\?\Volume{3abd5323-54d9-11e1-9992-2c27d7e6c591}\ [D:\] to the shadow set...
- Adding volume \\?\Volume{3abd5327-54d9-11e1-9992-2c27d7e6c591}\ [G:\] to the shadow set...
Preparing for backup ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Creating the shadow (DoSnapshotSet) ...
(Waiting for the asynchronous operation to finish...)
Error during the last asynchronous operation.
- Returned HRESULT = 0x8004230f
- Error text: VSS_E_UNEXPECTED_PROVIDER_ERROR
- Please re-run VSHADOW.EXE with the /tracing option to get more details
- Backup failed. Mark all writers as not succesfully backed up...
Completing the backup (BackupComplete) ...

ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed.
- Returned HRESULT = 0x80042301
- Error text: VSS_E_BAD_STATE

BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:04:56 AM

Posted 05 March 2012 - 03:58 PM

Have you ran any hard drive diagnostics on the external drive?

#3 Expert Novice

Expert Novice
  • Topic Starter

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Local time:12:56 AM

Posted 05 March 2012 - 04:54 PM

Hmmm, no. Such as Check Disc?

#4 Expert Novice

Expert Novice
  • Topic Starter

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Local time:12:56 AM

Posted 05 March 2012 - 07:47 PM

Ok, I ran chkdsk which said it moved/repaired some files. I ran it again and it did not report any errors.
I have also downloaded and run Seagate Seatool which I ran in Basic and Short Generic mode. Both returned no errors. I was going to run the Advanced and Long Generic modes but there was a warning about the possibility of losing some data. I wanted to avoid that.

After these tests I tried again to run Reflect and got the same error.

#5 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:56 PM

Posted 05 March 2012 - 10:33 PM

Hi

I'm pretty sure that those particular drives have a special controller board in the external case that does some fancy emulation/conversion on the fly to make 512 look like 4096. Not sure how to change that without installing it internally and making the largest partition less than 2TB. Not even sure that would work with it.

At any rate, I believe the problem is with the external controller board more than with the drive itself. Maybe seagate has some info on this aspect of it that can help you.

James

#6 Expert Novice

Expert Novice
  • Topic Starter

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Local time:12:56 AM

Posted 06 March 2012 - 06:13 AM

Hi James, thanks for that. The strange thing is that it has been working so that seems to suggest something else. If it's 4096 now that's what it was when the back ups were woking, even though Seagates site says it shouldn't have.

Edited typo

Edited by Expert Novice, 06 March 2012 - 06:14 AM.


#7 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:56 PM

Posted 06 March 2012 - 11:54 AM

That is weird. Did this particular backup push it over 2TB of storage?

Here is an excellent explanation of what I am talking about...

http://ubuntuforums.org/showpost.php?p=9754234&postcount=7

James

#8 Expert Novice

Expert Novice
  • Topic Starter

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Local time:12:56 AM

Posted 06 March 2012 - 12:00 PM

Not sure if that one would have pushed it over any limit, I forget how much data is on there just now, around 1.5TB I think, mostly music, but there's a lot of old back ups, most of them done with Macrium which I could delete as a test. I'll have a look at the link later, thanks.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users