Solutions to Common Drive Errors
Monday, January 31st, 2011There are several common file system or drives errors. They can happen during system boot up, log in or when you try to access a drive. You would normally get the following error messages:
- 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 is an error that is related to problems in master boot record or partition table entries. The partition table entries could be pointing to a sector that is not the actual beginning of a partition. Invalid BIOS settings, which sometimes is triggered by a dead or dying battery, could cause this error. 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 BIOS settings for drive parameters and LBA translation must be set to the same values as when the drive was partitioned and formatted to read the drive correctly. If the MBR on a FAT drive is damaged or virus infected, you can try FDISK/MBR to repair it. Use FIXMBR with a NTFS drive. More sophisticated disk problem require disk recovering tool or repartitioning and reformatting the drive.
No ROM Basic – System Halted
For an AMI BIOS, when the boot sector or master boot record of the boot drive is damaged or missing, you will get this error. 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, although bootable partition does not exist the data in the partition may still be valid and undamaged.
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, they would display this cryptic massage instead of dropping into BASIC. 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
when the hard disk is missing a master boot record or boot sector or when there is a problem accessing the boot drive, you may get this error, which is generated by the Phoenix BIOS. This has the same meaning as NO ROM Basic does on an AMI BIOS. No active partition is defined is the most common cause of this message.
Invalid Drive Specification
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 could get this type of error. 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 for example REMO to correct the problem.
REMO is a Mac Recover Software that may also be used for Mac file Recovery. It will recover data on a failed hard drive and recover formatted memory card. It could 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, you would receive this error if you tried to access a drive that had been partitioned but not yet formatted. The volume boot record (VBR), file allocation tables, and directories on the disk are created by the format command.
A data recover utility is required to solve this problem. Another solution could be 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
This message indicates the hard disk controller has failed, the hard disk controller is not set up properly in the BIOS, or the controller can not communicate with the attached drives (such as cable problems).
You can examine the drive installation and ensure that the cables to the drive are properly installed, the drive is getting power and spinning, and the BIOS settings for the drive are correct. If all these are correct, the drive, cable, or controller could be physically damaged. Replace them with know-good spares one by one until the problem is solved.