Old Bug Description for reference During boot the system gets 'stuck' on the Plymouth loading screen. This is not due to fsck.
Dropping into text mode the last line is that the file system is clean 'Root: clean , */* files */* blocks'. The system reacts to ctrl-alt-del and starts safely running the shutdown script 'looking of unattended updates, de-configuring network, .... '. Rebooting with '--verbose' kernel flag shows that the root fs on a MD raid is successfully assembled, mounted and checked for the need for fsck. The last thing the kernel does is run init. After this the same situation happens as above, all the correct init scripts are run with no errors. The system still reacts to events such as 'init: Handling usb- device-removed event' and even the screen enters and resumes power- saving. BUT the system never drops into any form of a shell on runlevel 1 or into GDM/X11. Running the kernel with 'break=init' and entering the busybox shell. I can successfully list the root fs and run init, but the same situation as above happens. Initially I thought it was due to nVidia's driver so i reinstalled without installing it and the same happens. The system does reboot successfully multiple times before I installed all the lucid updates (I started from 10.04-1). In '--verbose' Init states that plymouth-splash 'exited normally', 'goal changed from start to stop', ....., 'post-stop to waiting' and 'init: Handling stopped event'. That is the last thing that is printed to the screen during boot intill a event is run. ** Description changed: - During boot the system gets 'stuck' on the Plymouth loading screen. This - is not due to fsck. - - Dropping into text mode the last line is that the file system is clean - 'Root: clean , */* files */* blocks'. The system reacts to ctrl-alt-del - and starts safely running the shutdown script 'looking of unattended - updates, de-configuring network, .... '. - - Rebooting with '--verbose' kernel flag shows that the root fs on a MD - raid is successfully assembled, mounted and checked for the need for - fsck. The last thing the kernel does is run init. After this the same - situation happens as above, all the correct init scripts are run with no - errors. The system still reacts to events such as 'init: Handling usb- - device-removed event' and even the screen enters and resumes power- - saving. BUT the system never drops into any form of a shell on runlevel - 1 or into GDM/X11. - - Running the kernel with 'break=init' and entering the busybox shell. I - can successfully list the root fs and run init, but the same situation - as above happens. - - Initially I thought it was due to nVidia's driver so i reinstalled - without installing it and the same happens. The system does reboot - successfully multiple times before I installed all the lucid updates (I - started from 10.04-1). - - In '--verbose' Init states that plymouth-splash 'exited normally', 'goal - changed from start to stop', ....., 'post-stop to waiting' and 'init: - Handling stopped event'. That is the last thing that is printed to the - screen during boot intill a event is run. + Installing cloud-init on a non cloud system causes the boot sequence to + freeze with no error or warning. ** Summary changed: - boot freezes on init stage + boot freeze stage on non cloud ** Summary changed: - boot freeze stage on non cloud + boot freeze on non cloud -- boot freeze on non cloud https://bugs.launchpad.net/bugs/637172 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
