Public bug reported:
Working with headless server, my kernel boot console=ttyS0,
console=ttyS0,115200n8
Ubuntu stuck during boot , fsck prompt for user input
and wait for user input however keyboard console does not function
so system keep stuck ,
i expect that keyboard will be operation so i will be able to press S to skip
or R to recovery ,
or to workaround it with 10 seconds timeout and automatic Skip later on
68.810067] init: plymouth-upstart-bridge main process ended, respawning
[ 68.822144] init: plymouth-upstart-bridge main process (178) terminated with
status 1
[ 68.830078] init: plymouth-upstart-bridge main process ended, respawning
[ 68.842770] init: plymouth-upstart-bridge main process (180) terminated with
status 1
[ 68.850655] init: plymouth-upstart-bridge main process ended, respawning
* Stopping Read required files in advance[ OK ]
* Starting Mount filesystems on boot[ OK ]
* Stopping Track if upstart is running in a container[ OK ]
* Starting Initialize or finalize resolvconf[ OK ]
* Starting set console keymap[ 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 remote filesystems are mounted[ OK ]
* Starting device node and kernel event manager[ OK ]
* Starting load modules from /etc/modules[ OK ]
* Starting cold plug devices[ OK ]
* Starting log initial device creation[ OK ]
* Stopping set console keymap[ OK ]
* Stopping load modules from /etc/modules[ OK ]
* Starting Uncomplicated firewall[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device security[ OK ]
* Starting Mount network filesystems[ OK ]
* Stopping Mount network filesystems[ OK ]
* Starting Signal sysvinit that the rootfs is mounted[ OK ]
* Starting Clean /tmp directory[ OK ]
* Stopping Clean /tmp directory[ OK ]
* Starting configure network device[ OK ]
* Starting Bridge socket events into upstart[ OK ]
* Stopping Read required files in advance (for other mountpoints)[ OK ]
* Stopping cold plug devices[ OK ]
* Stopping log initial device creation[ OK ]
* Starting set console font[ OK ]
* Stopping set console font[ OK ]
* Starting userspace bootsplash[ OK ]
* Stopping userspace bootsplash[ OK ]
* Starting Send an event to indicate plymouth is up[ OK ]
* Stopping Send an event to indicate plymouth is up[ OK ]
The disk drive for /rescuecd is not ready yet or not present.
keys:Continue to wait, or Press S to skip mounting or M for manual recovery
<--- STUCK CANNOT PROCEED WITH BOOT --->
using mountall 2.53
amd64
filesystem mounting tool
Description: Ubuntu 14.04.5 LTS
Release: 14.04
** Affects: mountall (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1669081
Title:
Ubuntu doesnt boot stuck on FSCK prompt - Press S to skip mounting or
M for manual recovery
Status in mountall package in Ubuntu:
New
Bug description:
Working with headless server, my kernel boot console=ttyS0,
console=ttyS0,115200n8
Ubuntu stuck during boot , fsck prompt for user input
and wait for user input however keyboard console does not function
so system keep stuck ,
i expect that keyboard will be operation so i will be able to press S to skip
or R to recovery ,
or to workaround it with 10 seconds timeout and automatic Skip later on
68.810067] init: plymouth-upstart-bridge main process ended, respawning
[ 68.822144] init: plymouth-upstart-bridge main process (178) terminated
with
status 1
[ 68.830078] init: plymouth-upstart-bridge main process ended, respawning
[ 68.842770] init: plymouth-upstart-bridge main process (180) terminated
with
status 1
[ 68.850655] init: plymouth-upstart-bridge main process ended, respawning
* Stopping Read required files in advance[ OK ]
* Starting Mount filesystems on boot[ OK ]
* Stopping Track if upstart is running in a container[ OK ]
* Starting Initialize or finalize resolvconf[ OK ]
* Starting set console keymap[ 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 remote filesystems are mounted[ OK ]
* Starting device node and kernel event manager[ OK ]
* Starting load modules from /etc/modules[ OK ]
* Starting cold plug devices[ OK ]
* Starting log initial device creation[ OK ]
* Stopping set console keymap[ OK ]
* Stopping load modules from /etc/modules[ OK ]
* Starting Uncomplicated firewall[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device security[ OK ]
* Starting Mount network filesystems[ OK ]
* Stopping Mount network filesystems[ OK ]
* Starting Signal sysvinit that the rootfs is mounted[ OK ]
* Starting Clean /tmp directory[ OK ]
* Stopping Clean /tmp directory[ OK ]
* Starting configure network device[ OK ]
* Starting Bridge socket events into upstart[ OK ]
* Stopping Read required files in advance (for other mountpoints)[ OK ]
* Stopping cold plug devices[ OK ]
* Stopping log initial device creation[ OK ]
* Starting set console font[ OK ]
* Stopping set console font[ OK ]
* Starting userspace bootsplash[ OK ]
* Stopping userspace bootsplash[ OK ]
* Starting Send an event to indicate plymouth is up[ OK ]
* Stopping Send an event to indicate plymouth is up[ OK ]
The disk drive for /rescuecd is not ready yet or not present.
keys:Continue to wait, or Press S to skip mounting or M for manual recovery
<--- STUCK CANNOT PROCEED WITH BOOT --->
using mountall 2.53
amd64
filesystem mounting tool
Description: Ubuntu 14.04.5 LTS
Release: 14.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1669081/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
