** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261730
Title:
/dev/sda1 must be recovered on every boot
To manage notifications about this bug go to:
In 14.10 amd64, mountall keeps running, causing init to keep
/var/log/upstart/mountall.log open for writing, which prevents root from
being remounted read-only.
These things are easy to examine by adding a /bin/sh line to /etc/init.d/reboot
in do_stop() before reboot -d -f -i. Then when you
I have 14.04 LTS running as a virtual machine which I upgrade from 12.02 LTS
and I do now see the error too on every boot.
Thus I think it is not the disk but some other cause which leads to this error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: upstart (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/1261730
Title:
/dev/sda1 must be recovered on every boot
To manage notifications about
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261730
Title:
/dev/sda1 must be recovered on every boot
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (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/1261730
Title:
I have figured out a little more: On removing mounted and on the
start stanza the recovery doesn't appear anymore. But this still leaves
the question why this should cause such a behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I could debug it down to a testcase. Just create the file
/etc/init/test.conf with the following lines:
start on mounted and stopped mounted-tmp
exec mkdir -p /tmp/no-journal
After a reboot the recovery will happen. If you comment out the exec stanza all
is fine again. But I don't know how
Why are you filing this bug against mountall? It's not mountall that's
causing the filesystem to fail to unmount cleanly before reboot.
I'm also wondering why it isn't telling me how many inodes were repaired (I
remember to have seen this number on real recoveries a while ago).
Not in the
Why are you filing this bug against mountall? It's not mountall that's
causing the filesystem to fail to unmount cleanly before reboot.
Which package should it be assigned then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Tue, Dec 17, 2013 at 07:30:17PM -, Sworddragon wrote:
Which package should it be assigned then?
That depends on what's causing your disk to not be cleanly remounted
read-only on shutdown. Do you get any error messages on shutdown if booted
without 'splash'?
--
You received this bug
11 matches
Mail list logo
