Bad Block Management: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 122: | Line 122: | ||
<p>Bad Block management(BB) as the name suggests is responsible for handle bad blocks within the chip by using error detecting code(ECC) which is stored in a pages spare area.(link it)</br> | <p>Bad Block management(BB) as the name suggests is responsible for handle bad blocks within the chip by using error detecting code(ECC) which is stored in a pages spare area.(link it)</br> | ||
If a physical block is detected by the FTL as bad, it is recorded and replaced with a healthy block from the reserved area.(link it)</p> | If a physical block is detected by the FTL as bad, it is recorded and replaced with a healthy block from the reserved area.(link it)</p> | ||
<h1 id="section3">Flow chart of order of operations</h1> | <h1 id="section3">Flow chart of order of operations</h1> | ||
Latest revision as of 16:01, 15 January 2025
Background information
Bad Block management(BB) as the name suggests is responsible for handle bad blocks within the chip by using error detecting code(ECC) which is stored in a pages spare area.(link it)
If a physical block is detected by the FTL as bad, it is recorded and replaced with a healthy block from the reserved area.(link it)
Flow chart of order of operations
Insert a flow chart of steps and actions for each task (create using diagram)
Related Topics
Topics such as desoldering to chip off or firmware dumping for disk PCB repairs
Further reading
External references in wiki references can just be cited through the keyword link
- Reference 1: Source details
- Reference 2: Source details