Faults, causes, and handling of hard drive failures

Source: Internet
Author: User

(1) black screen faults
Cause: the data line at one end of the hard disk cannot be reversed)
Processing: Re-plug it (the red line of the data line is adjacent to the red line of the power line)


(2) display the fault of "Primary master hard disk fail"
Cause: (1) At least one hard disk data cable or power cord is not plugged in.
(2) the hard disk jumper is set to the slave disk, while the CMOS hard disk parameters are not modified (still the master disk)
Processing: (1) pin it
(2) resetting CMOS


(3) faults without prompt information
Cause: (1) Some values of the CMOS hard disk parameters are incorrectly set.
(2) Primary Boot Record errors or loss
(3) primary DOS boot records the first important data (number of bytes per row) Error
(4) The File Allocation Table is incorrect.
Processing: (1) resetting CMOS
(2) restore with the FDISK/MBR command
(3) Use DISKEDIT to fix it to 512
Procedure: start the computer with a floppy disk and run in diskedit/w/m mode; press Alt + P,
Change "face 0" to "face 1", and click OK. Press F7 to view it as a boot record.
Change the value of the number of bytes to 512 ".
(4) use DISKEDIT to call the second allocation table and use NDD to fix the problem. (For the download URL, see the end of the article)
Procedure: start the computer with a floppy disk and run diskedit. In the drop-down menu of "Tools ",
Select "Use the second FAT table", exit diskedit, run ndd, and select
"Diagnose disk", step by step follow the prompts until the operation is completed.


(4) display "disk boot failure, INSERT SYSTEM DISK AND PRESS
ENTER fault
Cause: (1) the hard drive and optical drive are connected to the same data cable, and the jumper is set to the master disk (or both are set to the slave disk)
(2) set the parameter of the CMOS hard disk to NONE.
(3) An error occurred while marking the end of the primary Boot Sector 55AAH.
Processing: (1) set the optical drive jumper to the slave disk (or the hard drive jumper to the master disk)
(2) resetting CMOS
(3) "diagnose disk" with NDD


(5) display "Error Loading Operating System" faults
Cause: the active partition mark 80 h in the hard disk partition table is changed to a value other than 00H (for example
Change to FFH)
Processing: fixed to 80 H with DISKEDIT
Procedure: start the computer with a floppy disk and run in diskedit/m/w mode. press Alt + P,
If no modification is made, press Enter. Press F2 to view it in hexadecimal format, and set B0
The second-to-last hexadecimal value of the address line is changed to 80.


(6) display "Not Found any [ative partition] in HDD" faults
Cause: the active partition identifier 80 H in the hard disk allocation table is changed to the inactive partition identifier 00 H.
Processing: fixed to 80 H with DISKEDIT
Specific steps: Same as (V)


(7) display "Type the name of the command, Inter preter ...... "
Cause: (1) the primary DOS partition flag in the hard disk partition table is incorrect after
(2) command.com is lost, damaged, or different from the other two Startup file versions.
Processing: (1) Use DISKEDIT to fix it to 06 H
Procedure: start the computer with a floppy disk and run in diskedit/m/w mode. press Alt + P,
If no modification is made, press Enter. Press F2 to view the modification in hexadecimal format, and press 000001C0
The third hexadecimal value of the address line is changed to 06.
(2) copy and overwrite the command.com file in a floppy disk (note that the version must be the same)


(8) enter d: Press enter (e: Press enter, f: Press ENTER) under DOS and then display "Invalid drive specification"
(Note: This phenomenon does not affect hard disk startup, for reference only)
Cause: (1) the CMOS hard disk parameter LBA is set to LARGE
(2) The inactive partition mark in the hard disk partition table is incorrect for H.
(3) Some data error of the extended DOS partition guide fan
Processing: (1) resetting CMOS
(2) Use DISKEDIT to fix it as 00 H
Procedure: start the computer with a floppy disk and run in diskedit/m/w mode. press Alt + P,
If no modification is made, press Enter. Press F2 to view it in hexadecimal mode, and set
The last and second hexadecimal values of the address line are changed to 00.
(3) Use DISKEDIT to fix
Specific steps: the situation is complex and requires detailed analysis.


(9) display "Invalid partition table"
Cause: some data in the hard disk partition table is incorrect.
Processing: fixed with DISKEDIT
Specific steps: the situation is complex and requires detailed analysis.


(10) display "Disk I/O error ...... "
Cause: the physical hard disk flag number in the Boot Record of the primary DOS is incorrect.
Processing: Change DISKEDIT to 80 H (the first physical hard disk ID)
Procedure: start the computer with a floppy disk and run in diskedit/m/w mode. press Alt + P,
Change the default value to: column 0, 1 fan, 1 fan, OK; press F2 to view in hexadecimal mode, set 00000020
The fifth hexadecimal value of the address row is changed to 80.


(11) Show "Missing operating system"
Cause: (1) three data errors in the initial location in the hard disk partition table
(2) An error occurred while marking the end of the primary DOS Boot Sector 55AAH.
Processing: (1) Use DISKEDIT to fix the problem as one face, zero cluster, and one fan.
Procedure: start the computer with a floppy disk and run in diskedit/m/w mode. press Alt + P,
If no modification is made, press Enter. Press F2 to view it in hexadecimal mode, and set
The second to last hexadecimal value of the address line is changed to 00.
(2) Use DISKEDIT to fix it to 55AAH
Procedure: start the computer with a floppy disk and run in diskedit/m/w mode. press Alt + P,
Change the default value to: column 0, 1 fan, 1, confirm, and change the last two hexadecimal values to 55AA.


(12) Show "Invalid system disk"
Cause: the io. sys file does not exist.
Processing: Replace with an I/O. sys copy in a floppy disk or use the sys c: Command for transmission (note that the version must be the same)


(13) Show "Non-System disk or disk error"
Cause: Same as (12)
Processing: Same as (12)


(14) Show "Failure... "
Cause: io. sys is modified.
Processing: Same as (12)

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.