[elbe-devel] initrd lacks e2fsck
Mark Ruys
mark.ruys at sensoterra.com
Sat Apr 23 20:37:01 CEST 2016
> Op 22 apr. 2016, om 22:07 heeft Mark Ruys <mark.ruys at sensoterra.com> het volgende geschreven:
>
> Hi,
>
> We're using ELBE 1.0 to generate a rootfs. The problem is that the /boot/initrd lacks some tools like fsck.ext4, so when I boot the rootfs, I get messages like:
>
> Begin: Checking root file system ... fsck from util-linux 2.25.2
> fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p1
> fsck exited with status code 8
> done.
> Warning: File system check failed but did not detect errors
>
> Now I don't now where initrd is generated, but it is my understanding that this is part of ELBE toolchain. If so, how can I influence the contents of the initrd?
>
> initrd contains:
>
> $ find . -name *fsck* -o -name *ext*
> ./etc/e2fsck.conf
> ./lib/arm-linux-gnueabihf/libext2fs.so.2
> ./sbin/mkfs.ext4
> ./sbin/fsck
>
Okay, I think I solved my problem by adding
<command>update-initramfs -u</command>
to the <finetuning>. No I get a slightly bigger initrd, and it does contain the necessary ext4 programs:
$ find . -name *fsck* -o -name *ext*
./etc/e2fsck.conf
./lib/arm-linux-gnueabihf/libext2fs.so.2
./sbin/mkfs.ext4
./sbin/fsck.ext4
./sbin/e2fsck
./sbin/fsck
Not sure if it's the best way to do it, but it works for me.
Mark
> Thanks,
>
> Mark Ruys
>
> The contents of the boot directory of the rootfs:
>
> -rw-r--r-- 1 markr markr 31445 Jan 27 2015 am335x-dimm-3.14.17-xenomai-emtrion.dtb
> -rw-r--r-- 1 markr markr 31445 Jan 27 2015 am335x-dimm-3.14.29-rt-emtrion.dtb
> -rwxr-xr-x 1 markr markr 1152054 Dec 11 2014 bootlogo.bmp
> -rw-r--r-- 1 markr markr 68658 Jan 28 2015 config-3.2.0+
> -rwxr-xr-x 1 markr markr 17332 Dec 11 2014 emPURS_plat
> lrwxrwxrwx 1 markr markr 17 Apr 22 20:22 initrd -> initrd.img-3.2.0+
> -rw-r--r-- 1 markr markr 2725811 Apr 22 20:22 initrd.img-3.2.0+
> -rw-r--r-- 1 markr markr 1726141 Jan 28 2015 System.map-3.2.0+
> -rwxr-xr-x 1 markr markr 2083 Jan 30 2015 uboot_script
> -rwxr-xr-x 1 markr markr 3309704 Jan 28 2015 vmlinuz-3.2.0+
> lrwxrwxrwx 1 markr markr 14 Apr 22 20:22 zImage -> vmlinuz-3.2.0+
>
> This is our project part:
>
> <project>
> <name>Gateway</name>
> <version>1.0</version>
> <buildtype>armhf</buildtype>
> <mirror>
> <primary_host>ftp.nl.debian.org <http://ftp.nl.debian.org/></primary_host>
> <primary_path>debian</primary_path>
> <primary_proto>http</primary_proto>
> <url-list>
> <url>
> <binary pin="1001">
> http://dimmam335xpkgmgmt:xxxxxx@dimmam335x.pkgs.emtrion.eu/debian/ <http://dimmam335xpkgmgmt:xxxxxx@dimmam335x.pkgs.emtrion.eu/debian/> jessie main contrib non-free
> </binary>
> </url>
> </url-list>
> </mirror>
> <noauth />
> <suite>jessie</suite>
> </project>
>
>
> And part of the pkg-list:
>
> <pkg-list>
> <pkg>linux-image-3.2.0+</pkg>
> <pkg>emboot</pkg>
> <pkg>sysvinit-core</pkg>
> <pkg>dimm-am335x-bsp</pkg>
> <pkg>disable-dhcp</pkg>
> <pkg>disable-fsck</pkg>
> ...
> </pkg-list>
>
>
> From the report:
>
> fileslist
> ---------
>
> |=====================================
> |+/boot/System.map-3.2.0++|linux-image-3.2.0+
> |+/boot/emPURS_plat+|emboot
> |+/boot/bootlogo.bmp+|emboot
> |+/boot/am335x-dimm-3.14.29-rt-emtrion.dtb+|emboot
> |+/boot/initrd+|postinst generated
> |+/boot/vmlinuz-3.2.0++|linux-image-3.2.0+
> |+/boot/am335x-dimm-3.14.17-xenomai-emtrion.dtb+|emboot
> |+/boot/initrd.img-3.2.0++|postinst generated
> |+/boot/uboot_script+|emboot
> |+/boot/config-3.2.0++|linux-image-3.2.0+
> |+/boot/zImage+|postinst generated
>
>
> _______________________________________________
> elbe-devel mailing list
> elbe-devel at linutronix.de
> https://linutronix.de/mailman/listinfo/elbe-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linutronix.de/pipermail/elbe-devel/attachments/20160423/d33ba283/attachment.html>
More information about the elbe-devel
mailing list