My disks are unsupported by Disk Director 11 Home
I have a trial version of Disk Director 11 Home Update 2 (build 11.0.2343) and have found it to be totally useless with my system. No functions are enabled, and all disks are greyed out and marked as Basic GPT (unsupported). The disks are one 256 GB HDD, and two 4TB drives, all SATA3.
I cannot contact support, because the only product listed as registered to me is True Image Home 2014, which I do not actually have, and I can get nowhere. So, I hope somebody here might be able to explain why my disks are unsupported.
Anhang | Größe |
---|---|
disk_director_11_errors.jpg | 235.53 KB |

- Anmelden, um Kommentare verfassen zu können

King.peter2,
Have you tried reinstalling the trial version, also have you entered the trial serial number?
@both posters.
Could you both outline exactly how your drives are setup?
Are they really GPT basic types?
Are they hybrid drives?
Are they SSD or eMMC type drives?
If you make a recovery CD, can the recovery environment boot and see your drives?
Do you have any disk manufacturers utilities installed?
If you have an external USB hub attached or a card reader, what happens if you disconnec them?
Are your machines a brand name model or one made by yourselves or a computer shop?
- Anmelden, um Kommentare verfassen zu können

I also have an "UNSUPPORTED" drive, and can't understand why. First, I restored a complete SSD with Win 10 installation on it. The restoration went fine, and the new disk was placed in a separate partition of a 2TB drive. The partition size is 746 GB and the size of the restored drive was 476GB (~130GB are used). Due to the size of the restored drive I had to reduce the drive partition down in order to get it to my new SSD drive. All went fine until I went to Acronis DD 2012 (I upgraded to that one today) and selected move partition [to the new drive]. There DD 2012 reported back that the operation failed (after quite a wait) and identified the need to run a check-disk on the drive. I did that but when I added the attribute to remove "readonly", and ran check-disk with the /r/v commands, Win 10 reported that it had made the changes to the drive and there were no errors. I set the attribute back to "readonly" booted back into Acronis DD 2012 and now it shows that the drive is unsupported. Had the new drive been big enough to take the whole image, it would have been no problem, but it is a 447GB drive. Anyway, I'm between a rock and a hard place and have lost a couple of days and nights trying to get back to square one. Acronis **might** be the solution, but I cannot tell. BTW, the reason for the drive being "unsupported" is totally unclear. Both the restored drive and the target drive are set to GPT and are basic (not dynamic), both show as local disk, NTFS file system, and are partitioned. When the move process started, I noted that since the size on the disk of the source drive (the restored drive) was ~140GB. So when the corrupt data information was flagged and the operation failed, I took the opportunity to change the partition down from 476 to 304. I used Acronis to change the partition size, which it did without a problem. I also changed the partition size on the target drive to give unallocated space of 232GB, which is more than enough for Acronis to do it's job IF the "UNSUPPORTED" issue can be resolved. Suggestions are welcome.
- Anmelden, um Kommentare verfassen zu können

Richard,
Are you running DD12 from wihtin Windows or from bootable media?
Is the new drive going to be your OS drive or a data only drive?
- Anmelden, um Kommentare verfassen zu können

Hello Colin, I ran DD12 from bootable media, since at that time, I had no 64 bit OS. What I had intended to do was to recover that C drive backup and use it as the baseline for Win 10 installation, so the answer is OS, not just a data drive - thankfully no data has been lost in this fiasco, but the upgrade has been a nightmare. For anyone reading this if you are upgrading to Win 10 and get stuck at the 99% point, google that and you'll find the solution - it is not forthcoming from anyone with whom I spoke at MS - all they wanted to do was restart the laborious process, although I must say they were friendly on the chat-line.
Thanks for your reply, Colin!
Dick
- Anmelden, um Kommentare verfassen zu können

Hello Richard,
First of all I recommend you checking if the disk itself reports to be in good state, even if it is a new one. You can use a free CrystalDiskInfo tool for that: blue color would mean that the disk reports to be healthy, yellow and red would indicate problems at hardware level.
Assuming the reported status will be "good", I suggest you to migrate your system by using backup-restore method with Acronis True Image 2017. A trial version would suffice. Save the image of the entire disk or individual partitions you want to move into a .tib file on an external location like USB HDD or a network folder. Then use "Recover disks" option which would basically copy/unpack/deploy your system onto the disk of your choice (the new disk). A general advice when recovering system onto a new disk is to use "Add disk" feature from Tools - Other (in Windows version) or Tools (bootable media version) to re-initialize the disk and make sure it is cleaned before the restoration. Do not create any partitions manually before doing the recovery.
If you will have any questions abot the system migration process with Acronis True Image, we would be happy to help and guide you: please enter our live chat from http://www.acronis.com/support/contact-us.html
As for why Acronis Disk Director 12 marks the partitions as "unsupported" - that also requires an investigation, collection and analysis of a system report, we would be glad to do that as well, of course.
Regards,
Slava
- Anmelden, um Kommentare verfassen zu können

Hello Slava,
Thank you for your message. First it prompted me to look at the drive again, and I had simply put it aside with other priorities taking precedence as the prior look at it was totally strange - I could not get into the drive at all, and only saw directory names preceded by a letter and a string of '---'. So I am now running Win 10 and I did download that CrystalDiskInfo, but could not even see the drive come up. I had first put that SSD into a USB 3.0 external drive box for SAT drives (this worked previously and all was visiible). Since I still could see nothing, I put it back into an SAT III position, where nothing is yet visible. The drive is a Crucial MX100 SSD - 512GB. I am wondering if there can be some issues releated to the Master File Table, but I may never know at this point. I do appreciate your pointing me to the CrystalDiskInfo, as it flagged 2 drives [yellow] with "Uncorrectable Sector count", despite being reported by DiskPart as healthy. I am wondering a bit about the true ability of motherboards to deal with the legacy MBR and newer GPT. My MB's bios is set to accept both, and apparently does read both, but when my 4TB drive arrives on Saturday, it is my intention to back up the all MBRs convert them to GPT and stay with that format, since I have several big drives on the system. I use Acronis True Image 2015, and while the 2017 version may have some advantages, I believe it can do the job - hopefully those Uncorrectable Sector count issues will not be show-stoppers! Anyway, thanks for your help, and any further suggestions are most welcome!
Best regards,
Richard Holliday
- Anmelden, um Kommentare verfassen zu können

Back again with an update. After preparing to shut down for the night, I stuck that drive back in the USB 3.0 drive and it came up! Anyway CrystalDiskInfo reported the drive 99% Good. I ran DiskPart and it reports it healthy - 2 partitions, and with the MBR type. I'm not sure how it got to this point, but it seems like sitting with power on it for a while brought it around. In any case, I will proceed with the plan noted above when that 4TB drive arrives and see if that helps. I am really puzzled as to why this drive shows up one day and not the next. Again, I am hoping that I don't run into a show-stopper when I try the backup and restore. I don't think the cloning process will work, as there is apparently some issue not yet uncovered!
Best,
RH
- Anmelden, um Kommentare verfassen zu können