package udev 204-5ubuntu20.20 failed to install/upgrade: pre-dependency problem - not installing udev

Bug #1649728 reported by Nico van der Horn
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Upgrading Ubuntu Server 12.04 LTS using do-release-upgrade.
Normal update/upgrade without problems/stable within release 12, including reboot.

During the upgrade I noticed "xenial" in the path-names, assuming the target would be 16.04 LTS.

But after 15min I noticed the following:

-----
Errors were encountered while processing:
 /var/cache/apt/archives/lvm2_2.02.133-1ubuntu10_amd64.deb
 /var/cache/apt/archives/udev_229-4ubuntu12_amd64.deb
Error in function:

SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/problem_report.py", line 416, in add_to_existing
    self.write(f)
  File "/usr/lib/python3/dist-packages/problem_report.py", line 369, in write
    block = f.read(1048576)
  File "/usr/lib/python3.4/codecs.py", line 319, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte

Original exception was:
SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
-----

Given the URL in the text, I landed here.

At the next choice, I selected to continue, effectively ignoring more problems with udev ?

I tried to recover by "apt-get -f install", later "apt full-upgrade" and it looked ok.
Unfortunately after reboot the server responded only to ping, as far as I could see nothing else.

I am working remotely with the server of my client, they start working at 08:00 CET.

Going for a short sleep now, as I'm afraid having to travel to the client and continue on-site.

If you can provide me with hits, I would apreciate that a lot.

Thanks in advance,

Nico

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu20.20
ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
Uname: Linux 3.2.0-58-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Tue Dec 13 20:57:14 2016
DuplicateSignature: package:udev:204-5ubuntu20.20:pre-dependency problem - not installing udev
ErrorMessage: pre-dependency problem - not installing udev
InstallationDate: Installed on 2012-01-16 (1793 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 051d:0003 American Power Conversion UPS
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU PRIMERGY TX100 S3
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-58-generic root=/dev/mapper/storage-root ro
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.0.1ubuntu2.15
SourcePackage: systemd
Title: package udev 204-5ubuntu20.20 failed to install/upgrade: pre-dependency problem - not installing udev
UpgradeStatus: Upgraded to trusty on 2016-12-13 (0 days ago)
dmi.bios.date: 12/01/2011
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V4.6.4.1 R1.6.0.0 for D3009-A1x
dmi.board.name: D3009-A1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D3009-A1
dmi.chassis.type: 6
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: TX100S3
dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.4.1R1.6.0.0forD3009-A1x:bd12/01/2011:svnFUJITSU:pnPRIMERGYTX100S3:pvr:rvnFUJITSU:rnD3009-A1:rvrS26361-D3009-A1:cvnFUJITSU:ct6:cvrTX100S3:
dmi.product.name: PRIMERGY TX100 S3
dmi.sys.vendor: FUJITSU

Revision history for this message
Nico van der Horn (0i0o) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Nico van der Horn (0i0o) wrote :

Today I went on-site and concluded that the boot hung on a problem with cryptswap1.
At this machine we do not need swap-encryption, so I changed in a standard setup.
This solved the problem of not completing the boot-sequence.
In addition I had to fix a few minor problems, like kernel version did not changed.
Case closed, thanks for your time.

Nico van der Horn (0i0o)
description: updated
Dan Streetman (ddstreet)
Changed in systemd (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.