[SOLVED] Ubuntu Lucid-Maverick upgrade fails. What should I do?

r.osmanov · 02-14-2011, 12:46 AM

Hi there!

Some time ago I launched the upgrade, and it had been interrupted by a network error(ISP). That's what I've got in sources.list:

Code:

$ grep ^deb /etc/apt/sources.list
deb http://uz.archive.ubuntu.com/ubuntu/ maverick main restricted
deb http://uz.archive.ubuntu.com/ubuntu/ maverick-updates main restricted
deb http://uz.archive.ubuntu.com/ubuntu/ maverick universe
deb http://uz.archive.ubuntu.com/ubuntu/ maverick-updates universe
deb http://uz.archive.ubuntu.com/ubuntu/ maverick multiverse
deb http://uz.archive.ubuntu.com/ubuntu/ maverick-updates multiverse
deb http://archive.canonical.com/ubuntu maverick partner
deb http://security.ubuntu.com/ubuntu maverick-security main restricted
deb http://security.ubuntu.com/ubuntu maverick-security universe
deb http://security.ubuntu.com/ubuntu maverick-security multiverse
deb http://ubuntu.uz/ubuntu/ lucid main universe
deb http://security.ubuntu.com/ubuntu/ lucid-security universe main
deb http://ubuntu.uz/ubuntu/ lucid-updates universe main

And now I cannot figure out what namely causes the error:

Code:

ruslan@mega-038: /tmp $ sudo do-release-upgrade 
Checking for a new ubuntu release
Done Upgrade tool signature
Done Upgrade tool  
Done downloading            
extracting 'maverick.tar.gz'
authenticate 'maverick.tar.gz' against 'maverick.tar.gz.gpg' 
tar: Removing leading `/' from member names

Reading cache

Checking package manager
Reading package lists... Done
Building dependency tree        
Reading state information... Done
Building data structures... Done 
Reading package lists... Done    
Building dependency tree          
Reading state information... Done
Building data structures... Done 

Updating repository information
WARNING: Failed to read mirror file
97% [Working] 
Checking package manager
Reading package lists... Done    
Building dependency tree          
Reading state information... Done
Building data structures... Done 

Calculating the changes

Calculating the changes

Could not calculate the upgrade 

An unresolvable problem occurred while calculating the upgrade: 
E:Error, pkgProblemResolver::Resolve generated breaks, this may be 
caused by held packages. 

This can be caused by: 
* Upgrading to a pre-release version of Ubuntu 
* Running the current pre-release version of Ubuntu 
* Unofficial software packages not provided by Ubuntu 

If none of this applies, then please report this bug against the 
'update-manager' package and include the files in 
/var/log/dist-upgrade/ in the bug report. 


Restoring original system state

Aborting
Reading package lists... Done    
Building dependency tree          
Reading state information... Done
Building data structures... Done

Code:

$ sudo tail -n 20 /var/log/dist-upgrade/main.log
2011-02-14 09:23:51,318 DEBUG entry 'deb http://security.ubuntu.com/ubuntu maverick-security universe' is already set to new dist
2011-02-14 09:23:51,318 DEBUG examining: 'deb http://security.ubuntu.com/ubuntu maverick-security multiverse'
2011-02-14 09:23:51,319 DEBUG entry 'deb http://security.ubuntu.com/ubuntu maverick-security multiverse' is already set to new dist
2011-02-14 09:23:51,319 DEBUG examining: 'deb http://ubuntu.uz/ubuntu/ lucid main universe'
2011-02-14 09:23:51,321 DEBUG entry 'deb http://ubuntu.uz/ubuntu/ maverick main universe' updated to new dist
2011-02-14 09:23:51,321 DEBUG examining: 'deb http://security.ubuntu.com/ubuntu/ lucid-security universe main'
2011-02-14 09:23:51,322 DEBUG entry 'deb http://security.ubuntu.com/ubuntu/ maverick-security universe main' updated to new dist
2011-02-14 09:23:51,322 DEBUG examining: 'deb http://ubuntu.uz/ubuntu/ lucid-updates universe main'
2011-02-14 09:23:51,324 DEBUG entry 'deb http://ubuntu.uz/ubuntu/ maverick-updates universe main' updated to new dist
2011-02-14 09:23:51,342 DEBUG running doUpdate() (showErrors=True)
2011-02-14 09:28:09,746 DEBUG openCache()
2011-02-14 09:28:09,747 DEBUG failed to SystemUnLock() (E:Not locked) 
2011-02-14 09:28:13,069 DEBUG /openCache(), new cache size 32495
2011-02-14 09:28:13,070 DEBUG needServerMode(): run in 'desktop' mode, (because of pkg 'ubuntu-desktop')
2011-02-14 09:29:14,500 ERROR Dist-upgrade failed: 'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.'
2011-02-14 09:29:14,500 DEBUG abort called
2011-02-14 09:29:14,503 DEBUG openCache()
2011-02-14 09:29:14,504 DEBUG failed to SystemUnLock() (E:Not locked) 
2011-02-14 09:29:19,581 DEBUG /openCache(), new cache size 33703
2011-02-14 09:29:19,582 DEBUG enabling apt cron job

Code:

$ sudo tail -n 20 /var/log/dist-upgrade/apt.log 
[sudo] password for ruslan: 
  Considering xserver-xorg-core 78 as a solution to xserver-xorg-video-nouveau 2
  Holding Back xserver-xorg-video-nouveau rather than change xorg-video-abi-8.0
Investigating libdrm-nouveau1
Package libdrm-nouveau1 has broken Breaks on xserver-xorg-video-nouveau
  Considering xserver-xorg-video-nouveau 2 as a solution to libdrm-nouveau1 15
  Upgrading xserver-xorg-video-nouveau due to Breaks field in libdrm-nouveau1
Investigating xserver-xorg-video-nouveau
Package xserver-xorg-video-nouveau has broken Depends on xorg-video-abi-8.0
  Considering xserver-xorg-core 78 as a solution to xserver-xorg-video-nouveau 2
  Holding Back xserver-xorg-video-nouveau rather than change xorg-video-abi-8.0
Investigating libdrm-nouveau1
Package libdrm-nouveau1 has broken Breaks on xserver-xorg-video-nouveau
  Considering xserver-xorg-video-nouveau 2 as a solution to libdrm-nouveau1 15
  Upgrading xserver-xorg-video-nouveau due to Breaks field in libdrm-nouveau1
Investigating xserver-xorg-video-nouveau
Package xserver-xorg-video-nouveau has broken Depends on xorg-video-abi-8.0
  Considering xserver-xorg-core 78 as a solution to xserver-xorg-video-nouveau 2
  Holding Back xserver-xorg-video-nouveau rather than change xorg-video-abi-8.0
Done
Log time: 2011-02-14 10:53:02.690378

Well, I see that something wrong in xserver-xorg*. I tried

Code:

$ sudo dpkg-reconfigure --force xserver-xorg

But it does nothing.

Should I reinstall xserver-xorg, remove maverick deb entries from /etc/apt/sources.list, or do something else?

Regards.

Kenny_Strawn · 02-14-2011, 01:21 AM

You can always try upgrading via apt-get in a terminal:

Code:

sudo su

echo "deb http://us.archive.ubuntu.com/ubuntu maverick main restricted universe multiverse" >> /etc/apt/sources.list
echo "deb http://security.ubuntu.com/ubuntu maverick-security main restricted universe multiverse" >> /etc/apt/sources.list
echo "deb http://us.archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse" >> /etc/apt/sources.list
echo "deb http://us.archive.ubuntu.com/ubuntu maverick-proposed main restricted universe multiverse" >> /etc/apt/sources.list
echo "deb http://us.archive.ubuntu.com/ubuntu maverick-backports main restricted universe multiverse" >> /etc/apt/sources.list

apt-get update && apt-get dist-upgrade
exit

Of course, you also need to be connected to the Internet to do this.

r.osmanov · 02-14-2011, 11:56 PM

Quote:

Originally Posted by Kenny_Strawn

...

Code:

sudo su

echo "deb http://us.archive.ubuntu.com/ubuntu maverick main restricted universe multiverse" >> /etc/apt/sources.list
echo "deb http://security.ubuntu.com/ubuntu maverick-security main restricted universe multiverse" >> /etc/apt/sources.list
echo "deb http://us.archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse" >> /etc/apt/sources.list
echo "deb http://us.archive.ubuntu.com/ubuntu maverick-proposed main restricted universe multiverse" >> /etc/apt/sources.list
echo "deb http://us.archive.ubuntu.com/ubuntu maverick-backports main restricted universe multiverse" >> /etc/apt/sources.list

apt-get update && apt-get dist-upgrade
exit

...

Update Manager have already done this, however leaving Lucid entries.
I tried remove maverick lines, update and upgrade. Everything was OK until update manager began to fetch new packages...:

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade:
E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

This can be caused by:
* Upgrading to a pre-release version of Ubuntu
* Running the current pre-release version of Ubuntu
* Unofficial software packages not provided by Ubuntu

If none of this applies, then please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bug report.

It seems, I gotta remove lucid sources and just update maverick packages... I'll post results.

Thank you.

syg00 · 02-15-2011, 12:55 AM

When I was a more active Ubuntu user, I found the upgrade always seemed to cause problems. I moved /home off to a separate partition and created two partitions for the Ubuntu "system". I would install into one, and use the pre-defined /home. Next release I would install into the other partition, and again use the common /home. If problems, it was a simple matter to boot from the old "system". After that simply flip-flop the system partitions.

Means you have to re-install any locally installed packages, but easy enough to generate a list.

r.osmanov · 02-15-2011, 11:30 PM

Quote:

Originally Posted by syg00

When I was a more active Ubuntu user, I found the upgrade always seemed to cause problems. I moved /home off to a separate partition and created two partitions for the Ubuntu "system". I would install into one, and use the pre-defined /home. Next release I would install into the other partition, and again use the common /home. If problems, it was a simple matter to boot from the old "system". After that simply flip-flop the system partitions.

Means you have to re-install any locally installed packages, but easy enough to generate a list.

Hmm. I've the following disk space usage:

Code:

ruslan@mega-038: /var/www/s3 $ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb8              63G   19G   41G  32% /
none                  999M  304K  999M   1% /dev
none                 1003M  252K 1003M   1% /dev/shm
none                 1003M  364K 1003M   1% /var/run
none                 1003M     0 1003M   0% /var/lock
none                 1003M     0 1003M   0% /lib/init/rw
/dev/sda1              37G  7.5G   28G  22% /backup
/dev/sdb6             2.8G  125M  2.5G   5% /tmp
/dev/sdb5             280M   83M  183M  32% /boot
/dev/sdb7              35G   14G   20G  41% /home
/dev/sdc1             7.6G  2.7G  5.0G  35% /media/8GFLASH

and the following partition layout:

Code:

ruslan@mega-038: /var/www/s3 $ sudo parted -l 
Model: ATA WDC WD800BB-55JH (scsi)
Disk /dev/sda: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      32.3kB  40.0GB  40.0GB  primary  ext4


Model: ATA SAMSUNG HD161HJ (scsi)
Disk /dev/sdb: 160GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type      File system     Flags
 2      32.3kB  160GB   160GB   extended
10      96.8kB  1439MB  1439MB  logical   linux-swap(v1)
 5      1439MB  1752MB  313MB   logical   ext2            boot
 6      32.0GB  35.0GB  3002MB  logical   ext3
 7      35.0GB  72.1GB  37.1GB  logical   ext3
 8      87.0GB  156GB   68.5GB  logical   ext3
 9      156GB   160GB   4499MB  logical   linux-swap(v1)


Model: A-DATA USB Flash Drive (scsi)
Disk /dev/sdc: 8087MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      31.7kB  8086MB  8086MB  primary  fat32        boot, lba

There is unallocated space between /dev/sdb5 and /dev/sdb6 of about 28G.
As it turns, I should:

create another /home partition there
reboot and log in as root
unmount current /home partition
update and upgrade the system

Right?

syg00 · 02-16-2011, 12:34 AM

Nope - the idea is to have two "system" partitions (basically all except /home) - and you do a fresh (complete) install - not upgrade - each release.
There is no need for another /home - the idea is to (always) use the same one. Ubuntu handles this well - even if you use the /home on an later release, you can always reboot back to the prior release, using the same /home. Very handy.
You can also use the same swap, but as Ubuntu uses UUID this can make the other system un-bootable. I don't use UUID for swap for this reason.
You assign the shared partitions to appropriate mount point(s) during the new install.

Your setup as is creates some issues:
- why do you have /tmp on a real partition ?. You won't want to have persistent data in there if "flip-flopping" releases like I'm suggesting. Consider puting /tmp on tmpfs - unless you need /tmp to persist across re-boot, in which case you might need two /tmp partitions. Can't see why though.
- /boot as a separate partition is a real management problem in this setup. I do it on some (most) systems, but you really need to be careful with automatic update systems. And grub2 complains if installed into a partition boot record. Can be done, but needs thought - consider just having /boot under the / (root) rather than in a separate partition.

r.osmanov · 02-16-2011, 03:13 AM

Quote:

Originally Posted by syg00

Nope - the idea is to have two "system" partitions (basically all except /home) - and you do a fresh (complete) install - not upgrade - each release.
There is no need for another /home - the idea is to (always) use the same one. Ubuntu handles this well - even if you use the /home on an later release, you can always reboot back to the prior release, using the same /home. Very handy.
You can also use the same swap, but as Ubuntu uses UUID this can make the other system un-bootable. I don't use UUID for swap for this reason.
You assign the shared partitions to appropriate mount point(s) during the new install.

Your setup as is creates some issues:
- why do you have /tmp on a real partition ?. You won't want to have persistent data in there if "flip-flopping" releases like I'm suggesting. Consider puting /tmp on tmpfs - unless you need /tmp to persist across re-boot, in which case you might need two /tmp partitions. Can't see why though.
- /boot as a separate partition is a real management problem in this setup. I do it on some (most) systems, but you really need to be careful with automatic update systems. And grub2 complains if installed into a partition boot record. Can be done, but needs thought - consider just having /boot under the / (root) rather than in a separate partition.

To keep two separate systems for updates... is a stuff to consider. However, idea to keep a "redundant" OS doesn't appeal to me.

I agree, my partitions don't look perfect

. I'd follow your suggestion about tmpfs and /boot.
Though, I cannot find something wrong with the separate /boot partition.

Could it be somehow caused by umask? Mine is 0027.

I tried to change repository mirrors. But the same issue.

Thank you!

syg00 · 02-16-2011, 08:05 AM

My suggestion were merely for you to consider if going the route of having two separate systems (for updates). If you don't intend to proceed that way, no real need to make those changes - especially /boot which could get messy.

r.osmanov · 02-17-2011, 10:52 PM

Replaced contents of /etc/apt/sources.list with

Code:

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.

deb http://archive.ubuntu.com/ubuntu maverick main restricted
deb-src http://archive.ubuntu.com/ubuntu maverick main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://archive.ubuntu.com/ubuntu maverick-updates main restricted
deb-src http://archive.ubuntu.com/ubuntu maverick-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu maverick universe
deb-src http://archive.ubuntu.com/ubuntu maverick universe
deb http://archive.ubuntu.com/ubuntu maverick-updates universe
deb-src http://archive.ubuntu.com/ubuntu maverick-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://archive.ubuntu.com/ubuntu maverick multiverse
deb-src http://archive.ubuntu.com/ubuntu maverick multiverse
deb http://archive.ubuntu.com/ubuntu maverick-updates multiverse
deb-src http://archive.ubuntu.com/ubuntu maverick-updates multiverse

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
# deb-src http://us.archive.ubuntu.com/ubuntu/ maverick-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
deb-src http://archive.canonical.com/ubuntu maverick partner

deb http://archive.ubuntu.com/ubuntu maverick-security main restricted
deb-src http://archive.ubuntu.com/ubuntu maverick-security main restricted
deb http://archive.ubuntu.com/ubuntu maverick-security universe
deb-src http://archive.ubuntu.com/ubuntu maverick-security universe
deb http://archive.ubuntu.com/ubuntu maverick-security multiverse
deb-src http://archive.ubuntu.com/ubuntu maverick-security multiverse

and made:

Code:

$ sudo apt-get clean
$ sudo apt-get autoremove
$ sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade

Thank you!