Invalid drive after resizing the secure zone
I have a second hard drive d: that is partitioned as d:, e:, f:, and secure zone also. I do not have the exact sizes, but I used manage secure zone to reduce the size of the zone. I noticed that the secure zone was greyed out but I went ahead anyway. I dropped the sz from about 6.3gb to 4.4gb and shared the extra with drives e: and f:. Drive e: is fine but drive f: is invalid. I really would appreciate some help. This is my families' digital photos from about 1995 to present. Thanks.

- Se connecter pour poster des commentaires

Can you post a screenshot of what Disk Management shows for the drive?
Also, it may be helpful to see a screenshot of what TI shows for the drive.
Do you have any backups in the SZ? Are they visible to TI? Don't create a new backup, but can TI Validate and otherwise "see" any existing backups in the SZ? Or is the SZ corrupted too?
- Se connecter pour poster des commentaires

I have attached a screen shot of disk management. TI has a problem now I attached a screenshot of the error I get on startup. TI does not access the drive in backup mode and there is a screenshot for that. There is also a screenshot of the TI log of the partition resizing. Thanks for helping.
Fichier attaché | Taille |
---|---|
39996-91240.JPG | 121.95 Ko |
39996-91243.JPG | 128.71 Ko |
39996-91246.JPG | 101.87 Ko |
39996-91249.JPG | 112.31 Ko |
- Se connecter pour poster des commentaires

In many cases, it's best to commit the changes to one partition at a time instead of grouping them into one procedure. I realize that you wouldn't be able to do that with just TI.
I would recommend that you create a sector-by-sector backup of the drive, but you would need a later version of TI (most likely). TI 10 may backup the entire F: partition since it's corrupted. You would probably need to try from the TI CD, though.
You could try running a format recovery program on F: and see if it recovers it. Running a file recovery program could also be tried, though many of those want to scan unallocated space.
Have you tried running chkdsk on F:? If so, what happens?
It's odd that F: would have become corrupted. F: only required a resize from the right side and so the data on it didn't even need to be moved.
- Se connecter pour poster des commentaires