hi, could somebody explain what this error for ?
i got this error on surface test and it,s currently testing a bad block and gives this error
error: 23 (cyclic redandancy check)
-
hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: error: 23 (cyclic redandancy check)
Hi,
It means that the sector(s) are damaged and they can't reliable store data, usually reported in read surface tests.
You may perform Disk -> Surface test -> "Reinitialise disk surface" which forces the drive to verify the integrity of those sectors, reallocate them if required (which mean the internal bad sector counter increases but the drive may work more reliable as then a spare area will be used instead of the original location).
It means that the sector(s) are damaged and they can't reliable store data, usually reported in read surface tests.
You may perform Disk -> Surface test -> "Reinitialise disk surface" which forces the drive to verify the integrity of those sectors, reallocate them if required (which mean the internal bad sector counter increases but the drive may work more reliable as then a spare area will be used instead of the original location).
Re: error: 23 (cyclic redandancy check)
thanks for reply but i got this error while the test is bieng in progress in Surface test -> "Reinitialise disk surface" mode , so is this mean that if that couldn,t repair will it still be able to result in succesful test ? or that mean i should not let it run anymore?
-
hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: error: 23 (cyclic redandancy check)
In theory, any simple write operation targeting the affected sector should cause the drive to re-examine the status of the sector and re-allocate it if required.
However, in most cases, this does not happen for the first time. This is why the "reinitialise disk surface" test uses special patterns (more passes) to force the drive to perform reallocation more quickly.
In some situations, even this is not enough. Then the following may help:
- running the test again (as you described)
- just before starting the test, select the "Configuration" page in the test preparation window and select to repeat the test (maybe with the option to process the specific blocks only instead of processing the complete surface)
- before starting the test, increase the "Surface reinitialisation level" in the same window.
These may all perform more overwrite passes as it is possible that (finally) the status of the sector is fixed.
If this does not happen even (even after many such passes) it may mean that the spare area is also damaged or full.
It would be nice to check the complete status of the drive so if possible, please use Report -> Send test report to developer option. Thanks!
However, in most cases, this does not happen for the first time. This is why the "reinitialise disk surface" test uses special patterns (more passes) to force the drive to perform reallocation more quickly.
In some situations, even this is not enough. Then the following may help:
- running the test again (as you described)
- just before starting the test, select the "Configuration" page in the test preparation window and select to repeat the test (maybe with the option to process the specific blocks only instead of processing the complete surface)
- before starting the test, increase the "Surface reinitialisation level" in the same window.
These may all perform more overwrite passes as it is possible that (finally) the status of the sector is fixed.
If this does not happen even (even after many such passes) it may mean that the spare area is also damaged or full.
It would be nice to check the complete status of the drive so if possible, please use Report -> Send test report to developer option. Thanks!