Hello, On Fri, May 12, 2017 at 2:35 PM, Felix Fietkau <n...@nbd.name> wrote: > On 2017-05-12 12:47, Edwin van Drunen wrote: >> Hello Sergey, >> >> When using sysupgrade on an RB912 running a full LEDE 17.01.1 to install a >> custom image made with the image builder, the kernel is installed just fine. >> Before and after the sysupgrade I booted OpenWRT so I could mount the YAFFS >> kernel partition and could verify that the kernel was updated and other >> files on the partition were removed (as a test I added a text file before). >> This shows that a partition image is successfully written to mtd5 when >> executing sysupgrade from a fully installed LEDE. >> >> So it seems to only be a problem when running sysupgrade from an initramfs >> image, which would be the way to go for a fresh install. >> I used the following initramfs image: >> https://downloads.lede-project.org/releases/17.01.1/targets/ar71xx/mikrotik/lede-17.01.1-ar71xx-mikrotik-vmlinux-initramfs.elf >> >> Is there something missing in the default initramfs image? >> Because I have no serial console and the ssh session is broken immediately >> after starting the sysupgrade, I also cannot see any error messages. > Hi Edwin, > > Based on the information you provided, I just found out that nand-utils > is missing in the initramfs image. I've just pushed a fix to master and > the 17.01 branch, so the next build should take care of this issue. > > https://git.lede-project.org/c536c50171 >
Wow, good catch! Seem like that this is the real root cause of issue. I completely missed the fact that initramfs could be built without using of the nand-utils package, since I always use custom build images. -- Sergey _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev