Many thanks for the hint in comment #44.
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
I just ran into this very same problem on a xenU host.
To fix this I did:
mount the root partition and chroot into it.
remove 'mountall' which triggers an uninstall of 'cron' and 'upstart'.
reinstall: upstart-compat-sysv and cron from jaunty.
exit the chroot, umount the root partition
restart the
I still have this error in my system after upgrading from 9.04 to 9.10.
Creating root device.
Mounting root filesystem.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting in
** Changed in: mountall (Ubuntu)
Status: Fix Committed => Fix Released
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
I may have been responsible for a false-flag that there had been a fix.
Apologies to all.
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
I seem to be affected by this bug as well, after updating from
2.6.31-17 to 2.6.31-19. I followed the instructions in the Upstart Wiki
referenced above and after initialization a call to mountall causes an
infinite loop of the following assertions.
process 2324: arguments to debus_pending_call_set
** Changed in: mountall (Ubuntu)
Status: Fix Released => Fix Committed
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
I have a very similar problem, I am trying to run uml and I receive
this:
[42949373.57] line_ioctl: tty0: ioctl KDSIGACCEPT called
mountall:/proc: unable to mount: Device or resource busy
mountall:/proc/self/mountinfo: No such file or directory
mountall: root filesystem isn't mounted
init: mou
hi,
the same problem - upgraded xen instance to karmic and dom0 kernel
upgrade is not under my control. Any workarounds? :)
best regards,
m
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notification because you are a member
I recently upgraded my xen instance from jaunty to karmic and - surprise
- it does not come up any more.
How can I fix this problem? As the dom0 is not under my control,
upgrading the kernel is not an option. Downgrading mountall? Replacing
mountall by a shell script to only mount /proc?
Why is
Similar errors to Sebastian Beca here if I remember them correctly. I
used to run a virtual server powered by Jaunty. The upgrade to Karmic
then killed it with regard to booting from inside the XEN machine, which
uses a 2.6.26-2-xen-686 kernel on Debian Lenny.
I am able to mount the filesystem of
Thanks very much for the help waverider. Alas, it looks like new errors
crop up so I have to turn to paid help for now.
I thought I'd update this for future reference for anybody else who may have
this problem in future:
- waverider's help/advice is quite helpful as above, also I came across this
Hi Vpo,
Google is your friend. Have a look at these - they may help:
http://www.linuxquestions.org/questions/linux-software-2/gtk-warning-
locale-not-supported-by-c-library-202951/
http://community.activestate.com/forum/if-you-receive-error-gtk-warning-
locale-not-supported-c-library
--
karmic
Thanks very much for the details waverider! I think this is what I need
to do. I just tried this though and I get a message saying:
"(process:6975):GTK-WARNING **: Locale not supported by C library. Using
the fallback 'C' locale.
"(gedit:6795):GTK-WARNING**: Cannot open display"
I tried this wit
Hi VPO,
My solution was to add new lines to Menu.1st
Using your preferred editor (vi, nano or whatever) - I will use nano as
an example:
sudo nano /boot/grub/menu.1st
This will open menu.1st in nano
Find the last kernel list lines that look something like this:
title Ubuntu 9.10
sorry, forgot to attach the screenshot of the boot error
** Attachment added: "ubuntu-bootup-error.jpg"
http://launchpadlibrarian.net/37258620/ubuntu-bootup-error.jpg
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notificati
I'm having the same problem when I updated from 9.04 to 9.10.
I'm fairly new to linux/ubuntu so I don't know how I'm supposed to
correct the kernel to 2.6.31? I tried many of the suggestions posted
here and related posts but unable to get through them without errors.
I tried what "itsjareds" sugg
My apologies if I am outside the process for reporting problems but this
is my first post.
I have had similar problems with an upgrade from 9.04 server to 9.10
server. Mountall failed and I was unable to connect to the network to do
any updates
After following this thread and with help from other
For me the simple reason for the phenomena depicted at the very
beginning of this thread was that I hampered my /etc/fstab before
restart, as I realized later. To cure the problem it was necessary to
check the UUID's of the hard drives with the blkid command and rewrite
fstab using a Live CD.
--
Boot into a Live session of Ubuntu and then open a terminal and mount
your installed Ubuntu partition. (I'll use /dev/sda1 as your root.)
# mkdir /mnt/ubuntu
# mount /dev/sda1 /mnt/ubuntu
# mount -t proc none /mnt/ubuntu/proc
# mount -o bind /dev /mnt/ubuntu/dev
# chroot /mnt/Ubuntu
# apt-get upda
Yes, but now the system does not boot. How can I fix it?
Is there a way to use the 9.10 boot disk to get into my system and upgrade
the kernel? Will this fix it?
BK
On Mon, Nov 23, 2009 at 1:13 PM, Scott James Remnant
wrote:
> On Mon, 2009-11-23 at 15:09 +, Sebastian Beca wrote:
>
> > Same pr
On Mon, 2009-11-23 at 15:09 +, Sebastian Beca wrote:
> Same problem, kernel 2.6.24, update and i get:
>
2.6.24 is too old - you need to use 2.6.31 on karmic (which is the
kernel it comes with!)
Scott
--
Scott James Remnant
sc...@ubuntu.com
** Changed in: mountall (Ubuntu)
Status: I
Same problem, kernel 2.6.24, update and i get:
mountall: /proc: unable to mount: Device or resource busy
mountall: /proc/self/mountinfo: Not such file or directory
mountall: root filesystem isn't mounted
init: mountall main process (2025) terminated with status 1
General error mounting filesystems
man2d: do not reopen bugs for which you are not the original reporter
** Changed in: mountall (Ubuntu)
Status: Incomplete => Fix Released
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notification because you are a memb
** Changed in: mountall (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: mountall (Ubuntu)
Status: Fix Committed => Incomplete
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notification because you a
I've had a similar experience to mars_calling - upgraded from hardy and having
trouble booting newer kernels but can't boot an older kernel because of this
mountall dependency. Would be nice if mountall was less fragile...
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launc
I have a slightly different problem and not a solution, unfortunately.
Perhaps it has been reported under another bug and would appreciate a
pointer to such.
Mountall fails with the following error (upgraded from Hardy Heron to
Karmic Koala):
This error occurs when trying to boot with an older ke
Awesome! Hopefully anyone else with this problem will have it fixed and
maybe even comment here if they have such luck. Thanks.
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks
I'm pretty sure you have symptoms of a bug that has now been fixed,
without the original installation there's no way to tell so I'm going to
optimisticly mark this Fix Released :-)
** Changed in: mountall (Ubuntu)
Status: Incomplete => Fix Released
--
karmic - mountall fails to mo
I don't remember much anymore because I had to overwrite that Karmic
installation to write up some papers for school. I did manage to get
some pictures from my phone of my boot messages though.
Beginning of the errors, starts below the CHICONY Keyboard line -
http://i36.tinypic.com/4qfseg.jpg
Fur
Could you please confirm:
- what error did you get? When you say "the error", which error? If
you can quote the exact text, that would be helpful
- when you say that it restarted automatically, what do you mean?
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.ne
Scott James Remnant wrote:
-
itsjareds: right, that doesn't work with Upstart I'm afraid - you need to
follow the wiki instructions and boot normally (though without "splash")
that'll give you a root shell
-
I tried booting normally and removing 'quiet splash' and I still got the
error a
** Changed in: mountall (Ubuntu)
Importance: Undecided => Medium
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
On Mon, 2009-10-12 at 17:40 +, Dave North wrote:
> This raises another issue. The online rumor is Ubuntu generally will no
> longer support linux booting without an initrd. If this is the case I'll
> politely go away and be done with Ubuntu, but it would be good to know
> if my "bug" is someth
itsjareds: right, that doesn't work with Upstart I'm afraid - you need
to follow the wiki instructions and boot normally (though without
"splash") that'll give you a root shell
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug noti
Scott James Remnant wrote:
How did you "boot into Ubuntu" ?
To be more clear I just edited the normal Grub line I boot with and
added /sbin/sulogin to the end.
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notificati
The problem on my system is clearly with mountall. I went to the source
repository and grabbed a couple of binaries, 0.2.0 and 0.1.8, which I
then subbed into my system. Mountall 0.2.0 failed at the same place,
mountall 0.1.8 works great. I'm running 2.6.31.3 without an initrd. This
is a switch of
On Sat, 2009-10-10 at 23:54 +, itsjareds wrote:
> I followed the steps on http://upstart.ubuntu.com/wiki/OMGBroken up to
> the part where I booted into Ubuntu and got into an emergency bash
> shell.
>
How did you "boot into Ubuntu" ?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
karmic
@Dave North: No, this problem occurred for me on my stock 2.6.31-11,
-12, and -13 kernels.
By the way I had to reinstall Ubuntu because I needed to use the
computer for school. A fresh install of Karmic seems to be working fine.
--
karmic - mountall fails to mount filesystem on boot
https://bugs
Are you folks running custom kernels? I'm seeing the same thing, but
only when I boot my stock 2.6.31.3 downloaded from kernel.org and built
without any modules. If I use the Ubuntu kernel, the install boots
normally -- which is to say, slower. But it does boot. With my
kernel.org kernel, it hangs
I have the same problem here.
But I am not completely sure that mountall is really the problem, because at
first, the last thing I saw on the console were some errors about not being
able to mount my windows partition. I edited my fstab and added "noauto", now
the error messages are gone, but th
I had a little help in #ubuntu+1 on Ubuntu's IRC, no luck but at least I
have a bit more info:
I attached my fstab. I commented out my ntfs partitions to see if that
was the issue, but it doesn't look that way. I haven't modified my fstab
for a long while and it's worked fine. Does anything look o
I followed the steps on http://upstart.ubuntu.com/wiki/OMGBroken up to
the part where I booted into Ubuntu and got into an emergency bash
shell.
I'm not sure if i need to start any services with 'start xyz'. I'm not
that experienced with Linux yet.
I tried just running 'exec /sbin/upstart' but I
On Sat, 2009-10-10 at 17:57 +, itsjareds wrote:
> Ok, I chrooted to my Ubuntu partition and got this output:
>
> -
> # mountall --debug
> mountall: Could not connect to Upstart: Failed to connect to socket
> /com/ubuntu/upstart: Connection refused
> -
>
The system (ie. init) needs t
Ok, I chrooted to my Ubuntu partition and got this output:
-
# mountall --debug
mountall: Could not connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
-
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You
Plese run "sudo mountall --debug" and attach the output
** Changed in: mountall (Ubuntu)
Status: New => Incomplete
--
karmic - mountall fails to mount filesystem on boot
https://bugs.launchpad.net/bugs/447747
You received this bug notification because you are a member of Ubuntu
Bugs, whic
46 matches
Mail list logo
