With /usr on another partition on ltsp-server ltsp pxer client can't boot.

[yopla]

ltsp-build-client on xenial

Here is my /etc/fstab on the server

UUID=a4f0879e-4d14-4efd-b8c7-d2dd53a6895e / ext4 errors=remount-ro 0 1

UUID=6f22021d-867a-43b9-aca1-e8bdb2413a0d /usr ext4 rw 0 1

# swap was on /dev/sda5 during installation
UUID=567b3f5a-0952-468d-bae7-d80876ad6728 none swap sw 0 0

ltsp-update-image --cleanup / has the same file in generated i386.img

pxe client won't boot anymore. http://pasteboard.co/K3ks97pv4.jpg

workaround :
temprorary comment /usr entry is /etc/fstab before ltsp-update-image

[Alkis Georgopoulos (alkisg)]

Fix committed in https://git.launchpad.net/ltsp/commit/?id=6db709c8df69132465b7704c20b1fb3c7f182141.

The problem was that /usr/share/initramfs-tools/init has the following code:
> if read_fstab_entry /usr; then
> log_begin_msg "Mounting /usr file system"
> mountfs /usr
> log_end_msg
> fi

I.e. it checks ${rootmnt}/etc/fstab, and if it contains a /usr partition, it tries to mount it before the init-ltsp.d/50-fstab script has a chance to create a clean fstab.

One solution would be to add /etc/fstab to ltsp-update-image.excludes, but since we support CONFIGURE_FSTAB in lts.conf, someone might actually want to include his $CHROOT/etc/fstab in the generated image.
So removing it from cleanup.d/50-fstab sounded like a better idea.

[Vagrant Cascadian (vagrantc)]

fixed in 5.5.10