TI 2010 will not work and I'm going crazy
Hello -
I upgraded my system from Vista 64 to Windows 7 64. Clean install.
Installed Acronis TI 2009. Kept hanging on analyzing partition.
Reviews the website and see that apparently Acronis TI 2009 is not supposed to be supported by Windows 7. (Although many, many people seem to run it just fine on Windows 7 64)
Shell out the $30 for an upgrade.
Installed Acronis TI 2010.
Same damn problem.
After a million configurations somehow last night it worked - I though things were peachy and I turned off the computer thinking that I would do a back up and get my files installed the following day. However...
This evening - same thing. The program hangs at analyzing one of the external drives (the one with everything on it).
I'm running Norton Internet Security 2010.
This is killing me. I cannot run Acronis, I cannot back up, I cannot get my files onto my clean install.
What can possibly be the problem?
Please help me.
Did you do an upgrade install over TI 2009? What build of TI (Click the Help drop down in the upper right corner)? If so re-install TI 2010 and select repair install. See GroverH's Index of Accumulated Wisdom http://forum.acronis.com/forum/3426. Search there for "2009" and 2010.
I did a complete new install of TI 2010. I rolled back to a restore point before the TI 2009 install.
The build of TI 2010 is Latest Build: #7046 (114.95 MBApril 1, 2010 ) . I cannot see the help menu because I cannot actually get into TI 2010.
I'd try a repair install. Run the installer again and select repair.
I will try that but I feel like I'm missing something basic here.
The TI 2009 was running fine with this drive on my old Vista 64 installation and Norton Internet Security 2009 (i'm now using 2010) until I added another drive. Then it started to hang.
So I did all this stuff - remove with clean up utility, reinstall, etc.
I thought that I could just get on with my life and get two back ups of my files going but no.
I've contacted LaCie about the second drive but they say that since Windows (Vista/Win7) sees the drive then it's not the drive.
This is really killing me.
I'll post the results in a few.
Nope - didn't do a thing. Hung.
OK - so I turned off the LaCie1, drive where it is hanging (the one that used to work just fine and worked last night the one time it worked and the one that has all of my files on it) and left on LaCie2 (the drive that wouldn't work in Vista). And TI 2010 started up fine.
And then I turned off LaCie2 and on LaCie1 (had to do a reboot as system froze) and now TI 2010 is hanging. However, I can see the drive and all the files in Windows Explorer.
I have tried to copy the files off but they are 110 GB each and the abysmal windows copy/paste problem prevents me from just copying files to the hard drive and starting over. I can copy/paste/delete smaller files no problem.
I don't know that it's the drive because this problem happened with the second drive initially.
The drive LaCie1 is 1TB and is about 1/2 full.
So - TI 2010 will not analyze the drive correctly but I can access the *.tib folders, open and copy my stuff to my hard drive at a MUCH faster rate then the regular Win7 speed. However, this does not answer any questions and I need to be able to have Acronis access 2 external drives on a Win 7 system.
Since you haven't mentioned any of these, I guess it's worth asking:
1) Have you checked the drive properties/policies for the ext. drives? Are they both the same (i.e., write cacheing, etc.)?
2) Assuming ther drives are USB, Have you tried different USB ports?
Have you tried plugging the problem drive into the USB port being used by the drive ATI does see, leaving the 'non-problem drive disconnected?
The same questions could apply to sata, if you're using an external sata port. Not sure about esata, but I would assume so.
3) Is the drive detected via the rescue disk? Under any of the above scenarios?
HI there
1) Yes I've checked the drive properties/policies on the external hds. Ironically, LaCie2 (the one that didn't want to work under Vista but works in win7) is set to Quick Removal. LaCie1 (the original that now is not accessible by Acronis under Win7) was already set to Bette performance with Caching
2) LaCie1 is eSata - there is only one drive - everything worked fine with TI 2009 and Vista 64
LaCie2 - I've tried both USB and the 1394 connector. Two different USB ports
3) Not sure what the rescue disk is - never made an Acronis rescue anything. It is there and functioning under the device management feature of Windows 7.
And again - last night as I was about to throw in the towel - it miraculously worked. And again I thought "oh yay, everything will be fine in the morning" but no. Now all it does is hang and I have to hard reboot my computer to get TI 2010 to quit. It' locks my drive and there is no way to kill the program. End Process does not work.
So SyncbackPro works but the LaCie1 (original) drive disappears after backup (sometimes). LaCie2 does not.
So perhaps it's a combination between Acronis and LaCie - neither of whom seems to want to actually take responsibility (plus a little Windows 7 thrown in there for fun).
Any ideas?
Jennifer. Do build Acronis Bootable media using the built in media builder function. Boot from the cd and see if you get the same behavior. The recovery CD is Linux based. This may shed some more light on the issue. It does sound like to me that the drive itself is the problem and using the bootable media my help narrow that down. You can also download bootable media from your Acronis account. See http://kb.acronis.com/content/1642.
Also download the ISO bootable media file from your account to try as an alternative to the version built via the media builder.
HI there
1) Yes I've checked the drive properties/policies on the external hds. Ironically, LaCie2 (the one that didn't want to work under Vista but works in win7) is set to Quick Removal. LaCie1 (the original that now is not accessible by Acronis under Win7) was already set to Bette performance with Caching
It's not mentioned, so, did you try setting Lacie1 to the same settings as Lacie2 (the drive that works under win7), including Quick Removal?
So the suggestions are to do this bootable media thing - which I'm not exactly sure as to what it really is.
What am I looking for when I do this?
Is this bootable media going to run acronis from a disk instead of from my computer?
From this page http://kb.acronis.com/content/8189 it looks like I have to back up something in order to create bootable media. I'm not sure that I understand the purpose of doing this?
MH - So try to set my policies to the ones not actually recommended by anyone. I guess I can try all variations of these.
I think this is what I'm looking for http://kb.acronis.com/content/4828 and I will try when I get home but I'm still not sure what the point is.
Is it to see if TI 2010 running from a disk recognizes the external drive?
The thing that's killing me (besides the 20 hrs of wasted time) is that this worked perfectly fine on Vista 64 with TI 2009. And it was the other disk that TI 2009 wouldn't recognize.
Also - what about the drive would make it not accessible by TI 2010 when it was accessible by TI 2009?
And it is currently, according to Windows 7, functioning fine. I can see copy/paste/delete files to it through Explorer and Robocopy.
It's just TI 2010 that cannot deal with it.
Is this bootable media going to run Acronis from a disk instead of from my computer?
Yes, that's its purpose. Without it you won't be able to restore your backup images in the event your system is unable to boot. It may also help sort out your drive issues. You need to be sure that the recovery CD can see the drives attached to your computer.
thomas - okey dokey. I'll try this when I get home.
What would I be looking for to clue me into a drive issue?
Even if it can't analyze my drive from the bootable media (and remember, it has seen this drive two times in the last two evenings after about 10 hard reboots each night) how would that make it a drive problem not a TI 2010 drive access problem?
So the suggestions are to do this bootable media thing - which I'm not exactly sure as to what it really is.
What am I looking for when I do this?
Is this bootable media going to run acronis from a disk instead of from my computer?
From this page http://kb.acronis.com/content/8189 it looks like I have to back up something in order to create bootable media. I'm not sure that I understand the purpose of doing this?
No, that is not about building a Rescue Disk. That link shows you how to make a image bootable when writing the image to DVD. A resue disk allows...well, perhaps the best way to help is to direct you to the pdf manual. You can download it here:
http://s4u.download.acronis.com/sl/kPJlynsXtaBWY3UOTBDl037UMoKiyEZ0TGBO…
Page 124, under the bookmark "Creating Bootable Media", sub item "Creating Linux-based rescue media". This will tell you about Rescue Disks and how to build one. The rescue disk allows you to boot from the disk and create or restore images in a Linux based environment. If the rescue disk sees the problem drive, it is additional info that could help pin down the issue. Another benefit is that, if it does recognize the problem drive, you can create images that way until the issue is found. Not as convenient as imaging from within windows, but a workable solution.
[/quote]
MH - So try to set my policies to the ones not actually recommended by anyone.
Yes. IOW, try setting the policies on the problem drive to coincide with those on the working drive. This does not mean that you must keep these settings, but, as mentioned above, the information obtained through such exercises may help track down the issue.
Jennifer,
I think you mentioned one LaCie drive is eSata the other USB, and the eSata is the one playing up?
If the drive also has a USB option, does it then work with TI?
It could be a combination of eSata (which is a bit flaky) , TI 2009/2010 and W7.
Either way as has been mentioned you need to make sure your rescue CD will read all your drives.
So it started like a charm when I changed it from eSata to USB. I had played with connections on the other drive but not this one as it had initially worked fine.
I will try rebooting and see if it starts again no problem.
OK - rebooted and now the computer won't turn on unless that drive is off. What's up with that? How do I have my computer boot normally?
(Oh - and it ran again once I finally got Win7 to start.)
Thanks for all the suggestions so far - it's been very helpful.
So it started like a charm when I changed it from eSata to USB. I had played with connections on the other drive but not this one as it had initially worked fine.
I will try rebooting and see if it starts again no problem.
OK - rebooted and now the computer won't turn on unless that drive is off. What's up with that? How do I have my computer boot normally?
(Oh - and it ran again once I finally got Win7 to start.)
Thanks for all the suggestions so far - it's been very helpful.
The first thing I would check is the boot order in the bios. Is a USB device listed 1st?
MH -
After a few reboots it now does exactly what it should. All this frustration and wasted time over a &*%*$ cable. I thought eSATA was supposed to be the cat's miao.
As for the boot order - the time I checked when it wasn't rebooting there was a USB device listed first. Why, I wonder? I will check on next reboot.
What is supposed to be listed first? My harddrive?
So I think this whole thing is solved - stupid cable. Are there problems with that 1394 cable too? I seem to have a connection for than and have run out of connections on the back of the machine - that's why I liked the eSATA in the first place.
If anything else comes up I'll be back here in a snap!
Thank you everyone.
MH -
After a few reboots it now does exactly what it should. All this frustration and wasted time over a &*%*$ cable. I thought eSATA was supposed to be the cat's miao.
As for the boot order - the time I checked when it wasn't rebooting there was a USB device listed first. Why, I wonder? I will check on next reboot.
What is supposed to be listed first? My harddrive?
Some people list their optical drive 1st, but it increases the boot time a little. I generally have my HD 1st, switching it to the optical only when I need to.
So I think this whole thing is solved - stupid cable. Are there problems with that 1394 cable too? I seem to have a connection for than and have run out of connections on the back of the machine - that's why I liked the eSATA in the first place.
It could have been any number of things. Likely not the cable, given that windows recognized the drive. Cudos to Colin B for nailing it shut.
Thanks to all of you - MH, Colin, and thomasjk.
You're right - I think Colin's comment about the combo of eSATA/Win7/TI 2010 made me feel a lot better - like I wasn't crazy. Whatever's going on it's way beyond my scope of knowledge and I imagine has something to do with how devices are recognized by hardware and software depending on connection type.
PS - I made a boot disk - didn't know how to use it :)
Jennifer said:
PS - I made a boot disk - didn't know how to use it :)
To use the boot disk you will have to set the BIOS on your machine to boot from the CDROM drive. How you do this varies by machine but generally you press one of the function keys i.e F2, F1 or sometimes Delete. When your machine starts you will usually see a prompt to enter Setup by pressing a certain key. Press that key. When you enter the BIOS look for Boot options. Exactly where it is in the menu system varies by the type of BIOS. Once you find it set the CDROM drive to be your first choice for booting instead of the hard drive. Exit BIOS saving your changes and restart the machine with the boot disk in the CDROM drive. You may see a message "Press any key to boot from CD\DVD drive", if so hit any key. The disk should boot and load the Linux version of TI 2010.
Jennifer,
If you have some spare time where you can do some reading, you will find the signature index below very helpful. Particularly, items in #2 as well as #7A, 7D, 7G & 7H. If you are curious about how others use TrueImage, you might also read the items listed in #12.