On Wed, Dec 11, 2013 at 08:01:07PM -, Nathan Groupp wrote:
> @Steve Langesek
> Actually, yes, that sounds like a great idea. What, exactly, is the
> point of prompting for console input when the operator is 5,000 miles
> away and there is no console?
There's no point in prompting. I asked y
@Steve Langesek
Actually, yes, that sounds like a great idea. What, exactly, is the
point of prompting for console input when the operator is 5,000 miles
away and there is no console?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
On Tue, Dec 10, 2013 at 09:26:47PM -, James Burns wrote:
> I'm having the same issue as Nathan. There should be a way to totally
> disable prompting in mountall if this is to be deployed in the cloud.
And do what instead of prompting? The system blocks on mountall because
it's waiting for the
I'm having the same issue as Nathan. There should be a way to totally
disable prompting in mountall if this is to be deployed in the cloud.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096307
Title:
I have the same issue in 13.04, however I don't get any messages. To be
able to continue I need to edit my grub options by removing "quiet
splash" and adding "nomodeset". Then I get the prompt for "Press S to
skip mounting or M for manual recovery".
--
You received this bug notification because y
I have reproduced this on the Ubuntu 12.04 LTS AWS AMI. Resolving an
error is particularly nasty when using cloud services, as a second,
running instance is required to debug the cause of boot failures. On
AWS, this involves removing the EBS system volume from the instance then
mounting it temporar
Hi Steve, I tried to reproduce this bug uncommenting the not existing
swap partition in my fstab file , but it does not want to hang my system
any more. Sorry for wasting your time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Zentai, I've run this test here with exactly that version of plymouth.
Please file a separate bug report for your issue and describe precisely
how I can reproduce the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I experienced the same boot hangup on a 64 bit 12.04 Ubuntu after the
update of plymouth to Version: 0.8.2-2ubuntu31
I had a missing swap partition in my /etc/fstab file which triggered some
mountall warning before.
Seems like the new plymouth takes this error seriously and the system will not
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plymouth (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096307
Title:
Ok, if the messages are not showing up, that would seem to be a bug in
plymouth rather than in mountall. And it seems to be specific to use of
a serial console. Could you post the full contents of /proc/cmdline on
the affected system? (Even better would be to run 'apport-collect
1096307' and let
Steve, I forget to mentioned one thing.
The platform we use is ARM not x86. Our Ubuntu 12.04 is installed through guide
for Marvell ArmadaXP Demo board.
On our deivce, there is only console /dev/ttyS0 for message output.
Is it possible that there is some package missing or and mis-
configurait
I've tried to reproduce this with both mountall 2.36 and mountall
2.36.3, and cannot. When booting the system, with or without plymouth
splash enabled, I'm shown a prompt as expected:
The disk drive for /test is not ready yet or not present.
Continue to wait, or Press S to skip mounting or M fo
Ed, which version of mountall do you have installed here? By design,
mountall should notify the user of this mount failure via plymouth, but
as your sample fstab entries show mount points that are not required for
the OS to boot, they should not block the rest of the system from being
started. As
Hi Steve, this issue can be easily reproduced through either of the following
scenario on Ubuntu 12.04.
Assuming Ubuntu 12.04 is located as /sda2, and I have two HDD connected as sda,
sdb. sdb4 is formatted as ext4
1. Adding one entry in /etc/fstab which will try to mount a non-existing disk
de
Please elaborate on what you mean when you say "mount a non-existing
device node". Do you mean you've added an entry to /etc/fstab? If so,
please show the exact fstab that triggers this issue.
A missing system filesystem caused by an incorrect entry in /etc/fstab,
or a failed disk, is indistingu
16 matches
Mail list logo
