Promise Technology FASTTRAK SX4300 - Manual (Page 59)

Chapter 6: Troubleshooting & Tips
53
Powering the system off and on once to reset the drive. Also confirm that
cables are properly attached and the drive is receiving power.
If the drive still appears to have failed, refer to the Rebuilding a logical drive
option in the WebPAM software as detailed in the WebPAM User Manual.
Drive cannot be formed into an logical drive
Disk drives must be free of media defects to be added into a logical drive.
Promise recommends using new identical disk drives for each logical drive.
Re-secure data and power cabling while checking for proper alignment.
System CMOS displays C: or D: drive failure during Startup
Do not reference C: or D: in the Motherboard Standard CMOS for drives
attached to the FastTrak controller. Only enter drive information in the
Motherboard CMOS for drives attached to the onboard IDE controller.
FDISK reports a much lower drive capacity if a single physical drive or a
striped logical drive exceeds 64GB (Windows 2000)
Due to a limitation with FDISK, the utility reports only the storage capacity
that exceeds 64GB. This is a cosmetic, not actual, limitation. Simply create a
single DOS drive partition, reboot, and then format the partition. The Format
command will recognize the total capacity of the partition accurately.
Windows will now recognize the total capacity of your logical drive.
Unable to Partition or Format Logical Drive
The MBR of one of the drives has become corrupt. Delete the existing logical
drive, then create a new logical drive with the Fast Init feature set to ON.
Cannot Rebuild Mirrored (RAID 1) Array
See Unable to Partition or Format array, above.
Fatal Errors or Data Corruption Are Constantly Reported When Reading or
Writing to Drive Array
See Unable to Partition or Format array, above.
Operating System-Related Issues
The Operating System no longer boots after creating a Mirrored Array using
your existing boot drive using Windows 2000/XP/2003 Server
This is due to Drive Geometry issues. You can verify this if you move the
original drive back to the onboard controller and it boots successfully. Each
controller can view a drive differently. This can be an issue for a new
controller that loads the original Master Boot Record (MBR) and then has a
problem translating it or the Operating System boot record.