[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412671
Ok, nevermind. This seems to be another issue. Namely for some reason
/home fails to mount at boot for some reason: The disk drive for /home
is not ready yet or not present. Continue to wait; or press s to skip
mounting or M for manual recovery. The workaround appears to be to
delete all LVM
The users complained that the issue re-occurred today. I remotely
upgraded the system yesterday (apt-get dist-upgrade), so its very likely
something in the upgrade process broke the system again. They will
transport me the machine today, so I will have physical access. If we
don't manage to fix it
I will confirm this from the logs when I get access to the machine, but
if I remember correctly, at least one of the updates was to libc, just
as the previous time this happened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried several reboots and several shutdowns all of which succeeded.
The issues started on January 20, after the system updates on January
19. I don't know how the Ubuntu startup system (Upstart) works, but my
guess is that one of those updates caused the race, and a subsequent
update caused the
If you prefer we can mark it Incomplete meaning we're waiting for more
info (i.e. other people running into it, or it re-occuring on the original
system) to be able to debug.
There were other known badnesses in the updates on January 20, which is
why I'm pretty sure this is in fact fix-released.
Since you're now unable to reproduce, I guess I'll mark this fix
released. Please re-open if it re-occurs.
When you say 'unable to reproduce', you did try several reboots which
all succeeded?
** Changed in: linux (Ubuntu)
Status: New = Fix Released
--
You received this bug notification
I've seen no sensitive data in the logfiles, so re-marking the bug
public.
** Information type changed from Private to Public
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: dpkg.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412671/+attachment/4302530/+files/dpkg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412671
Title:
** Attachment added: term.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412671/+attachment/4302532/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412671
Title:
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412671/+attachment/4302531/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412671
Title:
[14.04]
/var/log/upstart excluding the ureadahead logs which contained sensitive
information.
** Attachment added: var-log-upstart.tar.xz
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412671/+attachment/4302533/+files/var-log-upstart.tar.xz
** Information type changed from Public to Private
I can attach the logs, but please note that these do not cover the
events of the unsuccessful bootups, because / was mounted as read-only
and hence no logs were saved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is it possible to attach /var/log/syslog, /var/log/apt/term.log,
/var/log/dpkg.log, and a tarball of /var/log/upstart/ ? (If so, please
mark this bug private before attaching them).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bug may not be in the kernel package, but it seems very unlikely to be
in cgmanager, and more clueful people are likely to see it this way.
** Package changed: cgmanager (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
You received this bug
Bug may not be in the kernel package, but it seems very unlikely to be
in cgmanager, and more clueful people are likely to see it this way.
** Package changed: cgmanager (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
You received this bug
I remembered that another error message during boot was something about
being unable to mount /home. Since there was nothing in the logs, I
think that the boot process failed before properly mounting filesystems
from /etc/fstab.
--
You received this bug notification because you are a member of
17 matches
Mail list logo
