| Message ID | 20250305-initramfs-crypt-hook-patches-2-v4-1-4170912e5261@denx.de (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | initramfs-crypt-hook patch | expand |
On 05.03.25 13:00, Claudius Heine wrote: > Wherever or not the mount directory (and their parents) gets created > seem to be inconsistent; mentioning a missing mount point in the > `/etc/fstab` might cause the boot to fail, while using systemd `.mount` > units will just create the mount point. > > Wic creates missing mount points that where mentioned in the `.wks` > file; so moving from such a setup to letting `initramfs-crypt-hook` > mount the file system at boot inside the ramdisk, the mount would > suddenly fail. > > Therefore creating the mount point for your, if it doesn't exists seem to > provide a smoother transition. > > Signed-off-by: Claudius Heine <ch@denx.de> > --- > recipes-initramfs/initramfs-crypt-hook/files/local-bottom-complete | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/recipes-initramfs/initramfs-crypt-hook/files/local-bottom-complete b/recipes-initramfs/initramfs-crypt-hook/files/local-bottom-complete > index b991cb49fbdfdc4b2ffc81c1424fb3c695a973cd..80553d1cd8ccde7a6cc9b324c6e5faba8d8f3579 100644 > --- a/recipes-initramfs/initramfs-crypt-hook/files/local-bottom-complete > +++ b/recipes-initramfs/initramfs-crypt-hook/files/local-bottom-complete > @@ -41,6 +41,7 @@ mount_partition() { > partition_mountpoint=$2 > [ "$debug" = "y" ] && echo "mount device: '$partition_dev_path' to '$partition_mountpoint'" > if ! mountpoint -q "${partition_mountpoint}"; then > + mkdir -p "${partition_mountpoint}" > if ! mount -t "$(get_fstype "${partition_dev_path}")" "${partition_dev_path}" \ > "${partition_mountpoint}"; then > panic "Can't mount partition '${partition_dev_path}'!" > Merging this one already. Thanks, Jan
diff --git a/recipes-initramfs/initramfs-crypt-hook/files/local-bottom-complete b/recipes-initramfs/initramfs-crypt-hook/files/local-bottom-complete index b991cb49fbdfdc4b2ffc81c1424fb3c695a973cd..80553d1cd8ccde7a6cc9b324c6e5faba8d8f3579 100644 --- a/recipes-initramfs/initramfs-crypt-hook/files/local-bottom-complete +++ b/recipes-initramfs/initramfs-crypt-hook/files/local-bottom-complete @@ -41,6 +41,7 @@ mount_partition() { partition_mountpoint=$2 [ "$debug" = "y" ] && echo "mount device: '$partition_dev_path' to '$partition_mountpoint'" if ! mountpoint -q "${partition_mountpoint}"; then + mkdir -p "${partition_mountpoint}" if ! mount -t "$(get_fstype "${partition_dev_path}")" "${partition_dev_path}" \ "${partition_mountpoint}"; then panic "Can't mount partition '${partition_dev_path}'!"
Wherever or not the mount directory (and their parents) gets created seem to be inconsistent; mentioning a missing mount point in the `/etc/fstab` might cause the boot to fail, while using systemd `.mount` units will just create the mount point. Wic creates missing mount points that where mentioned in the `.wks` file; so moving from such a setup to letting `initramfs-crypt-hook` mount the file system at boot inside the ramdisk, the mount would suddenly fail. Therefore creating the mount point for your, if it doesn't exists seem to provide a smoother transition. Signed-off-by: Claudius Heine <ch@denx.de> --- recipes-initramfs/initramfs-crypt-hook/files/local-bottom-complete | 1 + 1 file changed, 1 insertion(+)