A friend asked me to look at her laptop (via TeamViewer) after she noticed that Rhythmbox wouldn't open. Here's what I learned:
Rhythmbox and Update Manager crash with a bus error:
$ rhythmbox (rhythmbox:3032): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Bus error $ update-manager Bus error
There is a cyclical Apt update error:
$ sudo apt-get update … W: Duplicate sources.list entry http://archive.canonical.com/ubuntu/ natty/partner i386 Packages (/var/lib/apt/lists/archive.canonical.com_ubuntu_dists_natty_partner_binary-i386_Packages) W: You may want to run apt-get update to correct these problems
The package database is corrupted:
$ sudo apt-get install debsums … Selecting previously deselected package debsums. (Reading database ... 95%dpkg: unrecoverable fatal error, aborting: reading files list for package 'linux-image-2.6.35-28-generic': Input/output error E: Sub-process /usr/bin/dpkg returned an error code (2)
See the truncation of
The root filesystem became read-only while I was investigating the Apt issues:
$ touch test touch: cannot touch `test': Read-only file system $ mount /dev/sda5 on / type ext4 (rw,errors=remount-ro,user_xattr,commit=0) … mount: warning: /etc/mtab is not writable (e.g. read-only filesystem). It's possible that information reported by mount(8) is not up to date. For actual information about system mount points check the /proc/mounts file.
The disk isn't full:
$ df -h /dev/sda5 Filesystem Size Used Avail Use% Mounted on /dev/sda5 108G 64G 40G 62% /
The SMART status displayed in Disk Utility is "Disk has a few bad sectors".
After rebooting, the system failed to boot with the message
Errors found while checking disk drive for /.
What is the root cause of this, and how can I be sure?