Ricard Bou 
Hi, I am trying to copy NAND contents from a mini2440 to another using supervivi. I create the backup file, and when I try to restore it supervivi detects several bad blocks in the NAND, and my software doesn't work. I bought another mini2440, I repeated the process, the bad blocks were different, but the problem is exactly in the same point: when linux kernel is booting, before login, it has some problem detecting/mounting the ubifs partition I created. I formatted md3 partition with ubifs to improve filesystem stability on brown-out-resets. Have you got any clue about what is going on there? Does the backup-restore process only support yaffs? How can the root partition "extend the end of the device"? Thank you in advance! Some additional pieces of info: logs ------------------------------------ S3C24XX NAND Driver, (c) 2004 Simtec Electronics s3c24xx-nand s3c2440-nand: Tacls=3, 29ns Twrph0=7 69ns, Twrph1=3 29ns s3c24xx-nand s3c2440-nand: NAND soft ECC NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 872 at 0x000006d00000 Bad eraseblock 999 at 0x000007ce0000 Bad eraseblock 1440 at 0x00000b400000 Bad eraseblock 1525 at 0x00000bea0000 Bad eraseblock 1636 at 0x00000cc80000 Bad eraseblock 1663 at 0x00000cfe0000 Creating 5 MTD partitions on "NAND 256MiB 3,3V 8-bit": 0x000000000000-0x000000040000 : "supervivi" 0x000000040000-0x000000060000 : "param" 0x000000060000-0x000000560000 : "Kernel" 0x000000560000-0x000040560000 : "root" mtd: partition "root" extends beyond the end of device "NAND 256MiB 3,3V 8-bit" -- size tr0 0x000000000000-0x000040000000 : "nand" mtd: partition "nand" extends beyond the end of device "NAND 256MiB 3,3V 8-bit" -- size tr0 UBI: attaching mtd3 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI error: ubi_read_volume_table: the layout volume was not found UBI error: ubi_init: cannot attach mtd3 UBI error: ubi_init: UBI error: cannot initialize UBI, error -22 ... UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19 VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: 1f00 256 mtdblock0 (driver?) 1f01 128 mtdblock1 (driver?) 1f02 5120 mtdblock2 (driver?) 1f03 256640 mtdblock3 (driver?) 1f04 262144 mtdblock4 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Backtrace: [<c003528c>] (dump_backtrace+0x0/0x108) from [<c039a6e0>] (dump_stack+0x18/0x1c) r6:c04f10b0 r5:c3812000 r4:c3823f60 [<c039a6c8>] (dump_stack+0x0/0x1c) from [<c039a724>] (panic+0x40/0x134) [<c039a6e4>] (panic+0x0/0x134) from [<c0008eb0>] (mount_block_root+0x17c/0x240) r3:c3823ec4 r2:c383f0ec r1:c3823f60 r0:c04555d0 [<c0008d34>] (mount_block_root+0x0/0x240) from [<c00090e8>] (prepare_namespace+0x80/0x19c) [<c0009068>] (prepare_namespace+0x0/0x19c) from [<c00084c0>] (kernel_init+0xf0/0x124) r6:c00201dc r5:c0020678 r4:c0020678 [<c00083d0>] (kernel_init+0x0/0x124) from [<c004e120>] (do_exit+0x0/0x628) r6:00000000 r5:00000000 r4:00000000