Skip to main content

ATIH2010 failed because Volume1 not found

Thread needs solution

Nearly every time, when I start ATIH2010 Build 7046 the Backup failed because the 'Specify the Place of Volume1'-Message. If I didn't see the Message and the 10 Minutes to specify the File are gone, the Backup is failed.

The Backup Files are on S:\Acronis\@date@_@time@.tib. S: is an USB-HDD.

The Log say only (German log):
---
- Das System kann die angegebene Datei nicht finden
- Spezifizieren Sie den Ort von Volume 1//Klicken Sie auf Durchsuchen um den Ort des Volumes festzulegen, auf Wiederholen für einen erneuten Versuch oder auf Abbrechen
- Vom Anwender abgebrochen.
---

Why did ATIH does not know its own Images?

Greetings pol...

0 Users found this helpful

Hello M. Polinski!

Thank you for joining us on Acronis Forum, we're glad to greet you here!

Unfortunately due to the lack of information it is hard to say what exactly caused the issue, so this situation requires investigation. Could you please obtain the following information?

  1. Acronis Info
  2. Exact sequence of steps performed

After that please kindly contact support directly with the information attached. Keep in mind that should there be any procrastination with the reply, you can always specify us the case number. We will do our best to speed up the process.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you!

> After that please kindly contact support directly with the information attached.

This is one of the problems... I really try to do this...

After Login, I've not very well options:

- Knowledge Base Information on Windows 7 Support in Acronis products

- Knowledge base

- Support forums

and some 'Buy'-Options. I've run the AcronisInfo Utility, but I've no chance to put the Informations to the support. I think the Support possibilitys are a little too restrictive!!!

But back to the problem: I think, the real failure is, that the Destination File are permanently overritten by simply choose the 'edit' option. If I name the File 'S:\Acronis\MyNameOfTheComputer.tib', the next time it's named 'S:\Acronis\MyNameOfTheComputer(1).tib' and so on. A total chaos happens if I use the @date, @time and so on Options. The next time the Destination Filename is a wild mix of '_'s and '(1)'s,'(2)s' and so on. A very BIG!!! Bug is, that if the Destination Drive (USB-HDD) is disconnected while editing the Job: Acronis set the Destination to the System Partition - and the next time, the Job starts it change the Partitions!!! This is REALLY not my will. Test it: Set Destination to a USB-HDD, switch it off (I think a BACKUP-HDD should always be off whenever the Backup is not in use. It should be on another PLACE). After this quit and restart Acronis TIH. Then try to edit the Job and look at the DestinationDirectory/File - exactly this happens. Not very nice, without a c't-rescure-CD I were very unhappy. I think that this modification of the Destination File/Directory is the real problem and I'm very surprised that obviously so less people have pursued their problems to this point.

Greetings   pol...

Pol,

Are these scheduled tasks or manual ones?

What type of task are you running, full disk/partition images, incremental, differential?

If a files is either part of an archive (Full + incremental or differential) then each slice of the archive has the _1,_2 etc added to the file name so that you can choose which slice you want to restore. Where are the '_s's ' coming from?

Could you post a snipshot of what you see?

The drive that the images are stored on have to be running when editing a task, as True Image has to match the task to a drive and make sure that the drive destination is valid. I agree though it would be nice if it were possible to be able to edit a task without having to have the archive drive attached.

M. Polinski,

To avoid unwanted changes, Do NOT edit any scheduled task. If you need to make a change in the task, then create a new task with the new changes and cease to use the old task. Target disk must be attached when task is being created.

As an alternative to your problem, consider using the helper program DriveNotify as listed in my signature link below. This program will prompt you to attach the target disk but will wait until you actually do attach the external before proceeding.