Trying to Re Image my computer with problems

[whs]

so if i was to remove my raid 0 then install the backup onto one of the drives, then once fully installed and loaded i then install the RAID drivers then i run another Disk backup and then reformat with the newly created backup with RAID 0, would that work??

What on earth are you trying to accomplish with Raid for the OS. As Greg says, it buys you nothing and complicates your life. Keep the OS on a single disk and move the data to an array - that makes sense.

 

[marsmimar]

This had been a very informative and educational thread.

 

[mjf]

If you have a valid windows generated vhd you can restore it and resize using Macrium. See here
http://www.sevenforums.com/performa...ved-image-smaller-hard-drive.html#post1112804
I tried it some time ago as an "experiment" and it seemed to work fine. I was being a bit cautious in my response.

One motivation for playing with this was to also be able to recover a windows image whose vhd file(s) existed but Windows refused to auto locate.

When the OS partition was separate from the system reserved, the Macrium image/reimage works ok on the OS partition. This should be enough to get you back in business but you need to recreate the system reserved partition.
For some reason Macrium will not image a mounted version of the system reserved partition.



Correction: Macrium Reflect V5 appears to have no problems imaging the System Reserved.

 

[whs]

Now if you have a combined (system, active, boot) partition I'm not sure that the process would work.

The Macrium imaging works. I have, however, not tried to restore from that image. So I am not certain whether that would work.

 

[mjf]

Now if you have a combined (system, active, boot) partition I'm not sure that the process would work.

The Macrium imaging works. I have, however, not tried to restore from that image. So I am not certain whether that would work.

I have the latest Macrium version so I still don't understand why the error on the 100MB system reserved partition.

Of course you can take a Macrium image of the ordinary system reserved partition - do it all the time.

 

[whs]

Try to image the 100MB partition with

WBADMIN START BACKUP -backupTarget:x: -include:y:

and see whether that may work.

 

[mjf]

Try to image the 100MB partition with

WBADMIN START BACKUP -backupTarget:x: -include:y:

and see whether that may work.

wbadmin is for windows command line execution of Windows imaging not Macrium imaging.
The problem I describe is with Macrium. Windows allows attaching the 100 MB system reserved vhd. Macrium won't image it. See screenshot in my post #43.

By the way wbadmin still wants the same folder and file structure as seen in [WindowsImageBackup]. It's main advantage as I see it is for writing your own imaging scripts.

 

[SIW2]

Yes, wbadmin is the same thing - most will prefer the windows sys img gui.

Macrium message looks like there isn't enough space on 100mb mounted volume to create volume snapshot -if that's the case , then it is a microsoft VSS issue really.

Haven't checked recently, but Macrium used to have alternate drivers to use when VSS fails - not sure if they do now.

Paragon has alternate drivers for just such a case.

Might sound odd - but also check you have enough shadow storage space on your current drive (C or whatever you are booted into )

Worth checking Macrium log - because it might be something else.

 

[mjf]

Macrium message looks like there isn't enough space on 100mb mounted volume to create volume snapshot -if that's the case , then it is a microsoft VSS issue really.

When the windows imaged 100MB system reserved is mounted it does have an occupancy greater than 50MB. Windows imaging requires the 50MB free shadow copy space for it's imaging.
I do not expect this shadow copy space to be of relevance to making a Macrium image.

PS: I'm not sure at this stage where the extra rubbish comes from in the mounted system reserved. It isn't there in the original.

 

[SIW2]

That seems to indicate - unless you can get macrium own pssnap.sys I think it is - can't recall now - to take over - then you can't image the 100mb thing with macrium.

No biggie - just use a different imaging app. - or don't bother imaging the 100mb - you would only mount vhd and do this in extremis - so it's not an issue if you need to run startup repair a couple of times after restoring the main windows partition as Active.

As you have the macrium pe plugin -you could even try the macrium boot corrector and see if that does the job instead of startup repair.

Most people won't have the macrium pe tho.

ps What is the extra stuff in the 100mb?

 

[gregrocker]

If the System Reserved partition was originally there but not reimaged or for any other reason the image isn't marked Active or include SYstem Boot files, then OP will need to mark it Active, boot the Win7 DVD to run up to 3 separate Startup Repairs with reboots to write or repair the System Boot Files to Win7.

Partition - Mark as Active
or for a picture of what you're doing use Partition Wizard bootable CD
Startup Repair - Run 3 Separate Times