Solved Image your system with free Macrium

[xxxdannyxxx]

The second snip is the difference.See how you have the HBCD menu.exe file this is whats missing when I do it very strange

 

[kado897]

As I added to my post I might have initially created it with 0.0.2.4 maybe that's the difference.

 

[xxxdannyxxx]

As I added to my post I might have initially created it with 0.0.2.4 maybe that's the difference.

I think it must be as your whole usb is set out slightly different.Ive got a copy of 0.0.2.5 here im going to have a try with that.

No joy with that version doesn't include the HDCD menu again



Did you just add the ISO through the Yumi program or did you make alterations to the menu

 

[mjf]

I'm not sure what stage you are struggling with. I decided to stick with the grub4dos loader which predated the YUMI release.
Once you select the mini XP option in Hirens you get

 

[xxxdannyxxx]

Hello Mjf

Yes I've got it working fine in Grub4Dos just would have preferred it on my Yumi multiboot usb but in my case its not adding the files correctly.Thanks though.
Anyway I feel as though I've Hijacked this thread.
My Macrium works great and have a few recovery options so thats brill.

Danny

 

[mjf]

Danny,
I don't think you've hijacked the thread at all. It's relevant to the topic.
I'd still like to know the advantages of the YUMI bootloader approach (now that's hijacking).

 

[xxxdannyxxx]

Danny,
I don't think you've hijacked the thread at all. It's relevant to the topic.
I'd still like to know the advantages of the YUMI bootloader approach (now that's hijacking).

Oh ok then lol I will carry on

I don't think there is an advantage with which method you use its just I'm tight and would prefer not to waste a 4gig usb on 500mb of Hirens files when I could use the whole usb with Yumi. That's the only reason really.Just nice to have everything in one place.

Danny

 

[kado897]

Danny,
I don't think you've hijacked the thread at all. It's relevant to the topic.
I'd still like to know the advantages of the YUMI bootloader approach (now that's hijacking).

Oh ok then lol I will carry on

I don't think there is an advantage with which method you use its just I'm tight and would prefer not to waste a 4gig usb on 500mb of Hirens files when I could use the whole usb with Yumi. That's the only reason really.Just nice to have everything in one place.

Danny

 

[mjf]

I don't think there is an advantage with which method you use its just I'm tight and would prefer not to waste a 4gig usb on 500mb of Hirens files when I could use the whole usb with Yumi. That's the only reason really.Just nice to have everything in one place.

Danny

You don't necessarily need YUMI
I have Hirens and all the rest of this on my 4GB. Apart from the folders the ISOs are apps of course.


I'll leave it at that because I am starting to move off the thread topic.

 

[stonebear]

Sorry if this question has been asked before but, I have watched the video here Imaging with Macrium on Vimeo so I do have some idea of what I am doing with Macrium, it seems nice and easy, I just have one question....

I have taken an image of my system drive (I may do a secure erase on my SSD) and I want to be able to restore a completely working OS, just as it is now....I selected "system reserved" as well as "C", so I will be able to boot into it when it is restored.

I seem to remember something about including the MBR when you are doing the restore, I am guessing I say "yes"?

 

[stonebear]

BTW, I have seen the warning...



"The recovery instructions work perfectly well with a "traditional" installation where the bootmgr resides on the C partition. If, however, you have a seperate 100 or 200MB partition where the bootmgr resides (usually a hidden partition), then you must not mark the C partition as active. Rather mark the partition as primary or logical. Else, your restored system will become unbootable.
The same applies to a double booted system where the bootmgr resides on a different partition."


So I know not to mark the "C" partition as active when I restore but I am unsure if I should have selected the "system reserved" or not when I backed up and I am not sure if I selct the "MBR" option or not when I restore.

The video explains what to do when backing up data drives but not system drives and although WHS did make some reference to system drives I am still unsure.

Maybe I should have posted this in the main forum?

 

[kado897]

I'm not sure what the position is on SSD but for a spinner. System Reserved and C: with the mbr restored should do it.

 

[whs]

In your case you must first restore the 100MB active partition and mark that as "active" and then the C partition and that must NOT be active. You have to predefine those partitions after you wiped the SSD. They also have to be aligned. You best do that when you attach the SSD ( e.g.with an enclosure) to another system. You find info how to define and align the partitions in this tutorial.

As far as the MBR goes, it does not hurt to replace it.

 

[stonebear]

In your case you must first restore the 100MB active partition and mark that as "active" and then the C partition and that must NOT be active. You have to predefine those partitions after you wiped the SSD. They also have to be aligned. You best do that when you attach the SSD ( e.g.with an enclosure) to another system. You find info how to define and align the partitions in this tutorial.

As far as the MBR goes, it does not hurt to replace it.

Thanks WHS, I am glad I asked cos it is more complicated than I thought.

Would I have to do all that with Acronis? I still have some time on my 30 day trial so I could take the image now.

 

[stonebear]

I'm not sure what the position is on SSD but for a spinner. System Reserved and C: with the mbr restored should do it.

That is what I was thinking too...

All that because of the stupid 100mb system reserved.

I can do as WHS suggested but I just hope Acronis is simpler.

 

[stonebear]

It seems that with Acronis you can do a disk restore rather than having to do partition restore with Macrium, that would keep the partitions intact.

 

[whs]

I am not really familiar with Acronis. But if you can clone the whole drive, that may be easier. But you still have the problem of size and alignment that you have to address.

 

[stonebear]

I am not really familiar with Acronis. But if you can clone the whole drive, that may be easier. But you still have the problem of size and alignment that you have to address.

Apparently not....?

"On the "Select destination of disk 1" screen, where you correctly chose the unallocated drive, there was another option on that page which you should have checked and that was "Recover Disk Signature."

When you chose what to restore, your choice should have been either checkmarking the Disk Option; or checkmarking all the partitions listed plus checkmarking the MBR/Track 0 option.

Normally, a disk option restore is the most predictable and trustworthy of all the restores--providing the backup includes all partitions on the original disk. You can practice again and see what the summary screen shows and then click Cancel to stop the practice.

Another restore option (but less desirable than a disk option restore) would have been to restore the partitions individually but this would have required two steps. Restoring the two partitions in the first pass and then restoring the mb/track0 ( plus checkmarking "Recover Disk Signature") in a separate pass."


http://forum.acronis.com/forum/15230

 

[stonebear]

Or maybe I will still need to align because it is an SSD...damn.

More tutorials to read, lol.

Thanks for the responses guys.

 

[stonebear]

It is ironic (!) that Windows own imaging can do what I need without the added complications caused by the 100mb system reserved but I can't use Windows own imaging because the 100mb system reserved is too full to allow me to do it!

Catch 22 again! If the 100mb system reserved wasn't so heavily recommended by the installer I would not have wasted the hours I have.


http://www.sevenforums.com/backup-restore/181573-not-enough-room-create-system-image-but-there.html