Ubuntu
eglibc package

libc6:amd64 general error mounting filesystems

Asked by Bensode

Not sure how to or if I should submit a bug report so I thought I'd ask here. I found a package in apt-get upgrade this afternoon (libc6) that when it installs and begins "Setting up libc6:amd64 (2.19-0ubuntu6.9) ..." I get spammed (in staggering lines) on console:

General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and reboot the system.
Give root password for maintenance (or type Control-D to continue):

I've been able to reproduce by just upgrading the libc6 package only. Control-D reboots and the problem persists and login is hampered by the same message and every key on the keyboard is followed with a carriage return. If I enter the password quickly enough, I get a shell but then the same symptom of every key press is followed by a carriage return.

This also happens at the console if I upgrade from a remote shell. What information can I gather and provide to help identify the problem? It's a VM and I took a snapshot prior to upgrading so I am able to revert and reproduce indefinitely. Thanks!

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu eglibc Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said : 		#1

Strange.

For diagnostics please provide the output of the following commands:

uname -a
lsb_release -crid
apt-cache policy libc6:amd64
mount
sudo dpkg --audit

Revision history for this message
Bensode (bensode) said : 		#2

Sure thing!

uname -a:
Linux zhubv2-template 3.16.0-62-generic #83~14.04.1-Ubuntu SMP Fri Feb 26 22:52:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -crid:
Distributor ID: Ubuntu
Description: Ubuntu 14.04.4 LTS
Release: 14.04
Codename: trusty

apt-cache policy libc6:amd64:
libc6:
  Installed: 2.19-0ubuntu6.9
  Candidate: 2.19-0ubuntu6.9
  Version table:
 *** 2.19-0ubuntu6.9 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
        100 /var/lib/dpkg/status
     2.19-0ubuntu6 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

mount:
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)

sudo dpkg --audit:
(no results)

Revision history for this message
Manfred Hampl (m-hampl) said : 		#3

Just ideas:

1. Such error messages can be caused by file system errors, you should try performing a fsck on the /dev/sda1 partition
2. It could be useful to find out at what step of the installation of libc6:amd64 the error starts. I assume it is during the postinst script. If executing the steps in the postinst script one by one raises the error at a certain line, the related program would be the culprit (and not necessarily libc6 itself).
3. Does the system behave well in all other aspects? Booting without problems, but just crashing with the setup of libc6?
4. Can you boot into an older kernel, and does this show the same problem?

Revision history for this message
Bensode (bensode) said : 		#4

I'll run the fsck this evening. Do you have any suggestions on how to step through the installation of libc6:amd64 via apt to determine where exactly it's happening? The system behaves normally, reboots and all other services function as expected. I will migrate the VM to another host and then also migrate storage to an alternate datastore after running the fsck. Older kernel might take me a bit of time after these other tasks but I can perform that as well and get back next week with the results.

Can you help with this problem?

Provide an answer of your own, or ask Bensode for more information if necessary.

To post a message you must log in.