CloneDisk

FAQ: Ist there a Way, to handle following error with CloneDisk?

 

I have changed the Clustersize on my NTFS Bootpartition, an than on next reboot ...    

 

A disk read error occurred press ctrl+alt+del to restart ...

Edited by @thehop, 22 June 2015 - 10:37 PM.

FAQ: Ist there a Way, to handle following error with CloneDisk?

 

I have changed the Clustersize on my NTFS Bootpartition, an than on next reboot ...    

 

A disk read error occurred press ctrl+alt+del to restart ...

 

how (and why) did you change te cluster size? using what tool?

cannot you just change it back ?

 

if you "only" messed up your partition boot sector, you may be able to edit/fix it.

if you actually messed up the filesystem, then this is beyond my skills...

Just for the record, it greatly depends on EXACTLY WHAT has been done to the NTFS filesystem, on what where the conditions of it before the failed attempt (fully defragmented vs. heavily fragmented) and on what is the actual goal (recover part of the data, recover the whole filesystem, etc.).

If only a few fields (in the bootsector or in the $MFT) have been changed it is usually possible to recover the whole filesystem, but it is hard to say without knowing what was done to that poor, innocent NTFS volume.

 

@thehop

Start a new thread, detailing as much as you can what you have done, follow the Standard Litany, please:

http://homepage.ntlw...ard-litany.html

 

Wonko

HOW: With my old Paragon Partition Manager (5.6) on a 100MB Windows 7 BCD Start Partition (NTFS, no UEFI).

 

WHY: Resizing, Enlarging - and changing the Clustersize 8 kb, to definitely prevent NTFS Compression.

 

STATUS: Fixed with starting Windows 7 Install Prodedure/Break off - does on Reboot

a CHKDISK - and maybe a Fixboot to startoffset? http://thestarman.pcministry.com/asm/mbr/PartTables.htm

 

NEXT TIME: I use CloneDisk to backup the MBR/PBR before  ...

 

thank You guys

Edited by @thehop, 23 June 2015 - 01:37 PM.

CloneDisk updated to 2.3.3.

Lots of work around the partition editor.

 

Changelog below.

2.3.x
changed : use IOCTL_DISK_GET_PARTITION_INFO_EX to retrieve part size when backuping/restoring/cloning
changed : common code for prep source and prep dest when backuping/restoring
added : vdh informations
modified : copyfile uses xcopy only if psexec not in the folder
added : get boot sector work with \\.\PhysicalDrivex syntax
added : reach boot sector from partition table
modified : get_bs and set_bs now get an offset optional parameter (to possibly skip asking the user)
modified : can create more than one gpt partition
added : can modify a gpt partition type
added : can modify a gpt partition attributes
added : can create a virtual disk (raw) in mb/kb/byes
fixed : taborder in mbr and bs form
fixed : config called later in formcreate
added: enable_advanced=1 option in config
fixed : _restore_bs to work with \\.\PhysicalDrivex syntax
added : lock & dismount volume(s) when writing BS to physicaldrive
todo : prep drive before cloning
modified : getdrive works will all medias
modified : _get_infos will not crash on GetDriveLayoutEX (x32)
modified : increased getdrivelayoutex buffer size (x32)
added : extra partition types in part editor (x32)
modified : grayed out menus based on gpt/mbr in part editor (x32)
modified : check on total size in wipe (x32)
modified : change backup_drive signature (mode parameter removed) (x32)
modified : backup_drive signature now accepts offset parameter (x32)
modified : restore_drive signature now accepts size & offset parameters (x32)
added : can backup/restore from part editor (x32)
added : disks in gray in main window (x32)
modified : disks and parts are displayed by default (x32)

 

Life happens and I've been away from this forum for a while now. Just wanted to post and say thanks erwan.l for continuing to support and develop CloneDisk, when so many of the other utils and programs I've used or use from this site have withered, with support/development canned. 

 

...... well after having a closer look at v2.3.3 with the additional .vhd and .iso virtual image options I'm just blown away!    

 

Any chance in your next version of a 'detatch ISO' or 'detatch VHD/ISO' option - from what I can see, having to exit to detach isn't the best but workable. 

...... well after having a closer look at v2.3.3 with the additional .vhd and .iso virtual image options I'm just blown away!    

 

Any chance in your next version of a 'detatch ISO' or 'detatch VHD/ISO' option - from what I can see, having to exit to detach isn't the best but workable. 

 

Hi Captain-midnight,

There is a detach vhd option already.

And it should work for iso as well (provided you mounted it with CloneDisk).

Regards,

Erwan

Life happens and I've been away from this forum for a while now. Just wanted to post and say thanks erwan.l for continuing to support and develop CloneDisk, when so many of the other utils and programs I've used or use from this site have withered, with support/development canned. 

 

 

Thanks for the kind words.

hi erwan.l,

I have made a clonedisk image of a single partitioned, USB HDD and I want to learn how to restore that onto a different partition.

do I need to restore it back to USB HDD and then save a partition image from that or can I use the disk image to restore a partition?

I have not yet restored partition only images. I want to put W7 on a third primary partition that has two empty partitions ahead of it and make it bootable from there by itself.

can you provide some tips for this?

thanks

CloneDisk updated to 2.3.3.

Lots of work around the partition editor.

 

 

Hi Erwan,

 

could you please tell me where to find the new version. It looks like the download on reboot.pro is not up-to-date and I think

http://erwan.labalec...k/clonedisk.zip

and

http://erwan.labalec...lonediskX64.zip

are still the previous version.

 

Many Greetings

MichaelZ

Hi Erwan,

 

could you please tell me where to find the new version. It looks like the download on reboot.pro is not up-to-date and I think

http://erwan.labalec...k/clonedisk.zip

and

http://erwan.labalec...lonediskX64.zip

are still the previous version.

 

Many Greetings

MichaelZ

 

Hi MichaelZ,

 

I host files on my domain (labalec.fr) and backup them up on my dropbox.

On reboot.pro, you'll find pointers to these 2 urls.

 

Zip files on my domain and dropbox are always the latest version.

 

I also maintain the changelog on reboot.pro along with the "versioning".

 

Current is 2.3.3.

 

Regards,

Erwan

I also maintain the changelog on reboot.pro along with the "versioning".

 

Current is 2.3.3.

... though you are too lazy to do it "properly"  

http://reboot.pro/to...-19#entry187929

 

Wonko

hi erwan.l,

I have made a clonedisk image of a single partitioned, USB HDD and I want to learn how to restore that onto a different partition.

do I need to restore it back to USB HDD and then save a partition image from that or can I use the disk image to restore a partition?

thanks

hi erwan.l,

I restored the image to disk then backed it up as a partition image (7gb size) then restored that image to a 10gb partition.

now diskmanager still shows the partition as 10gb but when I right click the partition and then click on properties, it indicates 7gb total size.

is this to be expected? seems odd that 3gb has somehow gone missing with no indication of unallocated space anywhere.

thanks

hi erwan.l,

I restored the image to disk then backed it up as a partition image (7gb size) then restored that image to a 10gb partition.

now diskmanager still shows the partition as 10gb but when I right click the partition and then click on properties, it indicates 7gb total size.

is this to be expected? seems odd that 3gb has somehow gone missing with no indication of unallocated space anywhere.

thanks

 

Just to be sure I get it right :

-you restored a DISK image to disk (please provide source and dest size)

-then backuped one partition image (7gb)

-then restored it to another partition which was 10gb before but 7gb after

 

At first look it sounds Ok to me.

-your disk MBR probably mentions a 10gb partition (disk manager may be using that info)

-but your partition BS mentions 7gb (windows uses that information for volumes)

 

You would need to adapt your MBR I would say?

Well, Zoso seemingly imaged a volume (filesystem) of 7 Gb which was "normally" inside a corresponding 7 Gb partition space and when he restored the 7 Gb volume (filesystem) inside a 10 Gb partition space it curiously remained exactly 7 Gb as the original.

 

I would say that it is largely expected, as no volume (filesystem) was resized in the procedure and of course the filesystem indexing structures remained unchanged.

 

The difference between 10 Gb (size of "outer" container) and 7 Gb (size of the "inner" container) is actually "unallocated space".

 

This is exactly the same as the backup bootsector of NTFS volume which is outside the volume but inside the partition, the difference is only between 512 bytes and 3 Gb.

Just in case:

http://www.forensicf...ewtopic/t=9374/

http://www.forensicf...560295/#6560295

That would be:

http://www.forensicf...r=asc/start=42/

Type #3, "partition slack".

 

See also (as a reference):

http://reboot.pro/to...ated-with-dsfo/

 

 

You would need to adapt your MBR I would say?

...reducing the indexed size for the partition to 7 Gb or resize (enlarge) the volume (filesystem) to use all the 10 Gb indexed in the MBR.

 

Wonko

 

 

...reducing the indexed size for the partition to 7 Gb or resize (enlarge) the volume (filesystem) to use all the 10 Gb indexed in the MBR.

 

Wonko

 

So using the windows extend feature on the volume (in disk manager on in clonedisk) would be enough?

Just to be sure I get it right :
-you restored a DISK image to disk (please provide source and dest size)
-then backuped one partition image (7gb)
-then restored it to another partition which was 10gb before but 7gb after

At first look it sounds Ok to me.
-your disk MBR probably mentions a 10gb partition (disk manager may be using that info)
-but your partition BS mentions 7gb (windows uses that information for volumes)

You would need to adapt your MBR I would say?

yes, restored a DISK image to a disk. the source image was taken from a 37gb USBHDD that had a single primary partition of 7gb containing W7 an the rest was unallocated space. the skip unused space option was selected upon backup. the target was the same USBHDD so it restored perfectly as expected.

yes, then I backed this newly restored USBHDD 7gb single primary ntfs partition with clonedisk save partition image feature.

yes, then I restored it to a 10gb partition but it was a logical on a different USBHDD.

ok, need to adapt MBR after this procedure, I did not know that but what if the partitions are the same size? instead of restoring a 7gb partition onto a 10gb partition space, restoring a 7gb onto a 7gb partitions space? they may not be exactly the same geometry so would it be best to adjust MBR or in some cases the EPBR, right?

So using the windows extend feature on the volume (in disk manager on in clonedisk) would be enough?

well, in this case disk manager sees it as 10gb so no option to resize there it is only when you right click the partition that disk manager is showing and then select "properties" that it then indicates 7gb instead of 10gb.

Ive cleared all that now so I can not go back to test clonedisk resize feature on the exact same situation. I can try to recreate it if needed.

thanks

So using the windows extend feature on the volume (in disk manager on in clonedisk) would be enough?

Yep.

Though it is doubtful that it will work (it needs to be tested).

The whole point is - as mentioned in the given post http://www.forensicf...560295/#6560295- is that MS/Windows and related tools "links" partition info with volume info, i.e. AFAIK/AFAICR the Windows 7 "extend volume" feature expects to find an "unpartitioned" area and extends the partition to include that, and then resizes the volume (filesystem) to the whole space of the partition (minus one sector for the backup bootsector if NTFS).

It is as well possible that it detects the unindexed space inside the partition but outside the volume, of course but it would be an "anomaly" given how partitions and volumes are normally treated in Windows.

 

In Clonedisk you could implement (if it is not actually there already) something *like* I am using the 10 Gb/7 Gb by Zoso as an example:

1) snapshot/save the extents of the 10 Gb partition

2) overwrite the MBR or EPBR partition table with the extents of the 7 Gb volume (taken from the volume BPB + 1 sector)

3) reboot (or refresh the disk manager view/detected devices, depending on the OS this might need to unmount/remount the volume(s) on the device)

4) use the disk manager or diskpart capabilities to "extend" the partition and volume to the same 10 Gb size it was before

5) it has to be seen how much "granularity" you have in the built-in tools (i.e. if you have sector-wise precision) though of course if both the "7 Gb" and the "10 Gb" have been created by the same Windows 7 through disk manager this is probably not a problem but when "mixing OS" (different alignment) and or using other tools which allow "custom" sizes/alignments you may risk to create some remaining "gap" between the "enlarged to 10 Gb (roughly)  partition and the subsequent one.

 

Almost completely unrelated (but not that much after all ) and just to show off a little bit, check how I managed to work around  the issue of 512/4Kb sectored devices:

http://www.msfn.org/...ent-interfaces/

http://www.msfn.org/...ent-interfaces/

at the time if I recall correctly one of the most annoying issues were the differences in the way the diskpart behaved when attempting to "refresh" the mounting, cannot say how Windows 7 behaves, but seemingly there are some differences between XP and Windows 8/8.1.

 

Wonko

 

P.S. Attaching the same graphic as in:

http://www.msfn.org/...aces/?p=1095185

that should help in understanding the difference between partition space and actual volumes inside it.

off topic or not.. Ive noticed that with Aomei and easus that when creating new logical partitions they do not include the unallocated space at the end of the disk into the extended partition like diskmanager does.

this also seems to be a problem for the enhanced write filter in 7 embeded but I havnt been able to narrow it down to exactly that just yet however, ewf works upon fresh install of 7 embedded if the unallocated space is within the extended partition and does not work if the unallocated space is outside of it.

the ewf documentation does mention that it needs unallocated space at the end of the drive but not that it must be inside the extended partition.

just thought I would mention it, not sure if it is helpful or not but just in case it is I post it.

off topic or not.. Ive noticed that with Aomei and easus that when creating new logical partitions they do not include the unallocated space at the end of the disk into the extended partition like diskmanager does.

Which "unallocated space"?

 

In disk manager you first create a (huge) Extended Partition and later you fill that space with one (or more) logical volumes.

 

If you are using more than one single logical volume (i.e. the first logical volume you create ("on the left")  is smaller than the whole extents of the Extended Partition) you have the space ("on the right" of the volume you just created, extending up to the end of the Extended Partition) which is correctly "allocated" (as being part of the Extended Partition) but that is "not allocated" as logical volume (still it belongs to the area "covered" by the Extended Partition).

 

The graphical representation disk manager does is actually accurate.

 

Can you post a screenshot of the various programs on the same disk highlighting the differences in the graphical representation of the disk? 

 

Wonko

I will test that scenario from home : backup partition, restore onto a bigger one.

 

Offtopic too : I shall add a graphical representation in clonedisk at some point (rather than a simple listview).

hi Wonko,

I may have confused the terms "free space" with "unallocated" I think so but I have cleared that layout now also. I will recreate it later and post some snaps of what I am trying to describe so it will be more clear.


edit:
Erwan.l, the main reason I am experimenting with partition images now is that when using clonedisk's "filecopy" feature that I like so much, when using it to move a W7 installation from one partition to another, I get many "Access Denied" errors that I never had with XP.

Ive assumed that is expected behavior with W7 due to increased security measures in the OS but if not, am I doing something incorrectly?

if the file copy worked me with W7 then I could just do that instead of restoring partitions.

about filecopy, 2 things :

-run as admin

-put psexec.exe in the same folder so that the copy process runs with system account

I restored a 500mb partition over a 1000mb partition.

Some windows api's report 1000mb, others report 500mb...

 

After that restore :

-MBR reports 1000mb for part1 (as expected).

-BS reports 500mb for part1 (as expected).

 

Will now try to "fix" the situation.

 

Edit1 : extend fails.

 

Edit2 : I updated the MBR with totalsectors=BS.totalsectors+1 and I could then extend successfully to 1000mb.