Ubuntu doesnt boot stuck on FSCK prompt - Press S to skip mounting or M for manual recovery

Bug #1669081 reported by Bazak1
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mountall (Ubuntu)
Expired
Undecided
Unassigned

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

Revision history for this message
Nish Aravamudan (nacc) wrote :

"console=ttyS0, console=ttyS0,115200n8"

Is that actually what you are passing? That doesn't seem correct for serial consoles.

Changed in mountall (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mountall (Ubuntu) because there has been no activity for 60 days.]

Changed in mountall (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.