I have a feeling you aren't even aware what "mapping" bad sectors means.
It's part of the filesystem. NTFS and FAT keep a list of bad sectors, and they dont use them. Remapping is the action of detecting a bad sector, recovering the data from that sector and storing it in another sector(a spare sector, which most drives have especially for bad sectors(thus the S.M.A.R.T register for "spare sectors"). The list prevents that sector from ever being used again.
Since it's part of the file system, formatting means the list needs to be rebuilt. Additionally, since a Low level format was performed, the Servo information that stored bad sectors of the drive from manufacture (yes, that's right- almost all hard drives have bad sectors. You just don't see them because the drive logic board omits them from all software level information.
why not? it's the unflagged bad sectors that cause problems.
once a chkdsk /r is performed, they will be flagged.
That would suggest that the Windows 2000 installer forgot something and the people who designed it had never heard of bad sectors and they did not know that checkdsk would fix it.
the windows installer doesn't run the chkdsk utility with the /r switch. It would take too long. It's not because they "forgot" something, but rather because they didn't think people would like waiting 3 or 4 hours to install windows.
Additionally, you cannot exclusively leave all the sectors adjacent to the damaged sector unpartitioned. While you can omit adjacent sectors on teh same track easily, doing so for sectors on the tracks adjacent to the track of the damaged sector would involve partitioning into several different partitions.
Since using chkdsk /r was suggested to flag all current bad sectors and keep them from being used, I don't see what particular benefit omitting a "known bad area" of a drive would do when in fact it's not really omitting a "known bad area" since a hard drive isn't a long sequential tape. Sectors that aren't sequentially labelled via LBA are still adjacent, since they are present on different tracks.
It's only when a drive has started accumulating lots of bad sectors, fairly suddenly, or that you've finally exhausted the spare sectors pool, that it is time to worry, and replace the drive. These symptoms are usually caused by a head crash which has physically scratched a platter or its oxide coating in one area, or eventual stress causing flaking of the oxide coating in one area. Repeated attempts to format or recover data from the area can actually cause the drive to fail faster, as the head is moved into the damaged area of the platter, often intensively, trying to read data, or repair the sector map. If you can just mark out the suspect sector, and never go there again, the drive may actually work a long while without further degradation. This happy result, of course, is more likely, if the bad area isn't in the middle of a platter, where the head has to physically traverse the area repeatedly on its way to further inner or outer tracks, even once it has been marked out. Head servos are good at jumping small defect areas, but not perfect, and if the flaking is across several radially contiguous sectors of the platter, the drive will continue to fail in operation, no matter what clever remap schemes are used, simply because the head servo can't jump the heads out of the way fast enough to get around the damage.
I get 0x000000ce when attempting the 2k install.
Squall- if your still there (lol) does the BSOD give you a filename?
Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT _CANCELING_PENDING_OPERATIONS - This Stop message occurs when you install a faulty device driver or system service, the driver failed to cancel pending operations before exiting.
The most humourous part of all if this is that Squall said "corrupted sectors" which could be something entirely different from "bad sectors".
