TI 2014 won't create an image of my system partition

CM:

This message usually means that there is a file system error that TI detects. You should be able to fix these by running checkdisk. Go to an elevated command prompt in Windows 7 and enter the following, assuming that your system partition has the drive letter C:

chkdsk c: /f

You'll get a message saying that the disk cannot be locked, would you like to schedule a scan when the PC reboots? Answer Yes, then reboot the PC. After the disk check finishes you can view what it corrected in the Event Log as follows: http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

If chkdsk successfully fixed any filesystem errors then you should be able to create an image.

Normally you would use chkdsk c: /r for a hard disk, which would do what chkdsk c: /f does AND also tries to recover data in bad sectors, but I don't think that would apply to an SSD. If the previous advice doesn't resolve the issue you can try running the disk diagnostics from your SSD manufacturer to see if it detects problems. For example, Intel has a utillity called "Intel SSD Toolbox" that does this for Intel SSDs.

Thanks, I tried all that before I posted. The disk passed every test I threw at it.

What I didn't try, and will now, is to update to a newer build of TI 2014. I made the mistake of believing Check for Updates when it told me that I had the latest version and build 6688 is newer than 6673.

Well, that didn't work!

It's too bad that TI doesn't provide any detail about what it thinks is wrong.

Also, this problem appears to have bee recurring for years and still hasn't been addressed by Acronis.

I'll try to uninstall and reinstall it, assuming I can find a recent version of the Cleaner - assuming there still is such a thing.

I think this will be my last version of TI. I abandoned Acronis' partition manager some years ago and I have had enough of TI's poor interface, the focus on bells and whistles at the expense of core functionality and the essentially non-existent technical support.

You might try a new task--especially if this task is a carryover from a previous install or the SD is a new change for the task.

Tried a new task too. Also tried an uninstall, CClean and reinstall. No change. Same errors.

Most annoying and frustrating. Not inspiring a lot of confidence in this version.

I don't have the answer to your dilemma but it would be of interest to see how the disk appears when viewed via Windows Disk Management graphical view.

How was the SSD created? Clone or restore or factory original install?

As far as I can tell it appears normally, preceded by the hidden Windows partition (attached GIF). It was cloned from a smaller SSD, for which TI 2014 worked. I hadn't tried it on the new SSD until after I moved the System partition up a bit to allow me to enlarge the hidden partition (both with Minitool Partition Wizard) because imaging with TI 2014 wouldn't work because the hidden partition Windows 7 SYSTEM_DRV was too small.

One thing I should check is the system partition alignment. That is the only thing that I can think of at the moment. I am going to check that again. That might be what TI 2014 is "looking for".

Partition Wizard, as I suspected, tells me that these partitons are already aligned. I will check further. Incidentally, TI 2014 isn't complaining about the hidden partition, just the System partition.

OK, after checking, the first two partitions are properly aligned (partition starting offset divisible by 4,096). And the System partiton is a multiple of 4096 in length, so that's not it.

Are we to assume that the 195 GB of unallocated space is for use of the SSD (over provisioning)? What brand SSD?

Do you still have the original System disk so that you could compare the actual size of the new System Partition with the original size of the old system partition?

No, the remainder was just space that I didn't need, at least initially, for the system and I hadn't decided whether I wanted a larger system partition or another partition. I could try extending it but not until I have backed it up. Oh, wait. I can't back it up. That's my dilemma.

Hello,
I am also a TIH2014 user, waiting better results for TIH2015.
I had no trouble backing up a disk (one partition) and restoring to a New SSD using TIH2014.

As a test, once the ssd was running with everything I wanted on the drive, I trashed it and did a recovery from the image...
All was well and everything recovered correctly.
One difference here is that my SSD has only ONE partition (the Win7/64 OS) and the original image was only from a single partition disk.

I did have an issue one time during an attempted restore but did not involve the ssd.
Grover and Mark, pointed me in the right direction with comments about possible disk errors. Seems my image was made from a disk that also had a few sector errors and that totally stopped the recovery process dead in its' tracks. Once the Chkdsk detected the errors and fixed them, a new image was created and a restore tested with no problems. So it appears to me that a unnoticed disk error can go undetected, get included in a disk image and cause a restore failure.

Steve

I too have successfully backed up partitions from an SSD, including a system partition, indeed on the same computer and with the same software that is now causing me trouble. There are also reports of the same problem occurring, for some people, with TI 2015, so I am not hopeful that trying it will fix the problem. I try reverting back to TI 2012 - it seemed the ost stable of the recent crop (2009 to-date, at least for me) but, I don't know ....

There are comments that it is some driver problem and I can see that. Some earlier versions of TI had some significant driver problems for a few of us in the past.

And in my case, TI 2014 won't create the image because of some problem that it sees but that I cannot identify.

Well, I downloaded a trial of TI 2015 and, to my surprise, it started and did not immediately fail.

I had to know that View current state of your disks was buried in Drive Cleanser and this itself was buried but now it doe not show a red X above the drive letter.

So, nothing wrong with my drive or partition. Now we'll see if the image creation completes - it has gone nearly to the end and then terminated - so ...

UPDATE: Yes, it seems that the current build of TI 2015 does not have the same problem. The image backup of my system partition completed without any problems.

Hmm, different interface - isn't too bad but where did the logs go, I wonder. I also don't seem to be given much control over the naming of backups. Oh, well, another "new" interface to get used to. At least it seems to work.

Thanks to all.

Oh, dear. I have doing a bit of reading about TI2015 and it seems that I would prefer a fixed version of TI2014. There seem to be a number of basic features, like log files and backup browsing, either missing or buried. Somehow, I don't think a fixed version of TI 2014 is very likely.