XO Flash Bad Blocks: Difference between revisions
(credit to Mitch Bradley for original text) |
No edit summary |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{OLPC}}{{Translations}} |
{{OLPC}}{{Translations}} |
||
This page is how to fix an [[Hardware_specification#Laptop_Hardware|XO laptop]] which is having problems with its main Flash ROM storage. It is part of the [[XO Troubleshooting Guide]]. |
This page is how to fix an [[Hardware_specification#Laptop_Hardware|XO-1 laptop]] which is having problems with its main Flash ROM storage. It is part of the [[XO Troubleshooting Guide]]. |
||
==Problem Description== |
==Problem Description== |
||
The NAND Flash which provides the primary storage for |
The NAND Flash which provides the primary storage for an XO-1 laptop usually has blocks of the chip which don't work. These are identified at the factory (using an extremely sensitive test) and don't change over the life of the device. Occasionally, however, a device develops additional bad storage blocks. If a laptop has had repeated problems where the solution was reinstalling the software, the bad block table may need to be rebuilt. |
||
== |
==Diagnostics== |
||
| ⚫ | |||
Unfortunately the standard mtd_debug tool (from the mtd-utils package) does not provide information about the BBT. You can download an improved mtd_debug from http://dev.laptop.org/~martin/ -- to use |
|||
===Using firmware Q2D16 or earlier=== |
|||
If you are using Open Firmware Q2D16 or earlier, the procedure requires that you type a few lines because of a firmware bug: |
|||
modprobe mtdchar |
|||
ok dev /nandflash |
|||
/path/to/mtd_debug info /dev/mtd0 |
|||
ok : xx dup aa ; |
|||
ok patch xx aa full |
|||
ok dend |
|||
ok test /nandflash::fixbbt |
|||
the output will include 'mtd.badblockscount'. |
|||
===Using firmware Q2D17, Q2E01 or later=== |
|||
If your Open Firmware is newer than Q2D16, just type: |
|||
==Repair== |
|||
| ⚫ | |||
* [[Upgrading_firmware|upgrade to the latest XO-1 firmware]], |
|||
* get to the [[Ok]] prompt, and type: |
|||
ok test /nandflash::fixbbt |
ok test /nandflash::fixbbt |
||
This procedure takes several minutes, because it tests every block on the NAND Flash with several data patterns. The procedure is safe for good NAND Flash, because it saves the previous block data before the test and restores it afterwards, so you won't lose any data on good Flash blocks. There is, however, a small chance of data loss in the event that a block goes bad during (i.e. as a result of) the test, preventing restoration of the previous contents. |
This procedure takes several minutes, because it tests every block on the NAND Flash with several data patterns. The procedure is safe for good NAND Flash, because it saves the previous block data before the test and restores it afterwards, so you won't lose any data on good Flash blocks. There is, however, a small chance of data loss in the event that a block goes bad during (i.e. as a result of) the test, preventing restoration of the previous contents. |
||
==Complete Failure== |
|||
* From http://lists.laptop.org/pipermail/testing/2011-June/002213.html |
|||
<nowiki>Either this NAND is close to complete failure, or else the bad block |
|||
table has become corrupted. |
|||
You could try recreating the bad block table as follows:</nowiki> |
|||
ok select /nandflash scrub! unselect |
|||
==See Also== |
|||
* [[NAND Flash Bad Block Table]] |
|||
[[Category:HowTo]] |
[[Category:HowTo]] |
||
Latest revision as of 05:56, 13 August 2013
This page is how to fix an XO-1 laptop which is having problems with its main Flash ROM storage. It is part of the XO Troubleshooting Guide.
Problem Description
The NAND Flash which provides the primary storage for an XO-1 laptop usually has blocks of the chip which don't work. These are identified at the factory (using an extremely sensitive test) and don't change over the life of the device. Occasionally, however, a device develops additional bad storage blocks. If a laptop has had repeated problems where the solution was reinstalling the software, the bad block table may need to be rebuilt.
Diagnostics
Unfortunately the standard mtd_debug tool (from the mtd-utils package) does not provide information about the BBT. You can download an improved mtd_debug from http://dev.laptop.org/~martin/ -- to use
modprobe mtdchar /path/to/mtd_debug info /dev/mtd0
the output will include 'mtd.badblockscount'.
Repair
You can ask Open Firmware to check the NAND Flash and add newly-bad blocks to the "bad block table" that tells the system not to use them. This requires a developer key for the laptop.
- upgrade to the latest XO-1 firmware,
- get to the Ok prompt, and type:
ok test /nandflash::fixbbt
This procedure takes several minutes, because it tests every block on the NAND Flash with several data patterns. The procedure is safe for good NAND Flash, because it saves the previous block data before the test and restores it afterwards, so you won't lose any data on good Flash blocks. There is, however, a small chance of data loss in the event that a block goes bad during (i.e. as a result of) the test, preventing restoration of the previous contents.
Complete Failure
Either this NAND is close to complete failure, or else the bad block table has become corrupted. You could try recreating the bad block table as follows:
ok select /nandflash scrub! unselect