Changes between Version 5 and Version 6 of SamsungF4EGBadBlocks


Ignore:
Timestamp:
Nov 30, 2010, 8:57:30 PM (9 years ago)
Author:
Christian Franke
Comment:

Clarify that the bug does not produce bad blocks

Legend:

Unmodified
Added
Removed
Modified
  • SamsungF4EGBadBlocks

    v5 v6  
    152152The above suggests that the disk sometimes discards a pending 64 sector write command when a IDENTIFY DEVICE command is received. This data loss occurs silently. There is no error message in kernel log, SMART Error log, NCQ Command Error log page, or SATA Phy Event Counters log page.
    153153
     154Please note that the {{{badblocks}}} command reported "{{{256 bad blocks}}}" in the above test because the data read differs from the data written before. None of the tests resulted in actual bad (unreadable) blocks on the disk. Testing did not damage the disk itself. The problem is that new data already sent to the disk may not be written. Previously written data is not affected.
     155
    154156The problem could '''not''' be reproduced with the above test if any of the following conditions are met:
    155157