Common Drive Error Messages and Solutions
Monday, January 31st, 2011Several common error messages are related to problems in the file system or drives. These usually occur when booting the system. It may also happen when attempting to log in or to access a drive. The common ones are the following:
- Missing Operating System
- No ROM Basic – System Halted
- Boot Error Press F1 to Retry
- Invalid Drive Specification
- Invalid Media Type
- Hark Disk Controller Failure
Missing Operating System
This error indicates problems in the master boot record or partition table entries. The partition table entries might be pointing to a sector which is not the actual beginning of a partition. This can also be triggered by invalid BIOS settings, in some cases resulting from a dead or dying battery. Another cause can be virus damage to the MBR. This error can also occur if no active partition is defined in the partition table.
You can solve this problem by correcting the invalid BIOS settings. The LBA translation and the BIOS settings for drive parameters must be set to the same values as when the drive was partitioned and formatted to read the drive correctly. You can try FDISK/MBR to repair a broken MBR on a FAT drive or FIXMBR with a NTFS drive. Other types of damage require more sophisticated use of a disk editor utility or repartitioning and reformatting the drive to start over.
No ROM Basic – System Halted
This error is generated by the AMI BIOS when the boot sector or master boot record of the boot drive is damaged or missing. You may also get this error when the boot drive has been improperly configured or is not configure at all in the BIOS. In this case, data in the partition might be valid and undamaged but no bootable partition exists.
IBM systems in this situation used to drop into a built-in BIOS version of BASIC, but most non-IBM BIOS manufacturers did not license this code from Microsoft. So, instead of dropping into BASIC, they displayed this cryptic massage. The typical solution to this problem is to run FDISK and set the primary partition as active because the most common cause of this type of error is a failure to set at least one partition as active (bootable). If this is not the problem, the solution is to repair the damaged MBR or correct the improper BIOS settings.
Boot Error Press F1 to Retry
This error is generated by the Phoenix BIOS when the hard disk is missing a master boot record or boot sector or when there is a problem accessing the boot drive. It is a problem similar to NO ROM Basic does on an AMI BIOS. No active partition is defined is the most common cause of this message.
Invalid Drive Specification
This error occurs when you attempt to log in to a drive that has not been partitioned or for which the partition table entry has been damaged or is incorrect. You can check the existing partition using FDISK or use FDISK to partition the drive. If they are damaged, you probably should use a data recovery tool including REMO to rectify the problem.
REMO is a Mac Recover Software that could also be used for Mac file Recovery. It will recover data on a failed hard drive and recover formatted memory card. It can also be used on Windows.
Another solution is to repartition the drive from scratch, but this causes any existing data on the drive to be overwritten.
Invalid Media Type
This indicates the partition table is valid, but the volume boot sector, directory, or file allocation tables are corrupt, damaged, or not yet initialized. For example, if you try to access a drive that has been partitioned but not yet formatted, you would normal receive this error. The volume boot record (VBR), file allocation tables, and directories on the disk are created by the format command.
The repair typically involves using a data recover utility or redoing the high-level format on the drive. Because high-level formatting does not actually destroy the data, one technique to recover is to high-level format (OS Format) the volume and then immediately unformat it using the unformat utility.
Hard disk controller Failure
You would get this error message when the hard drive controller has failed, the hard drive controller is not set up properly in the BIOS, or the controller can not communicate with the attached drives due to cable problems.
The solution is to check out the drive installation and ensure that the cables to the drive are properly installed, the drive is getting power, it is spinning, and the BIOS setup definitions are correct. If all these are correct, the drive, cable, or controller may be physically damaged. Substitute them with know-good spares one by one until the problem is solved.