Image created with ext4 root volume will not boot

[James Tunnicliffe]

I have tried creating an ext4 based image using:

./linaro-media-create --mmc /dev/mmcblk0 --dev panda --rootfs ext4 --hwpack ~/.cache/linaro/image-tools/fetch_image/snapshots.linaro.org/11.05-daily/linaro-hwpacks/panda/20110804/0/images/hwpack/hwpack_linaro-panda_20110804-0_armel_supported.tar.gz --binary ~/.cache/linaro/image-tools/fetch_image/snapshots.linaro.org/11.05-daily/linaro-nano/20110804/0/images/tar/nano-n-tar-20110804-0.tar.gz

The file paths are mirrors of where the files were downloaded from.

During boot, this happens:

Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
mount: mounting /dev/disk/by-uuid/d94a9ee0-7fca-4b87-81a5-c0057ffe3c71 on /root failed: No such device

The same board and SD card boot fine using ext3 and btrfs.

[James Westby (james-w)]

On Fri, 05 Aug 2011 13:52:05 -0000, James Tunnicliffe <email address hidden> wrote:
> Public bug reported:
>
> I have tried creating an ext4 based image using:
>
> ./linaro-media-create --mmc /dev/mmcblk0 --dev panda --rootfs ext4
> --hwpack ~/.cache/linaro/image-
> tools/fetch_image/snapshots.linaro.org/11.05-daily/linaro-
> hwpacks/panda/20110804/0/images/hwpack/hwpack_linaro-
> panda_20110804-0_armel_supported.tar.gz --binary ~/.cache/linaro/image-
> tools/fetch_image/snapshots.linaro.org/11.05-daily/linaro-
> nano/20110804/0/images/tar/nano-n-tar-20110804-0.tar.gz
>
> The file paths are mirrors of where the files were downloaded from.
>
> During boot, this happens:
>
> Begin: Loading essential drivers ... done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
> Begin: Running /scripts/local-premount ... done.
> mount: mounting /dev/disk/by-uuid/d94a9ee0-7fca-4b87-81a5-c0057ffe3c71 on /root failed: No such device

Perhaps this UUID doesn't match the UUID of the root fs on the SD card?

Would you check what the UUID of the fs really is? I'm not sure how to
do that though.

Thanks,

James

[Loïc Minier (lool)]

Could you check whether your kernel is configured with ext4? (/boot/config* file in the root partition of your SD card)

I've noticed this is missing in some of our configs since some weeks

[Loïc Minier (lool)]

e.g. bug #817148

[James Tunnicliffe (dooferlad)]

The UUID does match that of the root file system. I can't find any information relating to the kernel config on the burned image or in a quick look around the hardware pack, but that may be because I am looking in the wrong place. It would seem that bug #817148 is the problem.