文件系统烧写出现奇怪错误 NAND出现坏区

最近在学习移植这一块，但是出现了不少的问题
我将u-boot,zImage移植入开发板能正常运行，但是将文件系统erase之后重新烧写时出现了奇怪的错误，于是我选择了9-1的命令，将NAND彻底的格式化了，本想会正常，可是问题越来越多了，GOOGLE了一下，好像分区出现了问题，具体错误如下（所烧写的镜像均是开发板光盘中自带的）：
1.格式化后烧写kernel镜像之后，按8重启系统之后串口打印的不正常的消息为：
Freeing init memory: 180K
Warning: unable to open an initial console.
Failed to execute /linuxrc.  Attempting defaults...
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
Backtrace:
[<c0039fd4>] (dump_backtrace+0x0/0x10c) from [<c02b17f8>] (dump_stack+0x18/0x1c)
r7:00000000 r6:c03bdf40 r5:c03bd900 r4:c0396248
[<c02b17e0>] (dump_stack+0x0/0x1c) from [<c02b1848>] (panic+0x4c/0x124)
[<c02b17fc>] (panic+0x0/0x124) from [<c00354f0>] (init_post+0xec/0x178)
r3:00000000 r2:c385ee00 r1:c03f1000 r0:c033f2dc
[<c0035404>] (init_post+0x0/0x178) from [<c000847c>] (kernel_init+0xcc/0xf4)
r5:c001d670 r4:c001d9d4
[<c00083b0>] (kernel_init+0x0/0xf4) from [<c004af30>] (do_exit+0x0/0x620)
r7:00000000 r6:00000000 r5:00000000 r4:00000000
之后就是进入NOR 的U-BOOT中

2.格式化后烧写完kernel之后，开始烧写rootfs（rootfs大小为60.4M），串口打印出如下错误消息：
Advanced Linux Sound Architecture Driver Version 1.0.18a.
No device for DAI UDA134X
No device for DAI s3c24xx-i2s
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: UDA134X <-> s3c24xx-i2s mapping ok
ALSA device list:
  #0: S3C24XX_UDA134X (UDA134X)
TCP cubic registered
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
lib80211: common routines for IEEE802.11 drivers
s3c2410-rtc s3c2410-rtc: setting system clock to 2008-11-08 09:34:13 UTC (1226136853)
end_request: I/O error, dev mtdblock2, sector 0
FAT: unable to read boot sector
VFS: Cannot open root device "mtdblock2" or unknown-block(31,2)
Please append a correct "root=" boot option; here are the available partitions:
1f00             256 mtdblock0 (driver?)
1f01            2048 mtdblock1 (driver?)
1f02          257536 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
Backtrace:
[<c0039fd4>] (dump_backtrace+0x0/0x10c) from [<c02b17f8>] (dump_stack+0x18/0x1c)
r7:c380a0cb r6:c03bdf40 r5:c380a000 r4:c381df40
[<c02b17e0>] (dump_stack+0x0/0x1c) from [<c02b1848>] (panic+0x4c/0x124)
[<c02b17fc>] (panic+0x0/0x124) from [<c0008e30>] (mount_block_root+0x178/0x234)
r3:00000000 r2:c385532c r1:c381df40 r0:c033f578
[<c0008cb8>] (mount_block_root+0x0/0x234) from [<c0008f9c>] (mount_root+0xb0/0xf4)
[<c0008eec>] (mount_root+0x0/0xf4) from [<c00090d8>] (prepare_namespace+0xf8/0x18c)
r7:c03bd924 r6:c001e83c r5:c001e83c r4:c001e84c
[<c0008fe0>] (prepare_namespace+0x0/0x18c) from [<c0008478>] (kernel_init+0xc8/0xf4)
r7:00000000 r6:c001d9d4 r5:c001d670 r4:c001d9d4
[<c00083b0>] (kernel_init+0x0/0xf4) from [<c004af30>] (do_exit+0x0/0x620)
r7:00000000 r6:00000000 r5:00000000 r4:00000000

请问出现这样的问题的原因时什么了，我该如何解决
谢谢！

哈哈，问题解决了，下载完rootfs之后，用nand write.yaffs 0x30000000 root $(filesize)命令，而不是用nand write.jffs2...之类的命令

你要不说你是在uboot命令行使用命令来烧写的，别人是很难能给你分析出来是导致这个原因的。