Odd... The reproduction of To ease interpretive strain, I've taken the liberty of inserting line endings and removing the fragmentary terminal escape sequences which, once upon a time, turned the '[OK]' bits green. Here is /var/log/boot.log here is not the same as the one presented at Lubuntu Fails to Boot after mounting drive. The log here cuts off at line 18 Stopping Mount files.... Apart from that, the first 17 lines of both presentations are identical./var/boot/boot.log, tidied up a bit:
* Starting Mount filesystems on boot [ OK ] * Starting Signal sysvinit that the rootfs is mounted [ OK ] * Starting Populate /dev filesystem [ OK ] * Stopping Populate /dev filesystem [ OK ] * Starting Fix-up /sys/kernel/debug filesystem [ OK ] * Stopping Fix-up /sys/kernel/debug filesystem [ OK ] * Starting Clean /tmp directory [ OK ] * Starting Populate and link to /run filesystem [ OK ] * Stopping Clean /tmp directory [ OK ] * Stopping Populate and link to /run filesystem [ OK ] * Stopping Track if upstart is running in a container [ OK ] * Starting Initialize or finalize resolvconf [ OK ] * Starting Signal sysvinit that virtual filesystems are mounted [ OK ] * Starting Signal sysvinit that virtual filesystems are mounted [ OK ] * Starting Bridge udev events into upstart [ OK ] * Starting Signal sysvinit that local filesystems are mounted [ OK ] * Starting Signal sysvinit that remote filesystems are mounted [ OK ] * Stopping Mount filesâ€
Now, using <pre> markup, it becomes apparent that line eighteen of the version of /var/log/boot.log given here includes a spurt of random bytes as the logger went off the rails.
However, the version of /var/log/boot.log presented over at the other post runs on for a further 48 lines of reporting, announcing such matters as SystemD stopping "Send an event to indicate plymouth is up." Well, plymouth is the login manager, and the login manager appears multiple seconds after the kernel boot, when user space is well nigh complete.
Dear @Infinatum, I very much fear that you will enlist but little assistance with a post entitled "Lubuntu Fails To Boot after mounting drive" when the primary evidence of "boot failure" is a log that very much shows a nearly -- if not wholly -- complete system start up (including the mounting of local drives). I presume the one posted over there was a inadvertent mistake and am sad about the confusion it will elicit.
In light of that, you really should edit the post over there to include this /var/boot/boot.log instead, which actually indicates a catastrophe of some sort.
Now the real question is the nature of the catastrophe, occurring just as SystemD was announcing the completion of the rootfs-local-remote cluster of file system mountings. Be nice to get a dmesg at that point, but maybe the box is freezing in a kernel panic. Does lubuntu allow one to step through SystemD interactively...?
That could be a three pipe problem...
EDIT: This post mostly stricken because I believe @Infinatum has nicely edited out the confusing aspects. I am leaving my copy of his /var/boot/boot.log that was originally posted by him here because it shows a point of failure, useful for spelunking the matter.