December 28th, 2000, 01:46 PM
data error reading drive c
I'm cannot get my c: drive to boot. When I turn on my computer I get "data error reading drive c:" followed by a c prompt. I can use DOS but thats all. Thanks.
December 28th, 2000, 02:01 PM
You didn't say what operating system you are using (DOS 6.x, Windows 95). In my experience this usually means the drive is dieing.
Try running SCANDISK to see what errors it finds. This will only be available DOS 6.2 and above.
If you have data that you don't want to lose, make sure you back everything up.
I recently worked on a Windows 98 machine that failed to boot. We reinstalled Windows and after one boot, it failed. It turned out that the hard drive had a bad sector right where the BOOT files are installed. So it would corrupt the boot files every time. That drive gave "Error reading Sector" messages.
Let us know where this gets you and more info about your system.
January 3rd, 2001, 01:50 PM
Yes, I agree, be sure you have a backup then
run scandisk and be sure to run the surface scan. I believe this option marks any problem areas of the disk as unusable. Afterwards, the error message should not appear again.
I never say thingy.
Open your mind, not your computer.
January 5th, 2001, 07:48 PM
You can also run chkdsk.exe if you have an older Dos version. It is not as performant as scandisk, but it may get you able to boot again. But you should still get scandisk and run it with surface scan and make an undo disk. It may be just a FAT problem (a system crash may have caused a cross linked entry).
[Note: This message has been edited by Igor M]
January 5th, 2001, 08:03 PM
Data error reading drive C?
Assuming that the drive is setup correctly in the system BIOS theres only another posssibility
Bad sectors on the hard drive
Download the manufacturers hard drive tools & run them. If it fails the diagnostics replace it
In the beginning there was the command line
January 5th, 2001, 11:52 PM
You guys have been on Win 95/98 too long.
Unless you are loading DOS from your A drive - If you can run DOS, your C drive is booting.
If you have a bad cmos battery your drive setup may have reverted to a type that, while it can read the boot sector, and possibly other items, like DOS, that are stored on the first few sectors of the disk, the addressing doesn't match correctly as upper sectors are addressed and the software reports a data error. You need to know the Head/Track/Sector information for your disk, 'cause most of the older DOS machines don't have the ability to get that information from the drive like the Win-95 PNP machines do. Most of the drive Mfgr's web sites have that info available.
January 6th, 2001, 02:15 AM
dacomputers, With all do respect, "You guys have been on Win 95/98 too long." ???
If the computer boots to a C prompt, usually the drive is set up in the CMOS correctly (unless somebody entered new settings which is not likely). If the battery lost the settings it would not boot.
If it is Windows 9.x, a bad sector could hose the MSDOS.SYS file in which case you could Boot to DOS but Windows wouldn't work. Likewise if other pertinent Windows files are damaged.
While you could be right in some machines that there may be default Hard drive settings that would be recalled if the battery died, that would be rare.
As for the "Win 95/98 too long", this is the DOS/Windows 3.1 forum. It would most likely be Windows 3.1 that bettietemp is using. But that has not been verified.
[This message has been edited by Eeyore (edited 01-06-2001).]
January 6th, 2001, 12:10 PM
Most of us have been teching DOS since well before 95 released. Heres a Microsoft KnowledgeBase artice to substantiate
Hard Disk Errors Caused by Damaged Data or Physical Damage
In the beginning there was the command line
January 8th, 2001, 07:02 PM
I tried running SCANDISK and got the error message was "data error reading FAT on drive C" right off the bat. I then did CHKDSK and got the message "c:\qtinstal.exe is crosslinked on allocation unit 18,302". I stopped there, having no clue what this means. BTW, I have Dos 6.2 and win 3.1.
January 8th, 2001, 09:16 PM
To put it in simple terms when you store a file on the drive it is split in to several pieces all over the drive. The index keeps track of where all these pieces are so the file can be reassembled. Crosslinked means the index show two different files using the same bit of data. While that happens a fair amount of time when everything is right, the error reading the FAT would indicate that the drive is going bad. This is the index. There are two of them. If they are not identicle, you will get an error. If a part can't be read, you get an error.
If you are still able to read the drive, you can backup the data. But the drive is most likely finished. You could attempt a rebuild. But you risk losing all of the data.
January 9th, 2001, 09:26 AM
If it was my hard drive, (and I didn't have Norton Disk Doctor), here's what I'd try next:
[list=1][*]Boot from a MS-DOS 6.20 System Disk in drive A:
[*]At the A:\> prompt, type:
scandisk c: /autofix /surface
Note: If scandisk refused/failed to run, I'd try chkdsk c: /f
[*]Remove the floppy from A: and try rebooting from the hard drive.[/list=a]
- See the Warnings on this page before running the fdisk /mbr command.
- You can download a program that will create a MS-DOS 6.20 boot disk from this page.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)