TeraByte Unlimited

Hi - I have a i5 Windows 7 machine that's never given me a day of trouble - But a really weird thing happened last night. I have my backups automated (Perl is a wonderful thing), and last night the full backup backed up the -wrong- hard disk. I opened IFW and tried to redo it, and in the selection menu I saw that the hard disks were numbered differently! The first one is always the system disk, and the last one is always my storage disk - but today they were reversed! So when IFW did a backup using the controller specification, it found the wrong disk. I powered down and restarted this morning, and all was back to the way it should be. I auto-reboot every night before the backup, and somehow after last night's reboot the controller numbering came up different!

Has anyone seen anything like this before? Is it likely to recur? Is there some way to set up IFW to search by drive letter rather than physical controller #?

Thanks!
/j

Was it Visa or 7, Windows started to init drives in parallel to try and
speed boots so drives may end up in a different order. Anyway, you can use
the signature of the drive instead of drive number in your script (using the
#0xAABBCCDD in place of just the number where AABBCCDD is the hex signature
(shown next to the drive in the list in IFW or properties via
details/information) - when using gpt you'd use the {GUID} instead).



"jeffw_00" wrote in message news:[email protected]...

Hi - I have a i5 Windows 7 machine that's never given me a day of trouble -
But a really weird thing happened last night. I have my backups automated
(Perl is a wonderful thing), and last night the full backup backed up
the -wrong- hard disk. I opened IFW and tried to redo it, and in the
selection menu I saw that the hard disks were numbered differently! The
first one is always the system disk, and the last one is always my storage
disk - but today they were reversed! So when IFW did a backup using the
controller specification, it found the wrong disk. I powered down and
restarted this morning, and all was back to the way it should be. I
auto-reboot every night before the backup, and somehow after last night's
reboot the controller numbering came up different!

Has anyone seen anything like this before? Is it likely to recur? Is there
some way to set up IFW to search by drive letter rather than physical
controller #?

Thanks!
/j

Hi - Thanks - /d:0xabcdefgh sort of worked - but it captured both partitions on the main disk and I only want the first one. /d:?C: did what i wanted, but is that the proper way?. Will this get everything I need to recreate the disk with the C partition? (the D partition is scratch so I don't care about it).

Thanks!
/j

Add the Partition ID. For example...

/d:0xabcdefgh@0x1

that didn't work....

jeffw_00 wrote:
> that didn't work....

How about (typo above)....

/d:#0xAABBCCDD@0x1

(AABBCCDD is your Disk Signature)

If it doesn't work, what is your command line?

That worked - thanks! :-} (perhaps the manual could be a bit clearer on this? and maybe mention that the reassignment can happen and recommend this method? )

Best!
/j

jeffw_00 wrote:
(perhaps the manual could be a bit clearer on
> this? and maybe mention that the reassignment can happen and recommend this
> method? )

Jeff,

See page 37 in the IFW Manual. "Output Disk ID to Command Line –"

Didn't say there was no information - just make it a little clearer. I think you're suggested i should have
a) seen the feature,
b) found out what it did
c) check the box
d) look at the output
e) use the output to update my script.

I was thinking some more information where the /d: qualifier was presented might be useful

Just my $.02 FWIW
/j