------- Comment From <email address hidden> 2020-05-06 09:26 EDT-------
Just gave it a try - did a FTP load using the default .ins file in the ISO.
The only message that shows up at first indeed is
ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or directory
Then there's no output for about 06:20 and then there's this:
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) [6n
Unable to find a medium containing a live file system
So yeah - if one waits long enough, there will be a hint that something went wrong. However that's still not a great out-of-box experience for customers who are used to this exact same method just working ever since 16.04.
While the error message is technically correct, without additional documentation the user will still not know how to get things working from there.
------- Comment From <email address hidden> 2020-05-06 09:26 EDT-------
Just gave it a try - did a FTP load using the default .ins file in the ISO.
The only message that shows up at first indeed is fail-hooks. d//scripts/ init-premount/ lvm2: No such file or directory
ln: /tmp/mountroot-
Then there's no output for about 06:20 and then there's this:
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) [6n
Unable to find a medium containing a live file system
So yeah - if one waits long enough, there will be a hint that something went wrong. However that's still not a great out-of-box experience for customers who are used to this exact same method just working ever since 16.04.
While the error message is technically correct, without additional documentation the user will still not know how to get things working from there.