Wednesday, October 29, 2008

Problems with Hard Drive



Issue
  • Corrupted file header
Description
  • If an application cannot open or read one of its data files, the file header might be corrupted. Many application place a file header at the beginning of the file. The application users the file header to identify the file and its contents.
Resolution
  • You can sometimes recover the content by treating the file as an ACII text file. In Windows Explorer, change the files extension to. Txt and then import the data into the application. Read you applications documentation to learn how to import a text file (you will lose any formatting.
===============================================
===============================================
Issue
  • Lost cluster
Description
  • A disk can develop lost cluster if a program cannot properly close a file it has opened.
Resolution
  • Use Windows Error-checking tools or the Chkdsk command to repair lost cluster.
===============================================
===============================================
Issue
  • Erased file
Description
  • if you accidentally deleted a file, the file sometimes can be recovered.
Resolution
  • Look for the file in the Recycle Bin. If it is not there, try using the Unerase or Undelete command at a command prompt, which recovers some erased files.
===============================================
===============================================
Issue
  • Virus infection
Description
  • Viruses cause many files system problems, including corrupting system files, program files or data files.
Resolution
  • Run a current version of anti-virus software. The software probably will not help recover the file but might prevent other files from becoming infected.
===============================================
===============================================
Issue
  • Corrupted date on floppy disk
Description
  • If your system cannot read date on floppy disk, the floppy disk might be damaged or the data might be corrupted.
Resolution
  • Use Copy Disk in Windows Explorer to make a copy of the disk, if this does not work, try copying the disk with a third-party program such as Norton Utilities.

On-Screen Error Messages During POST

P.O.S.T
(Power On Self Test)

When you turn on the power to a PC, the
CPU begins the boot process by initializing itself
and then turning to the ROM BIOS for instructions.

The ROM BIOS then performs the
Power On Self Test or POST.

Once POST and the first pass at
assignment of resources are complete,
the next step is to load an OS



On-Screen Error Messages During POST

Error Message
  • CMOS battery failed
Possible Causes
  • Weak CMOS battery.
Course of Action
  • Load default setting in Setup and reboot the system.
  • Replace CMOS battery
===============================================
===============================================
Error Message

  • CMOS checksum error
Possible Causes
  • Hardware devices are not configured properly in CMOS.
  • Weak CMOS battery
Course of Action
  • Make sure the devices (mouse, drive, keyboard, etc) are connected properly and are set correctly in BIOS setup.
  • Load default setting in setup.
  • CMOS battery might need to be replaced.
===============================================
===============================================
Error Message

  • Memory size error
Possible Causes
  • Memory is not inserted properly
Course of Action
  • Make sure the DIMMs (Dual In-line Memory Module) are inserted properly.
  • This would also be displayed after upgrading the memory.
  • In this case, just enter the BIOS setup and save the new setting
===============================================
===============================================
Error Message
  • Memory test failure
Possible Causes
  • Memory is not inserted properly
  • The memory is physically damaged and can no longer be used.
Course of Action
  • insert the memory module in theDIMMs (Dual In-line Memory Module) sockets properly, and then reboot the system.
  • If needed, replace memory module.
===============================================
===============================================
Error Message
  • Keyboard error or no keyboard present
Possible Causes
  • Keyboard is disconnected or defective.
  • This can also be caused by a depressed key during a POST (either due to an object place on top of the keyboard or a stuck key).
Course of Action
  • Make sure the keyboard is connected properly and is set correctly in BIOS setup.
  • Replace keyboard if defective or repair defective key.
===============================================
===============================================
Error Message
  • FLOPPY DISK(S) failure(80)
Possible Causes
  • Unable to reset floppy subsytem.
Course of Action
  • Check floppy drive cable and for defective floppy drive.
===============================================
===============================================
Error Message
  • FLOPPY DISK(S) failure(40)
Possible Causes
  • Floppy type mismatch
Course of Action
  • Check BIOS setup on floppy disk type
  • Check for defective floppy drive
===============================================
===============================================
Error Message
  • Hard disk(s) Diagnosis failure
Possible Causes
  • Hard drive may be physically damaged
  • Hard drive cables may not be properly attached.
Course of Action
  • Make sure that the hard disks are set correctly in CMOS setup.
  • Check the hard disk drive cable and connection.
  • If needed, replace the hard drive.
===============================================
===============================================
Error Message
  • Primary master hard disk failure
  • Primary slave hard disk failure
  • Secondary master hard disk failure
  • Secondary slave hard disk failure
Possible Causes
  • Hard disk may be physically damaged.
  • Hard drive cables may not be properly attached.
Course of Action
  • A warning message to indicate a need fopr change in IDE Primary (Secondary) Channel Master (Slave) device.
  • Load default setting in CMOS setup. Check IDE drive jumper, the power connection and file drive cable and connections.
  • If needed, replace the hard driver/s.
===============================================
===============================================
Error Message
  • Mouse error or no mouse present
Possible Causes
  • Mouse is not connected properly or defective mouse.
Course of Action
  • Make sure the mouse is connected properly and is set correctly in CMOS setup.
  • Check for defective mouse.

PC's General Error Messages


Error Message
  • Invalid partition table
  • Error loading operating system
  • Missing operating system
  • Invalid boot disk
  • Inaccessible boot device
Possible Causes
  • The Master Boot program at the beginning of the hard drive displays the following messages when it cannot find the active partition on the hard drive or the boot record on that partition
Course of Action
  • Use Fdisk to examine the drive for errors.
  • Check the hard drive manufacturer's Web site for other diagnostic software
===============================================
===============================================
Error Message
  • Missing operating system, error loading operating system
Possible Causes
  • The MBR is unable to locate or read the OS boot sector on the active partition
Course of Action
  • Boot from a bootable floopy and examine the hard drive file system for corruption or run scandisk from the Windows Installer CD.
===============================================
===============================================
Error Message
  • Bad sector writing or reading to drive
Possible Causes
  • Sector marking on the disk may be fading
Course of Action
  • Try running Scandisk first (from the Windows Installer CD if nesessary). If it fails, consider reformatting the disk.
===============================================
===============================================
Error Message
  • Configuration/CMOS error
Possible Causes
  • BIOS setup information does not agree with the actual hardware the computer found during boot.
  • May be caused by a bad or weak battery or by changing hardware without changing setup.
Course of Action
  • Check BIOS setup for errors. If it doesn't work, try replacing the CMOS battery.
===============================================
===============================================
Error Message
  • Hard drive not found
Possible Causes
  • The operating system cannot locate the hard drive or the controller card is not responding.
Course of Action
  • Check the hard drive power and IDE cable if these are properly attached.
  • Else, check if the hard disk is detected using the auto-detect feature of the BIOS Setup.
===============================================
===============================================
Error Message
  • Fixed disk error
Possible Causes
  • The PC cannot find the hard drive t hat BIOS setup told it to expect.
Course of Action
  • Verify if hard drive exists in BIOS setup information.
  • Check power supply power cables, and connections.
===============================================
===============================================
Error Message
  • Invalid drive specification
Possible Causes
  • The PC is unable to find a hard drive or a floppy drive the BIOS setup tells it to expect.
Course of Action
  • Look for errors in BIOS setup or for a corrupted partition table on the hard drive.
===============================================
===============================================
Error Message
  • No boot device available
Possible Causes
  • The hard drive is not formatted or the format is corrupted.
Course of Action
  • Boot from a bootable disk and examine your hard drive for corruption or run scandisk from the Windows Installer CD.
  • Check if an active partition has been set on the hard drive.
===============================================
===============================================
Error Message
  • Non-system disk or disk error
  • Bad or missing command.com
  • No operating system found
Possible Causes
  • The disk in drive A is not bootable or cannot find the OS on the hard disk.
Course of Action
  • Remove the disk in drive A and boot from the hard drive. If no disk is in drive A, command.com on drive C might have been erased or the path could not be found.
  • Check the hard drive for corruption
===============================================
===============================================
Error Message
  • Not ready reading drive A: abort, Retry, Fail?
Possible Causes
  • The disk in drive A is missing, is not formatted, or is corrupted.
Course of Action
  • Try another disk or remove the disk to boot from t he hard drive.
===============================================
===============================================
Error Message
  • Bad command or file not found
Possible Causes
  • The OS command that was just executed cannot be interpreted or the OS cannot find the program file specified in the command line.
Course of Action
  • Check the spelling of the filename
===============================================
===============================================
Error Message
  • Write protect error writing drive A:
Possible Causes
  • The disk in drive A is protected
Course of Action
  • Let the computer write to the disk by sliding the write-protect tab (locked when hole is open) on the 3 1/2-inch disk.
===============================================
===============================================
Error Message
  • Track 0 bad, disk not usable
Possible Causes
  • This usually occurs when you attempt to format a floppy disk using the wrong formate type.
  • The disk may also be physically damaged and can no long be used.
Course of Action
  • Check the disk type and compare it with the type specified in the formate command.
  • Replace the disk.
===============================================
===============================================
Error Message
  • Device not found
Possible Causes
  • Errors in System.ini, Win.ini or the registry.
Course of Action
  • Look for references to devices or attempts to load device drivers.
  • Use Device Manager to delete/disable the device or edit System.ini or Win.ini.
  • Check for possible OS corruption.
===============================================
===============================================
Error Message
  • Device/Service has failed to start
Possible Causes
  • A hardware device or driver necessary to run the device or critical software utility is causing problems.
Course of Action
  • This type of protection is best handled using OS troubleshooting methods and tools.
===============================================
===============================================
Error Message
  • Error in Config.sys line xx
Possible Causes
  • A problem has occurred when loading a device driver or withe the syntax of a command line.
Course of Action
  • Check the command line for errors.
  • Verify that the driver files are in the right directory.
  • Reinstall the driver files, if necessary.
===============================================
===============================================
Error Message
  • Insufficient Memory
Possible Causes
  • This errors happens during or after the boot under Windows when too many applications are open.
  • This also occurs when the (virtual) memory manager does not release unused memory or the hard disk used for the virtual memory is low on free space.
Course of Action
  • Close some applications.
  • Also consider rebooting the system to clear items from the memory.
  • Consider cleaning (free up space) the hard disk used by the virtual memory.

Approaches in Troubleshooting a PC

When troubleshoot a PC, keep a few Fundamental rules in mind:

  • Make backups before making changes.
  • Follow the important safety precautions.
  • Approach the problem systematically.
  • Isolate the problem.
  • Boot from a disk to eliminate the OS and startup files on the hard drive as the problem.
  • Do not assume the worst.
  • Check simple things first.
  • Become a researcher.
  • Know your starting point
  • Establish your priorities.
  • Do not rush.
  • Write things down.
  • Take a break.