Imaging and verification

  • Thread starter Thread starter Lil' Dave
  • Start date Start date
L

Lil' Dave

Operating 2 SATA drives. They are identical 250GB Seagate SATA2 drives
operating in SATA1 configuration speed (motherboard limitation), and I'm
using the stepdown to SATA1 jumper on both SATA drives. Bios remaps these
to primary ide master/slave, nothing physically on primary ide Also using a
USB external drive. Each physical drive has a partition that I direct as
target for imaging, primarily the boot partion image as source (on SATA1).

Imaging and verifcation are always successful on the USB drive.
Verification rarely fails on the 1st SATA drive (master). Verification
always fails on the 2nd SATA drive (slave). The imaging program also has an
asset to review the internal of the image file, verify, and export that
image file. I can export a previously verified image from SATA1 to SATA2,
but, that exported image fails verification afterwards. When I source the
image file from the USB drive and export to the SATA2 drive, then verify,
that verification is successful. The time to make the same image is
a-l-w-a-y-s less when targeted at the SATA2 drive.

I have to use the SATAs as mapped ide as to allow Millenium and 98SE to run.
They won't work on the SATA controller bios configuration.

What's going on regarding SATA2, and is there a fix?

--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
 
Operating 2 SATA drives.  They are identical 250GB Seagate SATA2 drives
operating in SATA1 configuration speed (motherboard limitation), and I'm
using the stepdown to SATA1 jumper on both SATA drives.  Bios remaps these
to primary ide master/slave, nothing physically on primary ide  Also using a
USB external drive.  Each physical drive has a partition that I direct as
target for imaging, primarily the boot partion image as source (on SATA1)..

Imaging and verifcation are always successful on the USB drive.
Verification rarely fails on the 1st SATA drive (master).  Verification
always fails on the 2nd SATA drive (slave).  The imaging program also has an
asset to review the internal of the image file, verify, and export that
image file.  I can export a previously verified image from SATA1 to SATA2,
but, that exported image fails verification afterwards.  When I source the
image file from the USB drive and export to the SATA2 drive, then verify,
that verification is successful.  The time to make the same image is
a-l-w-a-y-s less when targeted at  the SATA2 drive.

I have to use the SATAs as mapped ide as to allow Millenium and 98SE to run.
They won't work on the SATA controller bios configuration.

What's going on regarding SATA2, and is there a fix?

--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
Click to expand...

Two exactly identical model of hard drives are never 100%
identical!!! Each drive develops there own "bad" sectors at the
manufacture of the drive. These "bad" sectors will be remapped
automatically by the manufacturer prior to shipping the drive.

You will need to locate the correct diagnostic tools and evaluate the
SATA2 drive.
 
Thanks. Will use the CD boot version for dos to avoid any un-noted hardware
conflicts that may exist in XP.
The windows version says its for externals anyway.

--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
 
Operating 2 SATA drives. They are identical 250GB Seagate SATA2 drives
operating in SATA1 configuration speed (motherboard limitation), and I'm
using the stepdown to SATA1 jumper on both SATA drives. Bios remaps these
to primary ide master/slave, nothing physically on primary ide Also using
a
USB external drive. Each physical drive has a partition that I direct as
target for imaging, primarily the boot partion image as source (on SATA1).

Imaging and verifcation are always successful on the USB drive.
Verification rarely fails on the 1st SATA drive (master). Verification
always fails on the 2nd SATA drive (slave). The imaging program also has
an
asset to review the internal of the image file, verify, and export that
image file. I can export a previously verified image from SATA1 to SATA2,
but, that exported image fails verification afterwards. When I source the
image file from the USB drive and export to the SATA2 drive, then verify,
that verification is successful. The time to make the same image is
a-l-w-a-y-s less when targeted at the SATA2 drive.

I have to use the SATAs as mapped ide as to allow Millenium and 98SE to
run.
They won't work on the SATA controller bios configuration.

What's going on regarding SATA2, and is there a fix?

--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
Click to expand...

Two exactly identical model of hard drives are never 100%
identical!!! Each drive develops there own "bad" sectors at the
manufacture of the drive. These "bad" sectors will be remapped
automatically by the manufacturer prior to shipping the drive.

You will need to locate the correct diagnostic tools and evaluate the
SATA2 drive.

-----

I used the word "identical" to denote same model number, source of supply,
and date of purchase. I ended up writing that information here to clarify
for your false assumption.

Yes, I'm getting said software. Thanks to the other poster who provided the
link.

My feeling is there is nothing wrong with either drive. Its the remap SATA
to ide bios function, along with the slowdown SATA1 jumper causing a
subliminal I/O problem that XP can't detect. Note that I stated the USB
drive image export and verification are successful to the 2nd SATA drive.
This takes longer than 1st SATA to 2nd SATA export and verification. which
are always unsuccessful.
--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
 
Seagate Tools, short and long test, could NOT find any problem with either
Seagate SATA hard drive.

--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
 
Operating 2 SATA drives. They are identical 250GB Seagate SATA2 drives
operating in SATA1 configuration speed (motherboard limitation), and I'm
using the stepdown to SATA1 jumper on both SATA drives. Bios remaps these
to primary ide master/slave, nothing physically on primary ide Also using
a
USB external drive. Each physical drive has a partition that I direct as
target for imaging, primarily the boot partion image as source (on SATA1).

Imaging and verifcation are always successful on the USB drive.
Verification rarely fails on the 1st SATA drive (master). Verification
always fails on the 2nd SATA drive (slave). The imaging program also has
an
asset to review the internal of the image file, verify, and export that
image file. I can export a previously verified image from SATA1 to SATA2,
but, that exported image fails verification afterwards. When I source the
image file from the USB drive and export to the SATA2 drive, then verify,
that verification is successful. The time to make the same image is
a-l-w-a-y-s less when targeted at the SATA2 drive.

I have to use the SATAs as mapped ide as to allow Millenium and 98SE to
run.
They won't work on the SATA controller bios configuration.

What's going on regarding SATA2, and is there a fix?

--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
Click to expand...

Two exactly identical model of hard drives are never 100%
identical!!! Each drive develops there own "bad" sectors at the
manufacture of the drive. These "bad" sectors will be remapped
automatically by the manufacturer prior to shipping the drive.

You will need to locate the correct diagnostic tools and evaluate the
SATA2 drive.

-----

Seagate Tools, short and long test, could NOT find any problem with either
Seagate SATA hard drive.
--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
 
No, although I used the same software to do the partitioning. The 3 primary
partitions are hidden copied parttions of the 1st hard drive on the second
hard drive. As is the extended partition, and, 3 of its logical
drives/partitions. These logical drives are hidden by the partitioning
software on the second drive. The last and 4th logical partition are
different on the second hard drive, its FAT32. On the first drive its NTFS,
partition created by XP logical disk manager. Both have different volume
names. Both are visible at all times. System restore is disabled on all
partitions except the C: partition where XP is also installed.

The partitioning software is Partition Commander.

--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
 
So in one case you are imaging to NTFS partition
and on the other drive imaging to a FAT32 partition?

Also do both drives have at least one NTFS partition
that is visible to the image backup software?
 
SATA1, 4th logical is NTFS. SATA2, 4th logical is FAT32. Different volume
names. Yes, those are my designated target partitions for imaging.

The XP boot partition is NTFS type 3, that's my primary focus as source for
imaging. Hidden from XP are the other 2 primary partitions. One is NTFS
type 3, one is FAT32. Except for the one logical drive I've mentioned
previously, all other logical drives are FAT32.

The imagiing software can see all partitions for imaging purposes, except
for one hidden NTFS primary partition on SATA1, and, 2 hidden NTFS primary
partitions on SATA2. The only thing seen there is the partition size.
That's the same as the logical disk manager in XP.

--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
 
For the FAT32 partition where you create Image backup files
is your imaging software set to create multiple files if the image
file exceeds 4GB?
 
No, don't have to. It does that automatically as part of the imaging
process to FAT32 partitions as targets.

--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
 
Can you reverse the SATA cable connectors
on the motherboard so that drive 1 is now 2
and SATA2 is now SATA1 and then see if
the problem is associated with the same drive
or the problem is now associated with the drive
that previously had no image backup verification
problems.
 
Back
Top