Skip to main content

Family Photos - Resize Disk Created Unformatted Partition - Disk Director 11 Home Update 2

Beginner
Posts: 2
Comments: 0

A couple of days ago I attempted to resize two adjacent volumes on a single physical drive - as I have done many times before - in order to add some capacity to my 'family photo drive'.

 

The first partition was to be made smaller by 10GB in order to 'give' this capacity to the second partition.  There were no obvious errors showing on either partition prior to the re-size attempt.  

 

After rebooting, the message stated that the resize had failed due to "bad blocks".  Here are the three relevant Acronis DD Logs:

 

"Log Entry Details

Type:          Error
Date and time: 10/03/2017 14:04:30
Code:          3,539,345(0x360191)
Module:        54
Owner:         Steve E Crane
Message:       
  Unable to resize partition with bad blocks
Additional info: 
--------------------
Error code: 401
Module: 54
LineInfo: B8927DFC4B593CDC
Message: Failed to execute the command in the environment.
--------------------
Error code: 402
Module: 54
LineInfo: 490DC54208ACB930
Message: Fdisk operation has failed.
--------------------
Error code: 703
Module: 54
LineInfo: 90921B07B1F5C0F9
Message: Corrupted file system.
--------------------
Error code: 12310
Module: 16
LineInfo: 007AFFF41AEF4EAD
Message: Failed to resize the volume.
--------------------
Error code: 1036
Module: 16
LineInfo: C57F4C2FE4F70A6A
Message: Corrupted file system.
--------------------
Error code: 35
Module: 7
LineInfo: 5738609E19DFE50E
Message: Unable to resize partition with bad blocks
--------------------

Acronis Knowledge Base: http://kb.acronis.com/errorcode/

Event code: 0x00360191+0x00360192+0x003602BF+0x00103016+0x0010040C+0x00070023"

 

"Log Entry Details
Type:          Information
Date and time: 10/03/2017 14:04:30
Code:          3,538,944(0x360000)
Module:        54
Owner:         Steve E Crane
Message:       
  Resizing volume
Volume description:
  Disk: 3
  Letter: P
  Label: P_Pictures-Maxtor6B200P0
  Size: 49.96 GB -> 59.96 GB
  File system: NTFS"

 

"Log Entry Details

Type:          Information
Date and time: 10/03/2017 14:04:30
Code:          3,538,944(0x360000)
Module:        54
Owner:         Steve E Crane
Message:       
  Resizing volume
Volume description:
  Disk: 3
  Letter: V
  Label: V_Video-Maxtor6B200P0
  Size: 119.93 GB -> 109.93 GB
  File system: NTFS"

 

I tried to gain 'direct' support for this problem but I could not find Disk Director 11 Home Edition in the drop-down menu provided when I attempted to register my issue, so I've had to resort to community support instead.

 

This drive has 15,000+ family photos on it, from when my daughter was born until present day - consequently it has MASSIVE emotional significance to me and my family and I would dearly like to employ the best techniques, tools and methodologies in order to recover the entire 14-years of content from this drive.

 

P L E A S E   H E L P ! ! !

Forum Star
Posts: 19
Comments: 2110
mvp

Top

Steve:

Here are the steps that I would do to attempt recovery of your valuable data:

1.  DO NOT do anything that involves writing to the disk to avoid causing further problems.
2. Purchase another disk that is as large or larger than your existing disk. An external USB disk would be appropriate.
3. Use TrueImage or Disk Director to clone the existing disk to the new disk. I would recommend using TrueImage for this task. Make a sector-by-sector image of the bad disk and save it to external storage (not to the new disk). This image should capture the exact state of your bad disk.
4. Restore the image exactly as-is (without resizing) in sector-by-sector mode to the new disk.
5. Your new disk should be an exact copy of the bad disk and now you can experiment with different recovery software without risking the original disk. Additionally you also have an image that you can use if multiple attempts at different recovery techniques are needed.
6. Put the bad disk aside and don't touch it until you have successfully recovered your files (hopefully).
7. Find a good disk recovery program like GetDataBack https://www.runtime.org/data-recovery-software.htm or an equivalent.
8. Attempt to recover the disk contents.

If one recovery program doesn't work you can try another by restoring your image to the new disk again and starting over with different recovery software. You can do this as many times as you want, which is the reason that I recommend using TrueImage in step 3.

Once you have (hopefully) recovered your files you can restore them back to the old disk. However, from your log details in your first post, the disk apparently had either bad sectors or just NTFS file corruption that could probably be corrected by reformatting the disk (don't use fast format because it won't correct bad sectors). But if it were me, I would not entrust a valuable photo collection to an older disk, and I would either start keeping multiple copies of the photo collection on different disks or implement a regular backup strategy with TrueImage.

I wish you the best of luck. If all else fails you can try a data recovery service.

Forum Hero
Posts: 35
Comments: 6089
mvp

Top

Are there no backups of these precious files anywhere else? I hate to make things worse for you, but if these are critical files, backups should be taken regularly to give you avenues to recover from. What would you do if the disk just failed on you or the computer caught on fire if there was no backup?