This bug has gotten me also I have found the undocumented
workaround, but unfortunately after the damage has already been done. I
have a system 5 states away, and only one person in the area that is 60
miles away. In order for me to fix this, I must ask them to drive two
hours round trip jus
Do we have a fix for this bug yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571444
Title:
Boot hangs and unable to continue when automount disk in fstab is not
available (Off or Disconnected)
I got bitten by this in Ubuntu Server 12.04 LTS because of an fstab
entry for an external USB disk (user-mountable).
The 'nobootwait' option in /etc/fstab did the job, but it is really
poorly documented. Because the issue occured around the time of
automatic fs checking, the logical place for me t
I got bitten by this in Ubuntu Server 12.04 LTS because of an fstab
entry for an external USB disk (user-mountable).
The 'nobootwait' option in /etc/fstab did the job, but it is really
poorly documented. Because the issue occured during automatic fs
checking, the logical place to search was 'man f
This issue has bugged me many times, but I think the real bug is not the
hang during boot under those circumstances, but the fact that during
boot process a message is given to the user, but the user can't see it!
Here the original problem was the hang in the boot process because the
disk was not
actually, no separate bug report needed - that appears to be bug
#655616.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571444
Title:
Boot hangs and unable to continue when automount disk in fstab i
In 12.04, mountall supports both 'nobootwait' and 'timeout' options to
control whether mountall should wait for a given filesystem before
signalling for the boot to proceed. That seems to be the issue raised
in this bug, so I think this is resolved.
There were other comments about the plymouth pr
If nobootwait doesn't work, try the nofail option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571444
Title:
Boot hangs and unable to continue when automount disk in fstab is not
available (Off
nobootwait break the mount command
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571444
Title:
Boot hangs and unable to continue when automount disk in fstab is not
available (Off or Disconnected)
I also had the same problem, but I found the solution:
sudo nano /etc/fstab
"nobootwait" - add this option to all external partition descriptions
The "bug" is resolved! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
We've also been bitten by this. We run approximately 2000 servers
(currently mostly Debian, but increasing numbers of Ubuntu Lucid).
We're finding our servers hang if, for example, a SAN disk has failed,
for whatever reason. Now, yes, we usually have some sort of remote
console access, but it's a
** Changed in: mountall (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/571444
Title:
Boot hangs and unable to continue when automount disk in fstab is not
a
** Changed in: mountall (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571444
Title:
Boot hangs and unable to continue when automount disk in fstab is not
a
I haven't heard anything.
You can add "nobootwait" to fstab to tell the OS to not wait for that
drive if it fails to mount.
You can also use the script that Gerald wrote up:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/614662
--
You received this bug notification because you are a me
Has there been any progress on this issue?
I run a headless server with an external USB drive attached. I found
this issue during a test power failure.
The server was shutdown properly and the power was cut to the external
drive. When the power returned, the server restarted but the drive did
not
Interesting history of discussion on this topic. I also stumbled on a
small thread regarding users confused about what to do for this here:
http://ubuntuforums.org/showthread.php?p=10094269#post10094269
I'm a fairly big fan of having a timeout for bootwait. Alternatively,
perhaps we need another o
To summarize, when booting a system, we have 2 options:
- We use "bootwait" on all local filesystems (default)
- We use "nobootwait" on all local filesystems.
The problem with "bootwait" is that it outright prevents the use of Ubuntu on a
headless system.
The problem with "nobootwait" is that i
I think we need to include the very real scenario where Ubuntu Server is
used in a headless capacity. For example I have a dedicated server with
GoDaddy and I have absolutely ZERO access to console. In truth, I
rarely have access to console on pretty much all the server I admin.
If I reboot a sy
@Philip: That's great news! Should save some from headaches in the
future. :-)
@Matheiu: Yes, I definitely wouldn't want nobootwait to be default for
my servers. A common scenario for me is a separate RAID array with
essential files for services on the server.
@Tim: A policy like that sounds good
The issue that it doesn't show any messages on the console is tracked in
bug 563916 and has been fixed in maverick, lucid is still being worked
on.
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You
@dblade I wasn't taking a stand on the other issues. But I agree not
displaying the message is/was a bug.
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because yo
@Tim: I agree with this policy and perhaps mountall is doing a better
job now at adhering to it.
I have a problem with informational messages and prompts are not showing
up on console. This isn't as big of a deal when you are aware of the
issue; you said yourself that you went through the source
I believe the correct policy for mountall is to ignore missing
filesystems that are marked with options "owner", "user" or "noauto".
Everything else should properly cause a hang (unless an admin explicitly
says a filesystem isn't required via nobootwait). "noauto" should
already be ignored and "us
>I have just tested what happens with Debian Etch if there is wrong (missing)
>devices in /etc/fstab : system don't boot, problem
> with fsck ("the superblock could not be read..."). Same behavior on
> Hardy. I think that if users really want to boot with
> missing parts, they should explici
My morning thoughts about "Default behavior for missing part set to
nobootwait" : in my opinion, this should not be done ! As if you are in
production system, your machine should only start if all prerequisites
are satisfied. Imagine what happens if you have /usr missing, with all
programs that sho
thanks,
all 3 absent infstab labeled SATA disks automatically skipped boot without
intervention.
$ dpkg -l | grep mountall
ii mountall 2.15.3~kumy2
filesystem mounting tool
for me the problem is completely solved.
thank you and
Thanks. I will try to provide feedback on your package hopefully
tonight.
I also like Erik Reuter's idea of a timeout which I think would be a
viable alternative in the event the consensus was that BOOTWAIT should
be the default. This is assuming that prompt/error messages were
corrected to disp
I've uploaded a new revision, and included other patches : (it's
currently building)
mountall (2.15.3~kumy2) lucid; urgency=low
* Default behavior for missing part set to nobootwait (LP #571444).
* mountall does not honor nobootwait flag on /var/* and /usr/* filesystems
(LP #654545)
* gfs2
@dvdb: for the missing splash screen, you just need to add "splash" to
your grub conf !
edit /etc/default/grub
modifiy line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
then regen grub's conf (update-grub2)
that does the trick for me :)
Also, I've tested my
Mathieu Alorent: my guess would be that there would be resistance to
this change as I think the goal is to empower the user to correct a
stituation without having to resort to technical recovery procedures or
find out about the problem after the fact. It is good that it is
configurable via fstab,
@bvdb: I've tested with your mount points and I was able to skip all
partitions
Here is an extract of my fstab:
inexistant.machine:/var/opt/hosting/data/var/opt/hosting/data nfs
defaults0 0
inexistant.machine:/var/opt/hosting/toto/var/opt/hosting/toto nfs
@dvdb: my case was about NFS mounts, I'll try with your config
@dblade: yes, the patch allow me to "press "S" to skip more than just the first
missing drive", my case was on NFS mount point.
@dblade: about the messages not displayed, we've got this problem too when we
started to install our serv
Mathieu Alorent I don't see a description on your ppa as to what you
implemented. Does your patch allow you to press "S" to skip more than
just the first missing drive?
>From what I can see (including other bugs) not everyone is seeing the
interactive prompt or errors when this hang issue occurs.
# dpkg -l | grep mountall
ii mountall 2.15.3~kumy1
filesystem mounting tool
I had to comment these out again to boot.
No solution on this computer.
#LABEL=HOME_IMAGES /images autodefaults0 0
#LABEL=BACK_SG /
For the specific problem : "Press "s" to skip the missing filesystem and
continue booting. - This workaround only works for the first missing
drive. For more missing drives press alt-sysrq-i and edit your fstab to
remove missing drives"
Please see bug #655616, I've made a patch and built a new p
I'm booting some test installs that use vmdks that point to raw devices.
It just so happened one non-crucial drive /dev/sdc was not available and
the boot process would hang. The twist is I don't see any error message
or prompt for input like this bug suggests. If it wasn't for this bug
report I
See also: bug #638228
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
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
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received t
Hello,
I ran into the same thing a few months ago and automagically fixed it by
mashing on the keyboard.
I did file a couple bug reports, but I guess they got no real attention
since it wasn't filed with the right package.
There are https://bugs.launchpad.net/ubuntu/+source/linux/+bug/609864
and
** Tags added: glucid
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Tags added: lucid
** Tags removed: glucid
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: glucid
** Tags removed: lucid
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I commented in a bug now marked as a duplicate of this one, but I'll re-post
here:
Anything with the 'user' fs option, should probably be ignored/skipped
by mountall to begin with, as those filesystems are generally not wanted
at boot time. I'm not sure how the current design of mountall could
o
Thank you Tim,
this workaround seems to work for me ... (the last 24hours at least).
Please Ubuntu, or Mint, do something about this very annoying bug!!!
I'm a linux teacher, and my negativity on the latest bugs in 10.04
is unconsciously influencing my students.
--
Boot hangs and unable to conti
After being frustrated with this bug for a while, I grabbed the mountall
source... it's a lot of stuff, but one thing I found was the
"nobootwait" option.
Adding "nobootwait" to all my "auto" mounts allowed my system to boot up
without intervention.
Although the fstab manpage is a little terse de
On 12/08/10 08:23, Erik Reuter wrote:
> I sent a message to Scott Remnant a couple weeks ago, referencing this
> bug. It does not seem to have gotten any attention.
>
> I'm not sure what Ubuntu is coming to when an important bug like this
> seems to be ignored by the developers.
>
>
Yes, It's a
I sent a message to Scott Remnant a couple weeks ago, referencing this
bug. It does not seem to have gotten any attention.
I'm not sure what Ubuntu is coming to when an important bug like this
seems to be ignored by the developers.
--
Boot hangs and unable to continue when automount disk in fsta
Pretty annoying bug and crippling to those of us that are dealing with
remote servers.
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because you are a member of Ub
Grrr. This is a medium priority bug and it's still unassigned.
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I've just been hit by this bug on 2.6.32-24-server #38-Ubuntu SMP x86_64
GNU/Linux
Here it's on a machine in a rack that has no video output or keyboard so
all I initially observe is a machine that didn't restart from power
down.
Remove the fstab entry and attempt to mount the remote drive after
This is a serious bug which means I will recommend that my customers not
upgrade to 10.04 for server environments till this is fixed. Same
problem occurs when a softRAID error prevents the array from being
mounted.
Unfortunately I can't develop a fix, but here's a few recommendations:
1. Timeout
Hi,
I confirm this pesky bug also affects sshfs entry on fstab (when the distant
ssh server is unavailable, running ubuntu server 10.04). The "s" touch solves
the problem, but as already said on a previous comment, the recovery mode
doesn't work... I won't comment on the "medium" importance, but
This also affected a 9.10 -> 10.04 Desktop, not Server, machine that had
removed the `splash' from the kernel line some time earlier. The non-
free virtualbox had placed the line
none /proc/bus/usb usbfs devgid=127,devmode=664 0 0
at the end of /etc/fstab some months earlier. Its presence c
It seems to me that mountall must be modified to timeout after X number
of seconds, where timeout means the equivalent of pressing 'S' for
skipping the unmountable volume.
The man page for mountall gives the author as "Scott James Remnant
".
Scott appears to be an employee of Canonical:
https://
Hi folks, I have the same problem with mounting nfs-shares on my working
machine to my htpc in the living room. There are 4 mount points for my
mythtv home entertainment and backup strategy.
/etc/fstab:
obelix:/var/lib/mythtv/music /var/lib/mythtv/music nfs _netdev,auto 0 0
obelix:/var/lib/mythtv/
This is a critical problem for me. I connect to my Ubuntu machine
remotely. If the drive is not found (OK if it is not) then the machine
hangs during boot. I cannot remote x-win and cannot ssh to the machine
without getting physical access. Have to connect a monitor and keyboard
to see what is
Ubuntu 10.04 (Server). Drobo connected via USB. Same problem. If I press
"s" the system will continue to boot. Putting "noauto" in /etc/fstab as
mentioned by Erik does the trick. Additionally, I also put a mount
command into /etc/rc.local. Not perfect, but it will do me for now.
/etc/fstab
LABEL
** Description changed:
On 10.04 Lucid server installations, if a filesystem that is specified in
/etc/fstab cannot be mounted for some reason (USB disk not connected, partition
deleted, samba share not availible etc.) the boot process hangs displaying
"mountall: Filesystem could not be moun
Importance should be high. In my own scenario I'm mounting to CIFS
shares on a server. If that server is unavailable then the Ubuntu server
will not boot at all. Pressing S seems to achieve nothing.
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Discon
This bug bit me also. I had a line in /etc/fstab for an iscsi volume
that was not available at boot time, and the system just hangs during
boot.
Workaround was to put the noauto option on the volume in /etc/fstab.
But I think this is a serious bug. I suspect most Ubuntu users would be
very frustr
** Changed in: mountall (Ubuntu)
Status: New => Confirmed
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Problem with this bug is that it interferes with a backup script i use
for several customers, sensing the right drive, and when found executing
the correct backup ...
Moreover, pressing S only works for the first drive it does not find, when
pressing S a second time, the system really hangs ...
(
** Description changed:
+ On 10.04 Lucid server installations, if a filesystem that is specified in
/etc/fstab cannot be mounted for some reason (USB disk not connected, partition
deleted etc.) the boot process hangs displaying
+ "mountall: Filesystem could not be mounted: ..."
+ Screenshot:
ht
This happened to me because for some reason 10.04 does not load the
wireless modules prior to attempting to connect to network shares that
are in fstab. The network (samba) shares are not able to be found and
then the boot just hangs. No shell, nothing, I can only reboot or use
the work around, t
@Scott:
1) I apport-collect'ed it.
2) Pressing "s" continues the boot process :)
3) # ls -l /lib/plymouth/themes
total 8
drwxr-xr-x 2 root root 4096 May 16 15:12 details
lrwxrwxrwx 1 root root 31 May 16 15:28 text.plymouth ->
/etc/alternatives/text.plymouth
drwxr-xr-x 2 root root 409
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release i386
(20100427)
Package: mountall 2.15
PackageArchitecture: i386
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.34-020634rc7-generi
Hit similar issue:
Removed drive from system but forgot to remove the line i fstab referencing to
it. Hence no 'filsystem' emitted. System hangs.
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You r
Same here (using Ubuntu 10.04 server). One of my hard drives is
formatted with JFS but I forgot to install jfsutils. Now when I try to
boot it says:
fsck: fsck.jfs: not found
fsck: Error 2 while executing fsck.jfs for /dev/sdb1
linuxroot: clean, ...
mount: wrong fs type, bad option, bad superblock
I have been delayed in getting the information (10.04 desktop
reinstall/setup eating my time)(Plus Wife factor of x3~6 delays)
However I will add to this bug's info.
This bug ALSO affects ubuntu 10.04 desktop edition.
I reproduced this but by accident on my Desktop install.
I was experimenting
Ok. I'll do that asap. (~12-24h)
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Thanks for the report,
In order to debug further I'll need you to collect a bit more
information for me. First can you run "apport-collect 571444" on your
system, this will attach various files from your system to the bug which
I need to analyse.
This is a server install, right? Could you run "
** Package changed: ubuntu => mountall (Ubuntu)
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
72 matches
Mail list logo
