[OE-core] wic wks: data partition only mounted on second boot?
Matthijs Vader
mvader at victronenergy.com
Mon May 23 08:58:10 UTC 2016
Hi,
I have my wks file like this:
part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 4 --size 16
part / --source rootfs --ondisk mmcblk0 --fstype=ext4 --label root --align 4
part /data --ondisk mmcblk0 --size 100M --fstype=ext4 --label data --align 4
It creates the /data partition, and adds it to the .wic file, all fine. But on
the first boot it is not auto-mounted. From the boot log:
[ 1.898069] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 1.906798] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 1.919446] devtmpfs: mounted
[ 1.923113] Freeing unused kernel memory: 264K (c069e000 - c06e0000)
version 2.88 booting
Starting udev
[ 2.535288] udevd[657]: starting version 182
And some extra info:
root at beaglebone:~# mount
/dev/root on / type ext4 (rw,relatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=243816k,nr_inodes=60954,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/volatile type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
root at beaglebone:~# cat /etc/fstab
# stock fstab - you probably want to override this with a machine specific one
/dev/root / auto defaults 1 1
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
tmpfs /run tmpfs mode=0755,nodev,nosuid,strictatime 0 0
tmpfs /var/volatile tmpfs defaults 0 0
/dev/mmcblk0p3 /data ext4 defaults 0 0
Now, if I just reboot the device, the extra image is mounted during startup:
[ 1.897948] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 1.906674] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 1.919137] devtmpfs: mounted
[ 1.922811] Freeing unused kernel memory: 264K (c069e000 - c06e0000)
version 2.88 booting
[ 2.925735] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
Starting udev
udev: Not using udev cache because of changes detected in the following files:
udev: /proc/version /proc/cmdline /proc/devices
udev: lib/udev/rules.d/* etc/udev/rules.d/*
udev: The udev cache will be regenerated. To identify the detected changes,
udev: compare the cached sysconf at /etc/udev/cache.data
udev: against the current sysconf at /dev/shm/udev.cache
[ 3.193848] udevd[664]: starting version 182
And also mount shows it mounted:
root at beaglebone:~# mount
/dev/root on / type ext4 (rw,relatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=243816k,nr_inodes=60954,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/volatile type tmpfs (rw,relatime)
/dev/mmcblk0p3 on /data type ext4 (rw,relatime,data=ordered)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
Any ideas how to make it boot during the first boot as well?
Thanks, Matthijs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160523/ce79c82d/attachment-0002.html>
More information about the Openembedded-core
mailing list