Learn How to Fix Common Drive Related Problems
Several common error messages are associated with problems in the file system or drives. These usually occur when booting the system. It might 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
It is an error that is related to problems in master boot record or partition table entries. You receive this error because the partition table entries are pointing to a sector that is not the actual beginning of a partition. Invalid BIOS settings, which sometimes is caused 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.
The normal solution is to correct 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. 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.
For IBM systems, it would normally drop into a built-in BIOS versions of BASIC if it is having the similar problem. However most non-IBM BIOS manufacturers did not license this code from Microsoft. so, they would display this cryptic massage instead of dropping into BASIC. Because the most common cause of this type of error is a failure to set at least one partition as active (bootable), the typical solution is to run FDISK and set the primary partition as active. 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. The most common cause of this message is having no partitions defined as active (bootable).
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. You should probably make use of a data recovery tool including REMO to correct the problem if the partitions are damaged.
REMO is a Mac Recover Software that could also be used for Mac file Recovery. It could 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, if you try to access a drive that has been partitioned but not yet formatted, you would normal receive this error. The format command is what creates the volume boot record (VBR), file allocation tables, and directories on the disk.
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).
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 could be physically damaged. Replace them with know-good spares one at a time until the issue is resolved.