From the mkfs.ext4 man page: lazy_itable_init[= <0 to disable, 1 to enable>] If enabled and the uninit_bg feature is enabled, the inode table will not be fully initialized by mke2fs. This speeds up file system initialization notice- ably, but it requires the kernel to finisby mlitke - Debian
I always run sync too, but I don't think that "finalizes" the file system. The bit of research I did after last posting leads me to believe the finalizing is forcing the ext4 file system to finish creating the inode table. I think the default when creating a new ext4 file system is to create part of the inode table, and then after the system boots, it will finish creating the tableby mlitke - Debian
Did you try formatting to ext3? If I remember correctly, I tried ext4 and it did not work for me. I also just found this in bodhi's install thread: QuoteIf you are running the latest U-Boot for Kirkwood then you can use Ext4. But be aware that Ext4 file system format needs to be "finalized" before it can be used for booting. Did you finalize the file system (I am not quite suby mlitke - Debian
I found them in your u-boot post. :) Looks like they are: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) So: - the order is a little different (and shouldn't matter) - rootdelay=10 is used instead of rootwait (which in most cases will result in the same behavior) - root is mounted read/write (I would have to look uby mlitke - Debian
bodhi, Do you know what default the kernel args are for Debian (cat /proc/cmdline)? It appears the Arch Linux ARM ones are working okay, but I am curious if there are any differences. The kernel args when booting Debian from the Arch Linux ARM U-Boot with the updates I outlined in the above procedure are: console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),-(rootfs) root=LABEL=rootfs rwby mlitke - Debian
bodhi, First off, thanks for all the work and time you have put into this! I have been running Arch Linux ARM for years and was sad to see it EOL for these devices, but really glad to see the Debian support continue. I have a little bit of an alternative to your instructions/approach to migrate from Arch. I have tested the steps below on both a Dockstar and a GoFlex Home with success bootinby mlitke - Debian