PDA

View Full Version : TI V9: unable to use image file on other active partition drive in same PC


videobruce
March 13th, 2008, 10:20 AM
I created a image file of the active partition of my slave HDD (as the way the bios reconizes it). I want to use it on my master bootable drive in the same PC.
When I did, all I get is a Windows dialog box hanging at "Logging off" at boot up.
I then tried a fresh install of just the O/S on that same drive. I imaged that and restored it on the other drive. That worked.

I can restore the image only to the drive/partition where it came from.

I'm figuring it is a issue with drive letters and/or renaming the drives (names, not letters) within windows since with the fresh install, I did nothing as opposed to renaming the two active drives before.

This MB allows changing the boot order within the Bios. Something I only use to do w/ jumpers on the drives themselves. These are IDE drives.
Is this a problem, as V9 seems not to reconize the correct drive letters; C becomes D and vice-a-versa.

XP Pro, two bootable drives, both partitioned twice (four drive letters total) 1st partition active. This was done w/ the bootable CD.

Hope that made sense.

jmk94903
March 13th, 2008, 09:34 PM
-{ Quote: "I created a image file of the active partition of my slave HDD (as the way the bios reconizes it). I want to use it on my master bootable drive in the same PC.
When I did, all I get is a Windows dialog box hanging at "Logging off" at boot up.
I then tried a fresh install of just the O/S on that same drive. I imaged that and restored it on the other drive. That worked.

I can restore the image only to the drive/partition where it came from.

I'm figuring it is a issue with drive letters and/or renaming the drives (names, not letters) within windows since with the fresh install, I did nothing as opposed to renaming the two active drives before.

This MB allows changing the boot order within the Bios. Something I only use to do w/ jumpers on the drives themselves. These are IDE drives.
Is this a problem, as V9 seems not to reconize the correct drive letters; C becomes D and vice-a-versa.

XP Pro, two bootable drives, both partitioned twice (four drive letters total) 1st partition active. This was done w/ the bootable CD.

Hope that made sense." }-Have you created a bootable TrueImage Recovery CD?

Can you boot from that CD and see the four partitions on the two internal drves?

Give each partition a name so that you can unambiguously identify each partition even if the Linux environment enumerates them differently.

videobruce
March 16th, 2008, 12:36 PM
I'm using the program from a CD.

Yes, but the drive letters are wrong. C is D and D is C. This seems to be a problem. See attachments. The 1st is what TI shows. I'm booting to what TI calls "D". The 2nd is what it should be as shown under 'My Computer'

I have which is the only way I know what is what. "Linux"???

So the question is; If I image what TI calls "D" (actually "C" in Windows), isn't that a problem when I restore it to another active partition either here or my other box??

jmk94903
March 16th, 2008, 04:40 PM
-{ Quote: "I'm using the program from a CD." }-Yes, you said that and I missed it.
-{ Quote: "Yes, but the drive letters are wrong. C is D and D is C. This seems to be a problem. See attachments. The 1st is what TI shows. I'm booting to what TI calls "D". The 2nd is what it should be as shown under 'My Computer'" }-The Recovery CD boots to a Linux operating system. Linux doesn't always enumerate the drives the same as Windows. Your system is an example of that. It's not a problem as long as you name the drive partitions and backup and restore the partitions by name rather than by letter.

Linux is calling the primary/active partition on the Master drive C, then the primary partition on the Slave drive D. It then goes back to the first drive and assigns letters to all the other partitions on that drive (E only) and finally gives letters to all the other partitions on the second drive (F only). That's how DOS also would enumerate the partitions. In Windows, you can select the letters after C, so you get a different order.

If you boot from the Recovery CD make an image of what TI calls D: Backup1 which is actually your boot partition, can you restore it to what TI calls C: Main1? Is that what you are trying to do?

videobruce
March 17th, 2008, 09:34 AM
-{ Quote: "If you boot from the Recovery CD make an image of what TI calls D: Backup1 which is actually your boot partition, can you restore it to what TI calls C: Main1? Is that what you are trying to do?" }- Yes. I was concerned about the use of the wrong drive letter, if it would be a problem with the registry etc. after it was restored.

Since this example is more complicated that most (two HDDs' and four partitions, two being active), both of my boxes are the same MB. I wanted to make a 'master' image with everything less the video driver (different cards, but same chipsets) so I can use that for all four active partitions. There is some coruption going on somewhere, either with drive letters, shortcuts, registry entries since even tho both boxes are similar. One box has two SATA drives and two optical drives (one SATA and the other IDE) and the other has two IDE drives and one optical SATA drive. Both boxes have media card readers (four more drive letters to deal with as you can see).

What I am doing is to build up this image w/o the other drive connected. I don't know if that will solve the problems. When I used a image file from the slave drive onto the other box, all I got was a dialog box saying "Logging off".

videobruce
March 17th, 2008, 09:50 AM
Separate questions;

That red flag associated w/ C & D partitions, can I assume that means the partition is active?

If I add the collumn 'Mount Points' (I believe that is what it is called) I get either question marks and or exclaimation points afte the drive letter. What's up with that?

jmk94903
March 18th, 2008, 01:31 AM
-{ Quote: "Yes. I was concerned about the use of the wrong drive letter, if it would be a problem with the registry etc. after it was restored." }-OK, then TI does what it is supposed to do. It restores to the same PC on the same or different drives.
-{ Quote: "Since this example is more complicated that most (two HDDs' and four partitions, two being active), both of my boxes are the same MB. I wanted to make a 'master' image with everything less the video driver (different cards, but same chipsets) so I can use that for all four active partitions. There is some coruption going on somewhere, either with drive letters, shortcuts, registry entries since even tho both boxes are similar. One box has two SATA drives and two optical drives (one SATA and the other IDE) and the other has two IDE drives and one optical SATA drive. Both boxes have media card readers (four more drive letters to deal with as you can see)." }-These systems are not really identical. The mobo is the same, but that's about it. The drives differ, so the installed drivers will be different and that's a bigger problem than the video difference. For video, you could switch to the basic VGA driver on each machine before making the image. That would restore normally regardless of the video card. In a separate step, you would have to install the video driver for the card not in the macine backed up. However, if the hard drive isn't supported, things get messier.
-{ Quote: "What I am doing is to build up this image w/o the other drive connected. I don't know if that will solve the problems. When I used a image file from the slave drive onto the other box, all I got was a dialog box saying "Logging off."" }-I think you need to backup each system separately rather than trying to create a single backup for both systems.

Alternatively, you could make the systems essentially hardware identical first with the same type of drives and video card.