Skip to contentSkip to conversation

wic adds wrong mount lines to my fstab

DISCUSSION Oliver Graute 2 participants 3 messages Feb 9, 2016 – Feb 10, 2016

lore
Share & tools
lore
#0 lore raw

Hello list,

I am using wic to generate partitioned yocto images. After I boot such an Image, I see two added entrys in my /etc/fstab wich are not correct.

cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>

/dev/root       /                 auto     defaults        1  1
proc            /proc             proc     defaults        0  0
devpts          /dev/pts          devpts   mode=0620,gid=5 0  0
usbdevfs        /proc/bus/usb     usbdevfs noauto          0  0

/dev/mmcblk0p5 /rwfs auto defaults 0 0
#/dev/mmcblk0p3 /rescue ext3 defaults 0 0
/dev/mmcblk0p5 /data ext3 defaults 0 0

tmpfs           /run              tmpfs    mode=0755,nodev,nosuid,strictatime 0  0
tmpfs           /var/volatile     tmpfs    defaults        0  0
tmpfs           /var/cache        tmpfs    defaults        0  0
tmpfs           /var/lib          tmpfs    defaults        0  0
tmpfs           /var/spool        tmpfs    defaults        0  0
tmpfs           /var/apache2/logs tmpfs    defaults        0  0
/dev/mmcblkp3   /rescue ext3    defaults        0       0
/dev/mmcblkp5   /data   ext3    defaults        0       0

the last two lines are added by the wic tool. Here is the 0 missing. If I add these 0 to my wks --ondisk mmcblk option wic is complaining. So I`am just using is like in this wks disk layout:

# short-description: Create SD card image with a boot partition # long-description:
# Create an image that can be written onto a SD card using dd for use

# with i.MX SoC family.
# 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?

Best regards,

Oliver

#1 lore raw

Hi Oliver,

Quoted 18 lines · Oliver Graute

# 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

Quoted 1 line

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

#2 lore raw
Quoted 32 lines · Ed Bartosh

Hi Oliver,

Quoted 18 lines · Oliver Graute

# 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

Quoted 1 line

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"

Quoted 7 lines

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.

Hello Ed,

it is working now with --ondisk mmcblk0. I'am not sure why it didn't worked before. I can't reproduce it anymore. Thx for your help and sorry for the noise.

best regards,

Oliver