This bug is being reported to happen also after a clonezilla based installation for Trusty.
"""
The issue with /tmp will timeout and continue to boot, / will hand the boot up unless there is some user intervention to continue the boot. The work around I mentioned came from a suggestion in the ‘askubuntu’ link listed below. What we did was modify /etc/grub.d/10_linux changing ‘ro’ to ‘rw’, but with the thought that this is just a temp patch with possible (unknown) downstream impact.
Rebooting the system to get to the boot menu, I used the 'e' option to modify the parameters changing 'ro' to 'rw' as suggested in the 2nd thread. This temporary change allowed the system to boot.
"""
This bug is being reported to happen also after a clonezilla based installation for Trusty.
""" d/10_linux changing ‘ro’ to ‘rw’, but with the thought that this is just a temp patch with possible (unknown) downstream impact.
The issue with /tmp will timeout and continue to boot, / will hand the boot up unless there is some user intervention to continue the boot. The work around I mentioned came from a suggestion in the ‘askubuntu’ link listed below. What we did was modify /etc/grub.
https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1308152 askubuntu. com/questions/ 453411/ ubuntu- 14-04-not- booting- after-error- message- tmp-could- not-be- mounted
(can't boot from kernel 3.13.0.24 after upgrade to ubuntu 14.04 LTS but able to boot with kernel 3.11.0.20).
http://
Rebooting the system to get to the boot menu, I used the 'e' option to modify the parameters changing 'ro' to 'rw' as suggested in the 2nd thread. This temporary change allowed the system to boot.
"""