Quantum malfunctions (Fireball drive families)

Manufacturer: Quantum, Quantum Fireball drive families: EL, EX, CR, CX, lct08, lct10, lct15

Malfunction signs: A drive operates normally for some time (from15 minutes to several hours), then it begins to hit its positioner against the limiting stop.

It is a very frequent malfunction in those drive families, it is caused by the chip controlling the spindle motor and positioner; the chip has poor quality of factory soldering (please see the table), overheats because of that and stops to function normally.

One peculiarity of the TDA5247HT (AN8428NGAR) microchip is the availability of space for soldering in the lower part of its case acting, by the way, as its heatsink. It accomplishes heat abstraction from the chip and its dissipation along the board. Thus mounting and removal of that chip should be performed using a thermal air unit.

To repair that malfunction, you should unsolder the chip, broaden the soldering pad as shown in the figure 9 (that work can be performed using a lancet for removal of a portion of protective layer), blanch it and the lower part of the chip and solder the latter back pressing its case gently during soldering in such a manner that solder shows through board openings on the other side. Then you should carefully flush the soldered location because that chip has high-resistance analog outputs and fusing agent residue may disturb its normal operation.

That method undoubtedly improves the thermal conditions of the chip but it does not yield positive results always. If a chip used to be overheated for a long time, its resoldering does not remedy the situation. In that case the chip should be replaced. It is advisable to replace it with an identical model offered by Panasonic and having better thermal characteristics. Such chips can be purchased at stores selling electronic components. Its price may vary from 5 to 10$.

Read More

Intel RAID Controller Troubleshooting Guide: Some of my hard drives show up during POST and some do not

Drives not showing up in post can be caused by a variety of problems. Please check the
following:

• Are you using the latest BIOS and firmware for the server board and the latest firmware
for the RAID card?

• System memory limitations limit the number and size of option ROMs that can be used
in the system. If you place too many adapters in the system, or the ROMs on the
adapters you have installed take up too much space in memory, the option ROM on
your RAID controller may not expand correctly and will not show the hard drives that are
connected to it. Try turning off the expansion ROMs for any on-board device that is not
being used. For example, if your server board includes a SCSI controller that is not
being used, disable this SCSI controller in BIOS setup. For a list of tested peripherals
with the Intel RAID controller, download the Tested Operating System and Adapter List
from http://support.intel.com/support/motherboards/server.

• If you are using a Zero Channel Card that utilizes the on board IO controller, such as an
on-board SCSI or Serial ATA controller, the Option ROM scan for the on-board device
must be enabled. If it is not enabled, drives connected to that device will not show up
during POST.

• Confirm that the drive power cables are firmly connected. If you are using a chassis
with a backplane, make sure the power and SCSI cables are properly applied to the
backplane and the hard drives are firmly seated in the backplane.

• Check your SCSI ID numbers. SCSI devices must each have a unique ID on the SCSI
bus. This number is set with jumpers on the device. ID numbers should be set starting
at 0 and they must be set lower than 8 if booting from the drive. If you are using a
server chassis with a backplane, the device IDs are usually automatically set by the
backplane, but may be manually configurable.

• Check for proper termination on the SCSI bus. Intel RAID cards are by default autoterminating.

If your hard drives still do not show during post, please call your customer support
representative. Note the following information and have it ready to assist the support engineer:

• Model number and firmware revision of the RAID controller you are using.
• Manufacturer and model number of other add-in adapters installed in your system.
• Manufacturer and model number of hard drives installed in the system.
• Identify the type of termination used for the card.
• The SCSI IDs of the devices on your SCSI bus.
• The number and type of SCSI channels.
• Manufacturer and model of the memory used in the system and on the RAID controller
and whether it is on the tested memory list.

Read More

JPEG Files

JPEG FilesNext we will look at carving JPEG graphic files, as specified in the document “Description of Exif file format.” For complete details of the file format specification, please refer to the hyperlink to the document, listed on page 1 of this paper.

The JPEG graphic file starts with a Start of Image (SOI) signature of “FF D8”.  Following the SOI are a series of “Marker” blocks of data used for file information.  Each of these “Markers” begin with a signature “FF XX”, where “XX” identifies the type of marker.  The 2 bytes following each  marker header is the size of the marker data.  The marker data immediately follows the size and then the next marker header “FF XX” immediately follows the previous marker data.  There is no standard as to how many markers will exist, but following the markers, the signature “FF DA” indicates the “Start of Stream” marker.  The SOS marker is followed by a 2-byte value of the size of the SOS data and is immediately followed by the Image stream that makes up the graphic. The end of the image stream is marked by the signature “FF D9”.

In the event that a thumbnail graphic exists within the file, the thumbnail graphic will have the exact same components as the full-size graphic, with “FF D8” indicating the start of the thumbnail and “FF D9”, indicating the end of the thumbnail.  Since thumbnails are significantly smaller and less likely to experience fragmentation than their larger parent full-size graphic, they can be used as a comparison tool for evaluating what the entire jpeg graphic is supposed to look like, in the event you must do a manual visual review of the carved graphic.

By searching first for all locations of the “FF D8 FF” signature, you identify the beginning of each jpeg graphic. The reason for searching for “FF D8 FF” is that there are different versions of jpeg  files, some that start with “FF D8 FF E0” and some with “FF D8 FF E1”, and leaving off the 4th byte in your signature will catch all instances, but may result in some false hits.

Rather than carve a specific length of data, in this case we will start at the beginning signatureand carve until we find “FF D9”.  In the event of a non-fragmented jpeg graphic, without a thumbnail, this will carve the whole file.  If we slightly modify our logic, by including a “if  “FF D8” occurs again before “FF D9”, then carve to the 2nd instance of “FF D9″” statement in our search for jpegs, then we will carve entire files including their thumbnail as long as they are not fragmented.  Without this “if” logic, the first search would stop carving at the end of the thumbnail and result in an invalid jpeg.  In the event of a fragmented jpeg file, the above carving method results in either a partial jpeg file or a complete jpeg file that contains extraneous data in the middle of it.

After carving all jpeg files based on these rules, we next quickly review which carved jpeg files are complete, versus which ones are fragmented and need further analysis.  By carving all jpeg files to a folder, you next add that folder to your forensic tool that has partial graphic file viewing capabilities, such as the “Outside In” viewer that is built into many existing forensic tools.  Using a gallery view, you can quickly identify which files are not displaying properly, only showing a partial file, and require further analysis.

Once all fragmented or partial jpegs are identified, manual visual inspection of each of these files was used to determine at what point the fragmentation occurred.  This was done by approximating the percentage of the file that displayed correctly in the viewer before displaying  corruptly.  The raw data of the carved file was then reviewed at the data at that percentage of the file to attempt to identify where the valid graphic data ended.  For this process it was assumed that the extraneous data started at an offset that was a multiple of 512-bytes from the beginning of the file.  Once the extraneous data was identified, it was then removed from the partial jpeg and re-evaluated as possible sector data for other fragmented files that had previously been identified

Read More