v5.0-v5.5 upgrade crash, now cannot get back into system

Project:Trisquel
Version:5.5
Component:Installer
Category:bug report
Priority:critical
Assigned:Unassigned
Status:closed
Description

Hi,

I have been using Trisquel for some time, v4.0, v4.5, v5.0.
Very excited about the chance the updated nouveau drivers might finally make my nvidia work properly with OpenGL so I pressed the 5.5 upgrade button on the update manager.

Everything was going cool, downloads done, and was installing for some time, then a nasty popped up:

"Could not install '/var/cache/apt/archives/libupower-glib1_0.9.13-1_i386.deb"
Failed to sync updated files list for package libupower-glib1: input/output error

It gave me a whole list of other stuff, maybe a list of files, I can't remember. I tried to copy the text but couldn't open anything any more, and it suggested I send in a bug report.

Nothing was happening, I left it for sometime to see if it was going to repair/rollback... nothing. Locked out.
I kicked the machine in the powerpants and tried to reload. It now gets past Grub, shows green loadup curtains / Trisquel logo then goes to a black screen with the circle loading cursor. I can move the cursor around but nothing else happens. left it for 10 mins... nothing happens. Tried loading a few times, gets to the same place, nothing happens.

I tried loading up a previous version at Grub, does the same thing.
I am effectively locked out of all previous versions.

When I hit the power button a screen shows with text that looks like a loadup log showing where it had gotten to.
It's quick, but I think the last thing on the list before all the closing down stuff gets added is: "checking battery state".

With a v5.0 CD I burnt previously I can get into the "try Trisquel without installing" and so I assume I can update some files from there if need be.

I hear Trisquel has no tools for recovery / checking system integrity?

What can I do to get going again?

I am a programmer, but consider my Linux skills close to intermediate.

I really want to do the Libre thing but will need help on this one.

I have a dell Inspiron 1720 lappy, dual boot with XP (boots ok so I assume it's not a hardware issue).

This machine is my daily beast for work / development / communications and I am dead in the water.
I am using the missus v5.0 and her email addy to send this SOS.

Thanks in advance for looking at this.

Webdude.

Thu, 04/19/2012 - 06:14

Ok, so I'm learning more about Linux, and I'm loving that everything is logged.
In the syslog I get lots of these...

Apr 19 14:28:18 XXX-laptop kernel: [ 54.569314] type=1400 audit(1334809698.746:74): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=1567 comm="apparmor_parser"
Apr 19 14:28:18 XXX-laptop kernel: [ 54.573258] type=1400 audit(1334809698.750:75): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=1567 comm="apparmor_parser"
Apr 19 14:28:18 XXX-laptop kernel: [ 54.612750] type=1400 audit(1334809698.790:76): apparmor="DENIED" operation="chown" parent=1 profile="/usr/sbin/cupsd" name="/run/cups/" pid=1568 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Apr 19 14:28:18 XXX-laptop kernel: [ 54.612953] type=1400 audit(1334809698.790:77): apparmor="DENIED" operation="chown" parent=1 profile="/usr/sbin/cupsd" name="/run/cups/certs/" pid=1568 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Apr 19 14:28:18 XXX-laptop kernel: [ 54.731039] type=1400 audit(1334809698.906:78): apparmor="DENIED" operation="mknod" parent=1 profile="/usr/sbin/cupsd" name="/run/cups/printcap" pid=1568 comm="cupsd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
Apr 19 14:28:18 XXX-laptop kernel: [ 54.742882] type=1400 audit(1334809698.918:79): apparmor="DENIED" operation="mknod" parent=1 profile="/usr/sbin/cupsd" name="/run/cups/cups.sock" pid=1568 comm="cupsd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
Apr 19 14:28:18 XXX-laptop kernel: [ 54.743230] type=1400 audit(1334809698.918:80): apparmor="DENIED" operation="mknod" parent=1 profile="/usr/sbin/cupsd" name="/run/cups/cupsd.pid" pid=1568 comm="cupsd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
Apr 19 14:28:18 XXX-laptop kernel: [ 54.748846] init: cups main process (1568) terminated with status 1
Apr 19 14:28:18 XXX-laptop kernel: [ 54.748944] init: cups main process ended, respawning

Mostly all for cups and some for mysql

It sounds like what is happening here...
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/810270

Check post #18 on that page...
He mentions having a SolidStateDrive but moved his /var to somewhere else.
I too have an SSD but all the system is installed on it.

Sounds like I am closer... maybe...
anybody out there?

Cheers.

Thu, 04/19/2012 - 07:38

ok,

so this dude had a similar issue:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/810687

He...
"managed to get the service started by adding the following lines to
/etc/apparmor.d/local/usr.sbin.cupsd:

/var/run/cups/ rw,
/var/run/cups/** rw,
"

In his case it was trying to do stuff with /var/run/cups/

But in my case it's trying to do stuff to: /run/cups/
..............................and also to: /run/mysqld/

So, without knowing what I was doing, but in desperation, I closed my eyes and fiddled with the keys...

My /run/ directory is empty so I added both /run/cups/ and /run/mysqld/ directories.

Then in: /etc/apparmor.d/local/usr.sbin.cupsd: I added:
/run/cups/ rw,
/run/cups/** rw,

Then in: /etc/apparmor.d/local/usr.sbin.mysqld: I added:
/run/mysqld/ rw,
/run/mysqld/** rw,

I then rebooted and tried to get into my normal latest Linux edition, but it still hangs =(

I went back in with the bootable CD (takes ages each time), then checked the syslog... and voila! the lines and lines of cups & mysqld logs ARE gone!!!
...but why does the system still hang?
Curiously, nothing was added to the 2 directories I created.

Also, while I was typing this, the laptop was left in this hanging state for some time and when I got back to it the screen was blank. I bumped the mouse and the spinning flower(wait for it)cursor came back, so it seems the screensaver at least is working.

Also the syslog did capture 1 more round of remaining repeating messages:

Apr 19 16:06:02 XXX-laptop dbus[867]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Apr 19 16:06:02 XXX-laptop dbus[867]: [system] Activated service 'org.freedesktop.ModemManager' failed: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
Apr 19 16:08:02 XXX-laptop dbus[867]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Apr 19 16:08:02 XXX-laptop dbus[867]: [system] Activated service 'org.freedesktop.ModemManager' failed: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
Apr 19 16:09:01 XXX-laptop CRON[1428]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
Apr 19 16:10:02 XXX-laptop dbus[867]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Apr 19 16:10:02 XXX-laptop dbus[867]: [system] Activated service 'org.freedesktop.ModemManager' failed: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
Apr 19 16:12:02 XXX-laptop dbus[867]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Apr 19 16:12:02 XXX-laptop dbus[867]: [system] Activated service 'org.freedesktop.ModemManager' failed: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success

Is this the last hurdle left?

Am I almost there?

guys? girls?

anybody?

Mon, 04/23/2012 - 14:44

Did you check the integrity of the install media with the built in menu option prior to install?

Do you have a separate /home partition? Is there something of value in /home? Can you access it? (e.g. using livecd or liveusb)

Usually installs are all or nothing.

Mon, 07/30/2012 - 18:11
Status:active» needs more info
Tue, 10/23/2012 - 18:05
Status:needs more info» closed

Marking as closed after 12 weeks of "needs more info" please feel free to re-open if the required information can be provided.