** Changed in: mountall (Ubuntu)
Status: Fix Committed => Fix Released
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: mountall (Ubuntu)
Status: Fix Released => Fix Committed
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Sorry if this is the wrong place to post this, I'm posting here as this
relates directly to my current problem, and I don't see a related forum
thread.
I'm also having this exact same problem. This isn't mentioned as a
possible problem here http://www.ubuntu.com/getubuntu/releasenotes/910
- if it
** Changed in: mountall (Ubuntu)
Assignee: nickisbored (nickd113) => (unassigned)
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) => nickisbored (nickd113)
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Sorry for the bump (I did waited for 2 weeks) but can anyone respond?
Re-updated all (today - 17.11.2009) and still can't boot 9.10 on xen.
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You received this bug notification because you are a member of
Still on the original bug (*), still referring to my 9.10 as xen guest
on 8.04.3 (all 32bit/i386)
After full-upgrade of both host and guest (guest via xen-update-image.
similar to chrooting and upgrading) problem still exist.
I see people referring here to upgrading/downgrading to version
0.1.4/
I ran the above - it went through the download process and said it had
been upgraded.
Still boots in to a black screen.
Error message is "init: spreadahead process (2xxx) terminated with
status 1"
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You
I'm guessing I try:
Ctrl + Alt + F1
Then:
$ sudo apt-get update
$ sudo apt-get upgrade
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
At risk of being told off, I think I may be experiencing the same
problem ;)
After the upgrade from 9.04 to 9.10 I get past the splash screen and
then I get something like "stayahead process terminated" and then just a
black screen.
I'm not exactly a Linux noob but I'm wondering what steps could
I also have this problem.
My install was as a VM on a XEN server (running on ubuntu server 8.04).
The installation was by debootstrap.
I had to link gutsy's scripts to karmic to make it work at all but I
don't believe this is the cause because all ubuntu dist's are linked to
gutsy.
Since the st
> Booting from USB drive and downgrading it to 0.1.8 makes the problem go away.
Same here.. how do I upgrade or downgrade the package from live cd?
Help please.. It's more than a week that I'm stuck to Vista.. It's really
frustrating.
--
init: mountall main process terminated with status 1
https
Ok mr grumpy. I'll try to get the os up and get apport running.
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Wladimir: please do not re-open *somebody else's bug*. From the brief
description above, you clearly have a completely different problem! For
you, mountall is actually crashing with SIGSEGV. Use "ubuntu-bug
mountall" to report the bug. Ideally if you can boot into your desktop,
apport will noti
Same here as Wladimir Mutel has. Can't boot any of my kernels. Happened
after I ran upgrade today
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Just have had this behaviour after upgrading my Ubuntu 9.10 (32-bit, on ASUS
Z99Le laptop) today morning and rebooting
(retyping last console lines by hand) :
Done.
Begin: Running /scripts/init-bottom ...
Done.
init: mountall main process (382) killed by SEGV signal
rm: cannot remove `/forcefsck
Thanks Serkan.
Note to others, if you are still having problems, you have a different
but to Serkan. Please file new bugs so we can triage your problems
independently.
** Changed in: mountall (Ubuntu)
Status: New => Fix Released
--
init: mountall main process terminated with status 1
ht
version 0.1.5 fixes this for me
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
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
http
Just updated to version 0.1.4 (among other updates) and that seems to
fix it.
Of course I had to boot from a USB stick and chroot to the environment
on the harddisk to fix it. Would be nice if we could somehow come up
with something along the line how Opensolaris handles updates: ZFS
snapshot and
Actually, my laptop gives these messages but never lets me have a shell,
so it maybe something else, ill investigate further tomorrow
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You received this bug notification because you are a member of Ubunt
+1 here too, unable to boot, can't get to the grub menu unfortunately no
menu.lst and grub.cfg says not to edit it...should I yield it's advice?
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You received this bug notification because you are a memb
+1
karmic (x86_64 & ext3 rootfs) and karmic-netbook-remix (i386 & ext4
rootfs)
On the x86_64 I was able to get things going by booting through
maintenance mode and resuming normal boot.
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
You received t
forgot to add, its karmic amd64
--
init: mountall main process terminated with status 1
https://bugs.launchpad.net/bugs/430374
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
http
23 matches
Mail list logo
