Persistent journald logs

oh yes, sure, let me put this a bit more into context… Actually I posted the issue I have in the following post, there you will see my file system. EmonPi crashes running OS on SSD - #8 by luisrodriguez7
I boot from the SD and then I have the operating system on the SSD. I have applied your proceudre in order to have persistent logs, so journals are stored in /home/pi/data/journald.logs
Here is my fstab:

pi@emonpi:~$ cat /etc/fstab
tmpfs           /tmp             tmpfs   nodev,nosuid,size=30M,mode=1777 0  0
tmpfs           /var/tmp         tmpfs   nodev,nosuid,size=1M,mode=1777  0  0
tmpfs           /var/log         tmpfs   nodev,nosuid,size=50M,mode=1777 0  0
tmpfs           /var/lib/dhcp    tmpfs   nodev,nosuid,size=1M,mode=1777  0  0
tmpfs           /var/lib/dhcpcd5 tmpfs   nodev,nosuid,size=1M,mode=1777  0  0
tmpfs           /var/lib/openhab tmpfs   nodev,nosuid,size=40M,mode=1777 0  0
#tmpfs           /var/lib/php/sessions    tmpfs nodev,nosuid,nofail,size=5M,mode=1777 0 0
proc            /proc            proc    defaults                        0  0
/dev/mmcblk0p1  /boot            vfat    defaults,noatime,nodiratime     0  2
/dev/disk/by-uuid/efbcb440-6661-4186-89cf-b7100fdddbbd /                ext4    defaults,ro,noatime,nodiratime,errors=remount-ro 0 1
/dev/disk/by-uuid/049fe126-0443-4393-98c5-40a043739bb8 /mnt             ext4    defaults,ro,noatime,nodiratime,errors=remount-ro 0 1
/dev/mmcblk0p3  /home/pi/data    ext2    defaults,rw,noatime,nodiratime,errors=remount-ro 0 2
/home/pi/data/journald.logs /var/log/journal none defaults,bind 0 0