[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 xen domain. so basically you cannot upgrade to karmic (and beyond?) if you're stuck on somewhat older kernels it seems. bummer. -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys 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: mountall main process (248) terminated with status 1 General error mounting filesystems. A maintenance shell will now be started. CONTROL-D will terminate this shell and re-try. the kernel is 2.6.18-xenU Any suggestions ? -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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_notify() were incorrect, assertion "pending !=NULL" failed in file dbus-pending-call.c line 596. This is usually a bug in some application using the D-Bus library. Is this the same bug? -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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: mountall main process (640) terminated with status 1 General error mounting filesystems. A maintenance shell will now be started. CONTROL-D will terminate this shell and re-try. r...@localhost:~# -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 karmic so dependent on kernel >= 2.6.26? What is the advantage in using /proc/$pid/mountinfo? -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 the Karmic system on a loopback device and chroot to it using that very 2.6.26-2-xen-686 kernel, so it's not a general incompatibility. Right now I converted the Karmic based virtual server to a physical machine, but it is only a temporary, unsatisfactory solution. Upgrading the XEN machine's kernel is not an option. -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 article at the link below which I found to be one of the more detailed and clear in terms of restoring GRUB: http://gwos.org/udsf/doku.php/core:grub:restore -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 - 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 with nano as well but no luck either. It looks like a problem with the locale definitions? not too sure how I should fix this before I can modify the menu.1st file. -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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, kernel 2.6.24-21-generic root(hd0,4) kernel /boot/vmlinuz-2.6.24-21-generic root=UUID=d0b20b1a-bf95-45f5-9276-59005afd293b ro quiet splash initrd /boot/initrd.img-2.6.24-21-generic quiet title Ubuntu 9.10, kernel 2.6.24-21-generic (recovery mode) root(hd0,4) kernel /boot/vmlinuz-2.6.24-21-generic root=UUID=d0b20b1a-bf95-45f5-9276-59005afd293b ro single initrd /boot/initrd.img-2.6.24-21-generic Copy these lines and past them directly below, then change all the kernel version entries (2.6.24-21-generic in this case) to whatever kernel is your most recent ie. the one installed by the update process eg 2.6.31-15-generic-pae as it was for me. Save the menu.1st file and reboot This worked for me -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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" suggested in post #28 but it displayed an error when "upgrading". I also tried what Mark Jackson Pulver suggested in this post #4 (https://bugs.launchpad.net/ubuntu/+bug/128313) but I didn't work and I tried to locate the 2.6.31 kernel package but don't know the exact name I should input. I've burned a recovery disk and working from there but have no idea how to move forward. During the GUI upgrade process, I kept the "menu.lst" rather than replacing it with the new one and I think that's where the problems lie. I've attached a screenshot of the error (which is similar to the ones posted above). I'm just not sure of the actual command lines/steps I need to take to fix this. Any help with step-by-step instructions for a newbie would be great! 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 others, it appears that the upgrade failed to modify menu.lst and my installation was trying to boot from kernel 2.6.20-16-server instead of the latest 2.6.31-15 -generic-pae which was installed on the server but not listed in menu.lst. This was why mountall failed - the kernel being used was too old. It would seem to me that this is a bug in the upgrade process. It is also evident that upgrade-grub does not work, as I eventually had to modify menu.lst manually to get grub to boot with the correct kernel - upgrade-grub makes no changes to the file. Sorry if I am out of line or reporting this incorrectly. -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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. -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 update # apt-get upgrade -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 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: Invalid => 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 direct subscriber > of the bug. > > Status in “mountall” package in Ubuntu: Fix Released > > Bug description: > Binary package hint: mountall > > I ran a daily update in Karmic and then restarted my computer. Ubuntu tried > to boot up but it gets stuck at a "cannot mount filesystem" error. I thought > it may have been a problem with the new kernel I installed but I tried my > old one and it still occurred. Ubuntu won't even boot in recovery mode. Now > I'm in a LiveUSB to be able to use my computer and submit this bug. > > I asked for help in the IRC server and one user told me that this was a > problem with the mountall package. My apologies if I filed this under the > wrong package. > > ProblemType: Bug > Architecture: i386 > Dependencies: > > DistroRelease: Ubuntu 9.04 > MediaBuild: Ubuntu 9.04 "jaunty" - Release i386 (20090918) > Package: mountall None [modified: /var/lib/dpkg/info/mountall.list] > ProcEnviron: > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: mountall > Uname: Linux 2.6.28-15-generic i686 > UnreportableReason: This is not a genuine Ubuntu package > -- Sebastián Beca C. Gerente de Proyectos sb...@cognus.cl Cognus, Top Line Consulting Av. Presidente Riesco 5335 piso 9 Las Condes, Santiago, Chile Tel: (562) 714 38 11 www.cognus.cl -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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: Invalid => 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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. what is the fix? ** Changed in: mountall (Ubuntu) Status: Fix Released => Invalid -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
** 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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.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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 kernel 2.6.24-24-generic, which was working with Hardy. The new kernel (2.6.31-??) does not get very far in the boot process, before it dies. I will submit a bug once I figure that one out. I was hoping to at least get going with a known working kernel, but it seems that is not to be either. Here is the error message: 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. A maintenance shell will now be started. ... -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 Further down in the boot sequence - http://i34.tinypic.com/4izh54.jpg I pressed ctrl+alt+del to add those messages below the 'Starting init crypto disks...' line - http://i36.tinypic.com/333bf9c.jpg Sorry I don't have better images, but this is all I have to recall. -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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.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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 and it restarted automatically. -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
** 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 something that simply won't be addressed. > No, we absolutely support that - in fact it's much faster to not have an initrd if you have your storage controller and filesystem drivers built into the kernel. You lose the ability to resume from hibernate, have root on LVM or MD, etc. but I don't think those are particularly compelling anyway ;) > Here's what appears on my console at the point of failure: > > mountall:/proc/filesystems: no such file or directory > init: mountall main process (1284) killed by SEGV signal > rm.: cannot remove `/forcefsck': Read-only file system > init: mountall post-stop process (1285) terminated with status 1 > This is bug 447947, I uploaded a fix for that last night. Scott -- Scott James Remnant sc...@ubuntu.com -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 the binary only; no config files were changed or other steps taken. 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 something that simply won't be addressed. Here's what appears on my console at the point of failure: mountall:/proc/filesystems: no such file or directory init: mountall main process (1284) killed by SEGV signal rm.: cannot remove `/forcefsck': Read-only file system init: mountall post-stop process (1285) terminated with status 1 It then goes on to find the keyboard and a usb card reader (four-slot, so all this takes about 20 lines) and, when I would expect it to mount the root filesystem, nothing happens. It just hangs. -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 - 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
@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.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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 not long after mountall rears its ugly head. Started at about the same time others began seeing problems. -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 the boot process still freezes at the same moment, immeadiately after the messages about mounting. -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 out of place to you? ** Attachment added: "My current fstab" http://launchpadlibrarian.net/33427743/fstab -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 was returned with 'command not found'. I ran 'ls /sbin' and found that there is no file named upstart, but there is upstart-dev-bridge. I tried 'exec /sbin /upstart-dev-bridge' and got a connection refused error again. So then I tried just running the command 'mountall --debug' and got the same error: - # mountall --debug mountall: Could not connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused - I'm not sure if this is normal or not, but I tried editing my /etc/fstab because I got errors about not having an ending newline, so I tried to 'echo "\n" >> /etc/fstab' and I was returned with an error that said my filesystem was read-only. Could this be the reason I cannot boot? 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 to be running. If you need to boot with an emergency shell, try following: http://upstart.ubuntu.com/wiki/OMGBroken (I really should make that a built-in feature :p) Scott -- Scott James Remnant sc...@ubuntu.com -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447747] Re: karmic - mountall fails to mount filesystem on boot
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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
