Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Helping out a freind...he is trying to do a scan disk after having an odd problem with his D Drive; when he rebooted it immediately went into ScanDisk but would lock up around 42%. I was able to get him into Windows. Right now he is running the THOROUGH scan. Its been 12...TWELVE hours since he started.
<<Cluster: 1,034,327 of ( I think 2,7***) >>
is where he is at right now. The numbers are SLOWLY rising. He has an 80 GIG drive.Any ideas or is this going to take another 12 hours to finish?! Is there a formula time wise to GIgabyte wise?
Thanks!

What are the other settings besides thourough? If the settings are to autmatically repair the errors the scan may be starting over again. Just a thought. Seems excessive, time wise. I have done a 60GB in thourough before and it seems like it only took a few hours. I am not sure if the scandisk utility in Win98 can handle disks larger than 64GB. That may be the problem. Was this system working with the 80GB for any length of time?

80Gig? That's a pretty big drive. Might be better off trying some other disk utility. Try searching the net. Like OtheHill said, scandisk isn't really good at working with drives larger than 64GB.

Fuzz
Take a look here at info on what I was referring to.http://www.48bitlba.com/win98.htm
System tools in Windows 98 and Me do not work with 48-bit LBA hard drives. Specifically, Scan Disk, Defrag, and Fdisk tools do not work with the larger hard drives. Potentially, you could corrupt data on the hard drive if you run some of the tools. This will not be a problem if you keep this in mind and simply do not run any of these tools. However, Windows 98 and Me will automatically run the Scandisk tool at startup after a bad shutdown. There is a way to configure Windows to not run Scandisk after a bad shutdown. Further details can be found lower on this page.

I had him set the Automatically repair errors. All other settings were left as default. (its been a while since I worked with Win98. The 80 gig drive had been working fine for a long time until just this past couple of days so don't know what to make of that.
I never thought of that that Win98 does not exactly work well with such large drives. The D Drive is a secondary drive and is for data storage from what I understand. I'm still amazed he can GET an 80 gig drive to work with Win98 and to do the stuff he's doing (burning DVD-Rs-- but that's another post on how he did that...)
I'll check into the idea of other disk utilities.

As far as I know scandisk will work OK on partitions up to about 127 gig.
Is scandisk marking alot of spots as bad or is it just taking a long time?
Make sure the HD is properly identified in cmos. You may want to download a utility from the drive manufacturer to check the drive. You should be able to check the drive's warranty status from their site also. If it's bad and still under warranty you can RMA it back to them and get another drive.

I hadn't previously checked the link you provided but it doesn't matter since an 80 gig drive isn't a 48 bit LBA drive. The reference I had to scandisk working OK up to 127 gig is from here:

DAVINCAPS
You are absolutely correct.
My original response asked if the 80GB drive had been woking properly for any length of time. I was thinking that if the disk had been partitioned with the original version of Fdisk that the drive may be corrupted and scandisk is just bringing it to light.

Yeah, I'd think scandisk would just see an old-fdisk-created partition as 16 gig (or whatever it works out to) and not 80. But I've never experimented.
I had a relatively new 40 gig drive awhile back where scandisk was marking a large number of consecutive sectors as bad. I either did a zero fill or LLF, then repartitioned and formatted and after that it ran fine with no bad sectors. Kind of like the drive was having a psychosomatic problem.
But we don't know yet if Fuzz's drive is just taking a long time or is marking the spots bad. If the drive is still good I think he may need to zero it out anyway and start fresh.

I had a 60GB partition take over 10 hours to do scandisk after a system lockup. Win98SE 466 MHz Celeron.

scandisk /surface ran in DOS provides for the nice GUI that shows the progress similar to "Show details" does using defrag in Windows.
It shows all the sectors and shows those that contain bad clusters after it's initial scan of the drive.Bryan

![]() |
Disk write error
|
cant see my 2nd hd
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |