 |
 |
How does the Forensic SF-5000™ handle bad sectors on the Suspect and Target drives? |
 |
 |
Bad (or "weak") sectors on the suspect drive are handled in the following way:
By default the first option is set to "Abort", the Forensic SF-5000™ will abort the capture process upon encountering the first bad sector. Note that the Forensic SF-5000™ will still make several attempts to correctly read the sector in question, but unless a perfect read was achieved, the process will abort.
The second option is "Skip". When this option has been selected, the Forensic SF-5000™ will still make several attempts to achieve a perfect read, but will move past the bad or weak sector instead of aborting. Note that there may be a CRC-32 mismatch after the capture session has completed.
The third option is "Retry". This option instructs the Forensic SF-5000™ to spend more time attempting to read all of the data from the bad or weak sector. This option can slow down the capture process.
The forth option is "Recover". When selected, the Forensic SF-5000™ will use a more complex algorithm in an attempt to retrieve as much data as possible from each bad or weak sector. Although this option is very effective at recovering data from bad or weak sectors, it can be time consuming.
Bad sectors on the target drive are handled as follows:
If the Verify setting is disabled, the Forensic SF-5000™ will not detect bad sectors on the target drive, unless the drive returns an error. Note, however, that newer drives use automatic reallocation and will rarely exhibit a bad sector, and thus reduce the probability of a problem to a negligible amount.
With the Verify setting set, the Forensic SF-5000™ will perform a scan operation on each sector after data has been copied. This scan occurs in step with the capture session and is transparent to the user. If an error is detected, the Forensic SF-5000™ will make several retries and abort if unsuccessful. |
|
|
 |
 |
How does the Forensic SF-5000™ calculate CRC-32? |
 |
 |
Both before and after a Capture session, the Forensic SF-5000™ performs a CRC-32 calculation on both the Source and Destination drives. During the CRC-32 calculation, (Software CRC-32) the sum of the bits in the last sector of each track is added and the final results are stored in memory. During the CRC-32, (Hardware CRC-32) the sum of all bits are calculated and stored in memory. These values, along with the type (hardware, or software) will be displayed on the report for each drive. The user will receive an error in the event of a mismatch. |
|
|
 |
 |
The Forensic SF-5000™ has a parallel port; can I attach it to a suspect PC for the purpose of capturing drive data without removing the drive from the PC? |
 |
 |
Yes, The parallel port on the Forensic SF-5000™ may be used to capture data from a suspect PC. In addition, it is used for printing sessions and performing software updates. |
|
|
 |
 |
What exactly does the Wipe clean Target drive do? |
 |
 |
The Wipe clean Target mode writes zeros to every sector on the target drive. This is single pass operation. Both the pattern (0x00) and the number of passes (1) are fixed and cannot be modified by the user.
There are two methods of wiping:
|
1. |
With Signature - this is the default setting that writes a signature to the destination drive that indicates that the drive was wiped. The unit WILL recognize the drive as having been wiped. |
|
2. |
Without Signature - this setting wipes the drive without writing a signature. The unit will NOT recognize drives as having been wiped if they lack our signature. | |
|
|
 |
 |
Why does the Target drive erase speed vary so greatly? |
 |
 |
The Forensic SF-5000™ searches the suspect drive for blank areas to use as a pattern source to write to the target drive. If the suspect drive does not contain blank sectors, the Forensic SF-5000™ will then create a pattern in memory to erase the target drive. This is a much slower process, as it requires considerable CPU bandwidth. |
|
|
 |
 |
The Forensic SF-5000™ does not recognize the suspect (or target) drive? |
 |
 |
Make sure that the drive jumpers are set as a single master. Drive jumper settings can be found at the drive manufacturer web site. Also, check the condition of the data and power cables; they are rated for a maximum of 500 insertions. New cables can be ordered from Logicube sales. |
|
|
 |
 |
Why do I sometimes see transfer speeds greater than 975MB/min, and other times as low as 200MB/min? |
 |
 |
There are many factors that determine transfer speed:
The age of the drives - The speed of the operation is governed by the slowest drive in the system. If an old drive is used, chances are it cannot sustain high transfer speed. Newer drives have faster electronics and larger caches, and can sustain rates as high as 16MB/sec.
Suspect drive with bad or weak sectors - With the Sector Recovery option enabled, the system will attempt to recover data from bad or weak sectors found on the suspect drive. This can be a time consuming operation, and may cause the overall speed of the capture to drop.
Suspect drive with bad or weak sectors - With the Sector Recovery option disabled, the standard retry mechanisms may still result in a reduction in transfer speed. |
|
|
 |
 |
What is the printed report? |
 |
 |
The printed report is a single page report that includes the manufacturer, model number, and serial number and drive geometries of both the source and destination drives. The report also gives any options used and user settings. The CRC-32 from the Source drive and the CRC-32 from the destination drive after the capture process is completed is also recorded. The report also allows for the user to record the case number, location, time and date of capture and the name of the officer doing the capture. |
|
|
 |
 |
Can the Solitaire™ clone to dissimilar drives? |
 |
 |
Yes. The Solitaire™ will take care of all the necessary adjustments of target drive structures to ensure the drive (of any size) will be valid and bootable. Many mixtures of master and target drive sizes (up to 80GB) were tested, and found valid. The above is true for all master drives that contain FAT16/FAT32/NTFS/Windows 2000 type partitions. Unknown partition types are cloned in mirror mode, and typically require identical (or very similar) master and target drives to guarantee a successful clone. |
|
|
 |
 |
Can I clone to/from laptop drives? |
 |
 |
Yes. Logicube sells 2.5" drive adapters, and can provide adapters to many of the special drive connections on the market. Please call for availability. Or, in cases where the drive cannot be removed from the laptop, you can use the parallel port connection or the CloneCard™ for coping through the PCMCIA interface. |
|
|
 |
 |
Can I clone to/from drives larger than 80 Gigabytes? |
 |
 |
Yes. The firmware was designed to support drives up to at least 750 GB. |
|
|