Solved Easeus todo for images?

[whs]

I don't know whather my suggestion will fix the problem. But since you would have less data to image, chances for the error to occur are minimized.

 

[DavidE]

Good point Wolfgang.

Even easier is try creating an image of 1 partition at a time.
The partition is the only partition should take a long time. The other 2 should run real quick. Then at least you'll know which partition is causing the problem without making boot changes.

 

[Scottyboy99]

Yeah I did see that article, not great for confidence. But the seagate diagnostics passed all ok. I am worried about messing with boot manager and whether it will have a negative effect on my being able to use the cache SSD drive software later on.

 

[Scottyboy99]

Here is a pic of disk management with the dataplex software installed thus activating the cache SSD drive. It now becomes invisible to Windows

 

[whs]

With what I suggested you are not 'messing' with the bootmgr, you just make a copy to C.

 

[Scottyboy99]

Ok. thank you. I'll have a crack at it tomorrow evening when back from work. I better hit the hay with early work start tomorrow. I do appreciate your help greatly. Just 1 quick question, is it worth before doing this tomorrow trying to image each partition individually to see if it hangs on anyone of them first?

 

[ThrashZone]

Your recovery partition is the active partition with the bootmgr. That's not good. I suggest you copy the bootmgr to C (see link) and then you image C only. There is no need for the other stuff..

http://www.sevenforums.com/tutorials/209885-bootmgr-move-c-easybcd.html

You never have updated the link to download easybcd mate

 

[DavidE]

Yea, guess i didn't explain clear enough.
My idea was to test creating an image of the small partitions separately, 1 at a time, those should run real quick.
Just to know if there is a problem with imaging either of those partitions.

 

[DavidE]

Just 1 quick question, is it worth before doing this tomorrow trying to image each partition individually to see if it hangs on anyone of them first?

That's what i would do, those backups should run in a matter of minutes, not hours.

I don't have experience with dataplex software or activating the cache SSD drive.

 

[whs]

I fixed the link - and here it is again.

Download EasyBCD - MajorGeeks

 

[Scottyboy99]

Yeah sorry, you did explain that clearly. I will do that tomorrow then. Trying to do too many things at once and getting in a stress over it! A good sleep and will be more methodical again tomorrow evening.

I don't think many know much about dataplex and the cache SSD, the company doesn't exist anymore. But the concept is great and gives near SSD performance across a whole drive. It never gave me much issue before but it has given some people trouble. It hates an unclean shutdown that's for sure and a restriction is never image with it activated. In 4 or 5 years I had to restore image a couple times due to dataplex but it always worked a treat. Just now I cant get a new pesky image done and with the USB HD holding the latest image having gone to silicon heaven I am now nervy.

Cheers to all for your helpfulness. I'll report back soon

Wayne

 

[mjf]

Your recovery partition is the active partition with the bootmgr. That's not good. I suggest you copy the bootmgr to C (see link) and then you image C only. There is no need for the other stuff..

http://www.sevenforums.com/tutorials/209885-bootmgr-move-c-easybcd.html

I don't want to confuse the info you are receiving but I would hold off on this initially. Making the recovery partition the active/boot partition is used by some large OEM suppliers (HP are one I think). I'd have a fallback image before you make that change.

You could try making a test image of your first 2 partitions.

 

[whs]

Your recovery partition is the active partition with the bootmgr. That's not good. I suggest you copy the bootmgr to C (see link) and then you image C only. There is no need for the other stuff..

http://www.sevenforums.com/tutorials/209885-bootmgr-move-c-easybcd.html

I don't want to confuse the info you are receiving but I would hold off on this initially. Making the recovery partition the active/boot partition is used by some large OEM suppliers (HP are one I think). I'd have a fallback image before you make that change.

You could try making a test image of your first 2 partitions.

So what's the problem.

HP uses the recovery partition as the active partition to save on the number of partitions. There is still this bad habit by all manufacturers to make all partitions primaries although only the active partition has to be a primary. And then they quickly run into the 4 primary partition limit - in MBR land.

 

[mjf]

Your recovery partition is the active partition with the bootmgr. That's not good. I suggest you copy the bootmgr to C (see link) and then you image C only. There is no need for the other stuff..

http://www.sevenforums.com/tutorials/209885-bootmgr-move-c-easybcd.html

I don't want to confuse the info you are receiving but I would hold off on this initially. Making the recovery partition the active/boot partition is used by some large OEM suppliers (HP are one I think). I'd have a fallback image before you make that change.

You could try making a test image of your first 2 partitions.

So what's the problem.

HP uses the recovery partition as the active partition to save on the number of partitions. There is still this bad habit by all manufacturers to make all partitions primaries although only the active partition has to be a primary. And then they quickly run into the 4 primary partition limit - in MBR land.

HP (& presumably Alienware) simply have a silly partition model. ACER had a system reserved (active, 100MB), a recovery partition, an OS partition and a user data partition. This conformed to the MS standard at the time. For the record I'm no supporter of ACER.

Getting back to the OP's problem, I think changing the booting structure is just complicating his problem - that's the problem.

 

[whs]

Getting back to the OP's problem, I think changing the booting structure is just complicating his problem - that's the problem.

Sorry Michael, but that is a lot of motherhood. What complications did you have in mind. Let's review them one by one.

 

[mjf]

Of course it's an added complication initially.
1) The changed boot structure could present its own problems that could confuse the issue.
2) same as 1)
...
I've finished my comments with this thread. Not quite.

 

[whs]

Which means you ran out of arguments, LOL.

Listen, I have done that bootmgr copy many times and have never - I repeat never - any problems. I have also recommended it to at least 30 other people and never had any negative feedback.

 

[mjf]

Which means you ran out of arguments, LOL.

Leave it alone you're talking rubbish

 

[Scottyboy99]

Well I'm trying again with macrium now. I did the first tiny partition and that completed its image fine, done in the blink of an eye. Then I did the recovery partition on its own, that completed very quickly. So now onto C: Windows. That's going to take a while, but as the other two imaged fine I think it points to something on c: not being right. But will see how it goes, if all the previous failures and BSOD are anything to go by it will happen around the 96/97% mark which will be in about 2 or 3 hours time. Will report back.

 

[Scottyboy99]

Failed again

Yep, BSOD on C: drive image. Too quick to read what the errors are though. I guess something is badly wrong somewhere. At a loss.