Thread: Introducing ubiboot N9 (multiboot OS loader)
View Single Post
fejd is offline fejd
2013-12-30 , 21:54
Posts: 12 | Thanked: 5 times | Joined on Dec 2013
#1024
Originally Posted by juiceme View Post
The ubiboot image is very large; about 12M in compressed form, true, that is because it includes the root filesystem of the repair mode in the kernel image.
However I have not ever seen that it would be too big to be flashed to the kernel MTD partition.

Would it be possible that your kernel partition is smaller than on other devices? I believe that even on MTD there is some flash filesystem that removes damaged flash blocks from use, maybe your kernel partition has been reduced in size?
How do I verify the size of the kernel partition? I've run sfdisk and it shows me:

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 16 1632511 1632496 52239872 c W95 FAT32 (LBA)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)
/dev/mmcblk0p2 1760512 1891583 131072 4194304 83 Linux
/dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux
/dev/mmcblk0p4 1632512 1760511 128000 4096000 83 Linux
start: (c,h,s) expected (1023,3,16) found (1023,63,32)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)

This is right after flashing MOSLO and trying to flash ubiboot. If the flash is damaged, would it help to run a disk check and mark the sectors, then flash again?

p.s. Is there any way to format the output to make it more readable? d.s.
Last edited by fejd; 2013-12-30 at 21:57.