Bad Block Management: Difference between revisions

From datarecoverywiki.com
Jump to navigation Jump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 112: Line 112:
     <h2>Contents <a href="javascript:void(0);" class="hide-link" onclick="toggleTOC()">[hide]</a></h2>
     <h2>Contents <a href="javascript:void(0);" class="hide-link" onclick="toggleTOC()">[hide]</a></h2>
     <ul>
     <ul>
        <li><a href="#section0">What tools you will need</a>
         <li><a href="#section1"> background information</a></li>
            <ul>
                <li><a href="#required">Required</a></li>
                <li><a href="#optional">Optional but useful</a></li>
            </ul>
        </li>
         <li><a href="#section1"> Uses of this skill</a></li>
        <li><a href="#section2"> Step-by-step guide with images</a></li>
         <li><a href="#section3"> Flow chart of order of operations</a></li>
         <li><a href="#section3"> Flow chart of order of operations</a></li>
        <li><a href="#section4"> Troubleshooting/tips and tricks</a></li>
         <li><a href="#section5"> Related Topics</a></li>
         <li><a href="#section5"> Related Topics</a></li>
         <li><a href="#section6"> Further reading</a></li>
         <li><a href="#section6"> Further reading</a></li>
Line 127: Line 119:
</div>
</div>
<!-- background information -->
<!-- background information -->
<h1> Background information </h1>
<h1 id="section1"> Background information </h1>
<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="section0">What tools you will need</h1>
<i> Items are not listed in any particular order </i>
<div class="infobox">
    <table>
        <tr></tr>
        <tr>
            <h3 id="required">Required</h3>
            <ul>
                <li>Test</li>
            </ul>
        </tr>
        <tr>
          <h3 id="optional">Optional but useful</h3>
            <ul>
                <li>Test</li>
            </ul>
        </tr>
    </table>
</div>
<h1 id="section1">Uses of this skill</h1>
<ul>
<li>1.test</li>
<li>2.test</li>
<li>3.test</li>
<h1 id="section2">Step-by-step guide with images</h1>
<p>Insert step-by-step walkthrough with images and summary text here</p>


<h1 id="section3">Flow chart of order of operations</h1>
<h1 id="section3">Flow chart of order of operations</h1>
<p>Insert a flow chart of steps and actions for each task (create using diagram)</p>
<p>Insert a flow chart of steps and actions for each task (create using diagram)</p>
<h1 id="section4">Troubleshooting/tips and tricks</h1>
<p>Fixes to any common issues that were encountered or could be easily encountered</p>


<h1 id="section5">Related Topics</h1>
<h1 id="section5">Related Topics</h1>

Latest revision as of 16:01, 15 January 2025

Data Recovery Resources

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

  1. Reference 1: Source details
  2. Reference 2: Source details