Yes removing this two lines fixes the issue.
I tought I was using the vanilla config file because I've tried 'apt-get
--reinstall install mountall' but apt leaved my old conf file.
sorry about that,
Matteo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Oh, so with your re-post of the adjusted job I've noticed something in
your bug report. You reported that the only output on your console was:
mkdir: can't create /dev/pts: already exists
And I didn't think this was related to the problem you were having. But
now, I realize that the 'mkdir' co
Here is the file:
# mountall - Mount filesystems on boot
#
# This helper mounts filesystems in the correct order as the devices
# and mountpoints become available.
description "Mount filesystems on boot"
start on startup
stop on starting rcS
expect daemon
task
emits virtual-filesystems
emi
On Thu, Oct 18, 2012 at 12:56:15PM -, Matteo Croce wrote:
> I have no /var/log/upstart/mountall.log
Ok. This is because of the 'console output' line. If you comment this line
out, do you get this log file on reboot?
> script
> . /etc/default/rcS
> [ -f /forcefsck ] && force_fsck="--
I have no /var/log/upstart/mountall.log
# cat /etc/init/mountall.conf
# mountall - Mount filesystems on boot
#
# This helper mounts filesystems in the correct order as the devices
# and mountpoints become available.
description "Mount filesystems on boot"
start on startup
stop on starting rc
On Wed, Oct 17, 2012 at 10:26:44PM -, Matteo Croce wrote:
> Sorry I was starting a custom kernel without initrd.
> I've retried with the ubuntu 3.5.0 one and writable /run but still no logfile
Can you attach your current /etc/init/mountall.conf file?
Do you have a /var/log/upstart/mountall.lo
Sorry I was starting a custom kernel without initrd.
I've retried with the ubuntu 3.5.0 one and writable /run but still no logfile
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064074
Title:
mounta
On Wed, Oct 17, 2012 at 09:39:58PM -, Matteo Croce wrote:
> /run is not mounted ad boot
Are you booting without an initramfs?
> I've changed it to /dev which is mounted by the kernel as devtmpfs but I
> can't see the log file at all. Maybe the mountall job isn't started at
> all?
Possible b
/run is not mounted ad boot, I've changed it to /dev which is mounted by the
kernel as devtmpfs but I can't see the log file at all.
Maybe the mountall job isn't started at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
On Tue, Oct 16, 2012 at 12:39:22AM -, Matteo Croce wrote:
> I've tried but I have no output by doing so.
> where the mountall stderr is redirected to?
It's sent to the console, as indicated by the 'console output' line in
/etc/init/mountall.conf. If this isn't working, you can try redirecting
I've tried but I have no output by doing so.
where the mountall stderr is redirected to?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064074
Title:
mountall blocks boot
To manage notifications ab
Thanks. As mentioned on IRC, please drop --verbose from the boot
options, and edit /etc/init/mountall.conf to add --verbose to the 'exec
mountall' line, and reboot again, capturing the console output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Attachment added: "boot with --verbose"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1064074/+attachment/3398339/+files/IMG_6113.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064
The mkdir output is from upstart, not from mountall. Please boot with
--verbose and capture the console output (screenshot is fine).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064074
Title:
mou
Happens on my desktop too after upgrade to quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064074
Title:
mountall blocks boot
To manage notifications about this bug go to:
https://bugs.launc
** Attachment added: "booting manually by emitting mountall signals"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1064074/+attachment/3398270/+files/IMG_6112.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I have made many photos to the boot process and how I'm actually
manually booting the pc, hope it helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064074
Title:
mountall blocks boot
To manage
** Attachment added: "boting with init=/bin/bash and opening a backup shell"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1064074/+attachment/3398269/+files/IMG_6108.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Attachment added: "the boot without splash and quiet"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1064074/+attachment/3398268/+files/IMG_6106.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Attachment added: "how the graphical boot hangs"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1064074/+attachment/3398266/+files/IMG_6102.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Attachment added: "what happens when I press ESC"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1064074/+attachment/3398267/+files/IMG_6105.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
On Sun, Oct 14, 2012 at 02:01:42AM -, Matteo Croce wrote:
> it shows "no such file or directory" when the system is hanged,
> after letting the system boot manually it's:
> drwxr-xr-x 2 root root 0 ott 14 03:29 /dev/pts
Ok, then this doesn't seem to be related to the actual problem.
But is t
it shows "no such file or directory" when the system is hanged,
after letting the system boot manually it's:
drwxr-xr-x 2 root root 0 ott 14 03:29 /dev/pts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
On Sat, Oct 13, 2012 at 07:22:12PM -, Matteo Croce wrote:
> I see: "mkdir: can't create /dev/pts: alredy exists"
Please show the output of 'ls -ld /dev/pts' on the root partition of the
affected system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I see: "mkdir: can't create /dev/pts: alredy exists"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064074
Title:
mountall blocks boot
To manage notifications about this bug go to:
https://bugs.lau
On Wed, Oct 10, 2012 at 08:52:18AM -, Matteo Croce wrote:
> I don't use splash, I boot without 'splash' and 'quiet'.
> All I see is the kernel mounting root (mounted ext4 on /dev/sda1 etc.), then
> "Freeing unused kernel memory" then stop.
> this is why I debugged it via a second terminal.
Ha
Ok maybe it's not a mountall bug, but if I start mountall by hand, or if
I emit its signals the system starts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064074
Title:
mountall blocks boot
To ma
I don't use splash, I boot without 'splash' and 'quiet'.
All I see is the kernel mounting root (mounted ext4 on /dev/sda1 etc.), then
"Freeing unused kernel memory" then stop.
this is why I debugged it via a second terminal.
--
You received this bug notification because you are a member of Ubunt
Ok, that's a rather strange error condition for mountall. Mountall
talks to plymouth and provides regular status updates, including
information about any filesystems that are failing to mount. You
mention plymouth is running ok; how is it configured? Is this a machine
with a graphical boot splas
after mounting the roo filesystem the boot stops, no output
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064074
Title:
mountall blocks boot
To manage notifications about this bug go to:
https://b
On Tue, Oct 09, 2012 at 09:23:45AM -, Matteo Croce wrote:
> I start the system with init=/bin/bash
> then I do `open -c2 bash` to have another shell
> then I do `exec /sbin/init` on the first shell and on the second shell I
> watch the boot process
> the only alive process apart init, my shell
I start the system with init=/bin/bash
then I do `open -c2 bash` to have another shell
then I do `exec /sbin/init` on the first shell and on the second shell I watch
the boot process
the only alive process apart init, my shell and the kernel threads is plymoutd.
if I do `initctl list |grep -v stop
> it seems that mountall fails to spawn a few processes because PATH is
wrong.
This only shows that your init=/bin/bash shell has the wrong path.
Using init will give you the correct path.
You don't say how your system failed to boot when not using
init=/bin/bash.
** Changed in: mountall (Ubuntu
** Tags added: quantal
** Changed in: mountall (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064074
Title:
mountall blocks boot
To manage notifications a
34 matches
Mail list logo
