Toshiba L630 Laptop User Manual


 
2.5 HDD 2 Troubleshooting
2-11 Satellite/Satellite Pro/L630/L635 Maintenance Manual
create a DOS partition on drive C. Then restart the computer.. If the
problem persists, go to Procedure 3.
Check 3 If drive C is listed as active in the FDISK menu, perform Check 4. If drive C
is not listed as active, return to the FDISK menu and choose the option to set
the active partition for drive C. Then restart the computer. If the problem
persists, perform Check 4.
Check 4 Enter DIR C: and press the Enter key. If the following message is displayed,
go to Procedure 3. If contents of drive C are listed on the display, perform
Check 5.
Invalid media type reading drive C
Abort, Retry, Fail?
Check 5 Use the SYS command in the DOS system to install system files.
If the following message appears on the display, the system files have been
transferred to the HDD. Restart the computer. If the problem persists, go to
Procedure 3.
System transferred
NOTE: If the computer is running Windows 7 Home edition and the hard disk capacity is
more than 512 MB, the FDISK program will ask if you need support for a partition larger
than 2 GB. Select Y for large partition support; however, be sure to read the precaution
regarding access by other operating systems.
Procedure 3 Format Check
The 2.5-inch HDD is formatted using the low-level format program and the FREE-DOS
FORMAT program. Using these programs, follow the steps below to format the HDD.
Check 1 Enter FORMAT C:/S/U to format the HDD and transfer system files. If the
following message appears on the display, the HDD has been formatted.
Format complete
If you cannot format the HDD using the test program, go to Procedure 4.
Procedure 4 Test Program Check
Run the HDD test program stored on the maintenance test program disk for all test items. See
Chapter 3 for details on how to use the test program.
If an error is detected during the HDD test, an error code and status will be displayed. The error
codes and their status names are listed in Table 2-1. If an error code is not generated and the
problem still exists, go to Procedure 5.