I installed Debian Jessie on a ReadyNas102 that has a bad block, like so:
,
| NAND: (ID 0xf1ad) 128 MiB
| MMC: MRVL_MMC: 0
| Bad block table found at page 65472, version 0x01
| Bad block table found at page 65408, version 0x01
| nand_read_bbt: Bad block at 0x0024
`
Where
Package: flash-kernel
Version: 3.35+deb8u2
Severity: critical
Justification: causes serious data loss
Control: block 806926 with -1
Hello,
when flash-kernel writes a kernel/initrd to NAND flash it uses plain
write(2) to /dev/mtdX (flash-kernel < 3.52) or flashcp
(flash-kernel >= 3.52). If the
Control: reassign -1 mtd-utils
So far I see no evidence for the claim that flashcp should not be used
for writing to NAND devices in either its --help or its source (it has
no man page AFAICS).
Having a tool in Debian called "flashcp" which can (according to this
report, I haven't checked this
Processing control commands:
> reassign -1 mtd-utils
Bug #813995 [flash-kernel] flash-kernel: writes to nand without being aware of
bad blocks
Bug reassigned from package 'flash-kernel' to 'mtd-utils'.
No longer marked as found in versions flash-kernel/3.35+deb8u2.
Ignoring request to alter
4 matches
Mail list logo
