Error (code) 500(0x101f4): ATI-11 & 11.8101 when creating Secure Zone
After 2 days of concerted effort, I am not able to create a Secure Zone on HDD0, or Icy Dock external drive; using either the original ATI-11 Home or the latest update, Build 8101, without the error message: "Failed to write data on disk; to Sector xxx (numerous sectors). The error code is 500(0x101f4). XP disk manager sees the SZ structure once it is created, but I can't build an image in the safe zone.
I am not comfortable in attempting to backup to a hard disk with errors. Several of my prior images and backups were corrupt.
My system is XP-Pro (sp3) with current updates. HDD's are WD Raptor 300gb, and WD Caviar 250gb. I am creating SZ's of 50gb minimum, to hold a disk image; and include partial backups. Disks have 3 primary partitions on system and 2 on external drive.
I have attempted several methods including: trying to install software in 'Safe Mode' (won't work); cleaning, defragging, chkdisk, reformatting; cleaning registry with each install of ATI. All attempts have been done on Primary partitions in both NTS and FAT32 formats. The partitions have been created using Norton Partition Magic 8, and XP Disk Management.
A forum search doesn't bring up this error.
Is there a solution?
Thanks,
Bruce
Hi, Colin,
I just finished doing chkdsk, full repair, for the intended volume--internal, OS HDD--via Windows so don't have a log. Attempting to create the SZ volume failed per the above error, as before, using my original ATI-11 program. It was in an NT file system.
The HDD was partitioned a couple years ago. As a clean (new) drive, it was probably done through XP, but subsequent resizing adjustments were done through Partition Magic.
As a clarification, all active utility programs (AV, firewall, anti-malware) were disabled during the last few SZ creations.
Also, the existing files are quite compact (graphically, if like the old defragger) in the target volume.
This issue has me stumped. Any help is surely appreciated.
Bruce
Bruce,
You mention that you did the chkdsk via Windows, the Windows based full repair isn't quite the same as the Windows boot time /r version.
If you open a command box in XP (start button\run\"cmd") and then in the command/DOS box type in chkdsk /r you'll get a message thay chkdsk cannot perform the operation on a mounted drive and would you like to schedule it to run at reboot. Hit the Y key and then the next time you boot the system checkdisk will run before Windows files get loaded.
To make sure you get as much of the drive as possible, remove the SZ partition from within TI 11, then run chkdsk, a sector error might actually be where the SZ is and Windows won't go there because as far as it's concerned the partition doesn't exist for most purposes.
Then remake the SZ, but don't activate the ASRM, and see what happens.
Colin,
The SZ was created after chkdisk. I know most 'old-hats' prefer command line work, but I am not savvy enough in the "new" MSDOS (7?)--or DOS6--to find (know) the partition in which the SZ is to be built. The other partitions aren't simple D:, and E:; or, E, F. They are H, and I; and could be anything else in a base record. Checking C: drive (the default) is only time consuming.
I'll do some DOS7 research, but am thinking if TI is this sensitive, it may not be practical for a recovery after catastrophic drive C: damage.
One question would be to forget SZ. But if bad sectors or index are the issue, an image my not be any good.
Bruce
Bruce,
You don't have to hunt for the SZ, and you wouldn't find it on a 'normal' search anyway as it is a hidden partition.
Use TI 11 Secure Zone Manager to delete the zone and chose to add the space back to your C: partition.
Then open the Windows command box and just simply type in at the cursor chkdsk /r and press the enter button, Windows does the rest.
It is better to have your images live on another drive internal or external, the problem with the SZ is that as you've noted, if the drive gets a major fault, you've also lost your images as well. The SZ was originaly designed for PC's/laptops that can only ever have one internal drive fitted.
Bad sectors won't neccessarily carry over to the image, but certainly could as could the image itself become affected by bad clusters/sectors.
Do you have a second drive just to test that imaging itself works.
As an aside with TI 2009 and 2010 the SZ can be on a different drive to the main one.