Bad sectors are mainly due to the magnetic weakening of the domain and mechanical faults. Over time, the magnetic areas of a disk lose its magnetism and hence its inability to retain data. Such bad sectors have the tendency to spread and are usually non-repairable. Mechanical faults include physical shocks to the disk, abrupt power shutdowns and disruptions during read-write operations. Head crash can also cause bad sectors and lead to permanent data loss on the disk. When bad sectors spread, it can result in system instability when important system files are destroyed. Mild corrupted data however can be corrected by most file system utilities.
Unknown to most, the bad sectors could some times be due to bad parity checking bits written on disk. Most modern disk while storing data will transparently store parity bits together with the data. When the data is read, the parity bits are also retrieved and compared to ensure the data integrity. This goes on without the knowledge of normal user. When the parity bits are corrupted for some reasons, it will result in bad sector errors. In this case, through some proprietary recovery software, ADRC could actually repair the bad sectors without loss of data by correcting or rewriting the corrupted parity bits on disk.
Very often, bad sectors are manifested as a result of failing Read Write head. When the Read Write heads fail to read and interpret the magnetic signals normally, the same kind of bad sectors errors could occur. Frequently, bad sectors are also early signs of disk crash as it deteriorates over time.
Solution to Bad Sector Problem
If the disk is still working well, important data should be backed up immediately to avoid further data loss. If the system respond is virtually "hanging" to a standstill and you have valuable data, the best option is to consult a data recovery specialist without doing this yourself.
Commonly, a full format process should be able to "mask" the bad sectors or earmark the bad sectors in file allocation table. One could continue to use the disk while the operating system will take notice of the location of bad sectors and avoid them altogether.
Another common CHKDSK utility provided by Windows Operating System may help to detect and mark for bad sectors. During a surface scan, it attempts to write data to that sector and then read back what it wrote. If the two do not match, the sector is marked as bad as it does not maintain data integrity. The operating system will note the particular sector and avoid writing new data onto that area of disk. After which, the bad sector will be remapped to a special sector on the drive which is reserved for this purpose.
For Windows 98, ME users, follow these steps:
- To do this, click Start, point to Programs
- Point to Accessories, point to System Tools and select ScanDisk
- Select the Thorough option and click Automatically Fix Errors
- Click Start
- On the desktop, double click on My Computer
- <>Right click and select Properties on the erroneous drive
- Open the Tool Tab
- Select Check Now under Error Checking
- Select the option to Automatic Fix File System Errors and Scan For And Attempt Recovery For Bad Sectors
CHKDSK offers 2 modes of scanning:
Error Checking
This mode scans your computer's files and folders. It searches and repairs any minor corrupted files and inconsistencies it detects.
Surface Scan
This mode scans every sector of the disk and identifies bad sectors. When a bad sector is detected, CHKDSK will automatically mark it as bad and the system will refrain from writing further data into that sector. The bad sectors will then be remapped with working ones on the disk. Due to the intensive nature of the scan, surface scan mode typically takes very long time to perform. Time range can stretch from a few hours to a few days.
Click Start
It must be pointed out here that one must use CHKDSK with extreme care because if the disk is failing imminently, such operation may stress the disk to a point of complete failure. Put it ironically, if you have a good working disk, try it. If you think your disk is failing imminently, , refrain from using CHKDSK.