[yocto] wic adds wrong mount lines to my fstab
Ed Bartosh
ed.bartosh at linux.intel.com
Wed Feb 10 02:19:13 PST 2016
Hi Oliver,
On Tue, Feb 09, 2016 at 09:29:16AM +0100, Oliver Graute wrote:
> # It uses SPL and u-boot
> #
> # The disk layout used is:
> # - ----- --------- ---------- -------- --------- ---------- ------------
> # | | SPL | u-boot | /boot1 | /boot2 | rootfs1 | rootfs2 | data |
> # - ----- --------- ---------- -------- --------- ---------- ------------
> # ^ ^ ^ ^ ^ ^
> # | | | | | |
> # 0 1kiB 69kiB 4MiB 4MiB + 20MiB 4MiB + 8Mib + rootfs1 + rootfs2 + data
> #
> part SPL --source rawcopy --sourceparams="file=SPL" --ondisk mmcblk --no-table --align 1
> part u-boot --source rawcopy --sourceparams="file=u-boot.img" --ondisk mmcblk --no-table --align 69
> part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label boot --active --align 4096 --size 20M --extra-space 0
> #part /boot2 --source bootimg-partition --ondisk mmcblk --fstype=vfat --label boot2 --active --align 4096 --size 8M --extra-space 0
> part / --source rootfs --ondisk mmcblk --fstype=ext3 --label root --align 4 --size 125
> part /rescue --source rootfs --ondisk mmcblk --fstype=ext3 --label secondary --align 4 --size 125
> part /data --ondisk mmcblk --fstype=ext3 --label data --align 4 --size 730
>
> Some sugesstions to fix this?
How exactly wic complains if you use --ondisk mmcblk0 ?
It worked for me with this .wks:
part /boot --source bootimg-pcbios --ondisk mmcblk0 --label boot --active --align 1024
part / --source rootfs --ondisk mmcblk0 --fstype=ext3 --label root --align 1024
part /rescue --source rootfs --ondisk mmcblk0 --fstype=ext3 --label secondary --align 4 --size 125
part /data --ondisk mmcblk0 --fstype=ext3 --label data --align 4 --size 730
bootloader --timeout=0 --append="rootwait rootfstype=ext3 console=tty0"
and produced these 2 lines in fstab:
/dev/mmcblk0p3 /rescue ext3 defaults 0 0
/dev/mmcblk0p5 /data ext3 defaults 0 0
If you provide more info about your setup(layers used?) I can try to
reproduce it and fix the issue.
Creating bug in https://bugzilla.yoctoproject.org would be great too.
--
Regards,
Ed
More information about the yocto
mailing list