*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
** This bug has been marked a duplicate of bug 571444
Boot hangs and unable to continue when automount disk in fstab is not
available (Off or Disconnected)
* You can subscribe to bug 571444 by following
Even if you set your entry in /etc/fstab to NOT run fsck, the current
mountall will HANG your system if there is a problem.
BTW, I wrote a small script to make booting a system a little less
scary. You can find it here, https://bugs.launchpad.net/bugs/614662
Gérald
--
No error message
oh god. i had this bug right now, i had to get my server from colocation
as sshd didnt start because the boot stopped at mount/fsck (i stupidly
added an automount for a -missing- pendrive with fsck option then made
system to force fsck at boot. Not that hard mistake to make as it sounds
at first.)
You know what I would REALY love to see since I am always concerned
about mountall giving me grief is and new option for the sixth field in
fstab.
If would be great if mountall could be updated such that the sixth field in
fstab is:
0 Don't check and **DON'T PAUSE**, filesystem does not need to
The reason you don't see anything is that you disabled the Ubuntu splash
screen.
If you remove the kernel options quite splash and you have entries in your
fstab that the system has a problem mounting.
**Your in trouble!**
I use a serial console to manage all my servers and this upstart bug is
Does the default install of Server even have the splash screen
installed?
I am running a plain install of Lucid Server x64. I know the desktop
version has the splash screen - plymouth, isn't it? I don't recall if
it's installed and enabled by default on the server install.
I checked what the
I see what you meant now, you need to enable the splash screen by
adding splash after quiet in the boot options.
With that enabled, it displayed the error message. It would be nice to
not have to rely on a splash screen to display error messages when it is
not turned on by default.
I would much
I would much rather have it display the error on the terminal instead.
Tell me about it. I don't have monitors attached to the servers I admin
so this is a real prob for me.
I can no longer admin the servers strictly from the serial console.
Gérald
--
No error message displayed when device
** Tags removed: needs-upstream-testing
--
No error message displayed when device fails to mount on Ubuntu Server 10.04
https://bugs.launchpad.net/bugs/609864
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi Charles,
If you could also please test the latest upstream kernel available that would
be great. It will allow additional upstream developers to examine the issue.
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the
upstream kernel, please remove the
Installed /~kernel-ppa/mainline/v2.6.33.5-lucid
2.6.33-02063305-generic x86_64
Same thing - no error message displayed.
Installed /~kernel-ppa/mainline/v2.6.34-lucid
2.6.34-020634-generic x86_64
Same thing - no error message displayed.
Installed /~kernel-ppa/mainline/v2.6.35-rc1-lucid
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52503567/BootDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52503568/Dependencies.txt
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/52503569/Lspci.txt
** Attachment added:
After hitting s the OS boots normally.
** Attachment added: No error message is displayed, you have to know to press
s to skip the problem mount
http://launchpadlibrarian.net/52503951/Ubuntu%20Lucid%20Hit%20s.jpg
--
No error message displayed when device fails to mount on Ubuntu Server
Having no error message like the one displayed in Ubuntu Desktop causes
confusion as to what is wrong.
See attached screenshots for what happens if the OS is unable to mount a
device listed in fstab on boot.
** Attachment added: OS is hung when booting after a device listed in fstab
is not
14 matches
Mail list logo
