Pacman does not upgrade (Solved)

lilsirecho · 2010-04-09 17:36:16

[root@n6re ~]# pacman -S kernel26
resolving dependencies...
looking for inter-conflicts...

Targets (35): linux-api-headers-2.6.33.1-1
tzdata-2010h-1 glibc-2.11.1-2
ncurses-5.7-2.1 readline-6.1.002-1
bash-4.1.005-1 gcc-libs-4.4.3-2
db-4.8.26-1 zlib-1.2.4-1
cracklib-2.8.13-2 pam-1.1.1-1
shadow-4.1.4.2-2 attr-2.4.44-1
acl-2.2.48-1 gmp-5.0.1-1 libcap-2.1
coreutils-8.4-2
kernel26-firmware-2.6.33.2-1
module-init-tools-3.11.1-2
mkinitcpio-busybox-1.15.3-5
util-linux-ng-2.17.1-1
gen-init-cpio-2.6.32-1 findutils-4.4
sed-4.2.1-1 pcre-8.02-1 grep-2.6.3-
filesystem-2010.02-4 libusb-0.1.12-4
glib2-2.24.0-1 udev-151-3 file-5.04
gzip-1.4-1 which-2.20-2
mkinitcpio-0.6.3-1 kernel26-2.6.33.2

Total Download Size: 0.00 MB
Total Installed Size: 235.73 MB

The items above have been downloaded but pacman reports all are in the system already (not true) and none were upgraded.

Present kernel is 32.

Cannot display pacman -Q.

Recently installed pacman-cage.

Have I missed some upgrade to pacman?

Last edited by lilsirecho (2010-04-14 05:23:52)

chpln · 2010-04-09 22:34:06

Seems unlikely that it's being caused by missed a pacman update, though you can check with pacman --version (should be 3.3.3).

I'd try 'pt-pacman-uncage && pacman -Syy' - one thing that comes to mind is the loopback fs for pacman-cage not being large enough. You can check whether this might be the case with 'df -h /var/lib/pacman'.

lilsirecho · 2010-04-09 23:41:18

chpin;

Thanks for the comments.

I now have a further problem after forcing the upgrade.

The device by uuid for my HDD is verified by my backup drive with the command BLKID.

However, the drive with that uuid does not boot giving the error:

Unable to determine the major/minor number of root device...(the uuid is correctly stated).

The boot is halted with ramfs prompt.

I ran e2fsck on all partitions correcting what errors showed.

The drive consistently fails with the above error.

chpln · 2010-04-10 00:48:36

There has been a bug-report recently opened for this: http://bugs.archlinux.org/task/18810. Seems a possible solution has just been posted there.

lilsirecho · 2010-04-10 02:44:19

Posted solution doesn't work.

lilsirecho · 2010-04-11 15:47:24

FS#18810 is assigned to no one!

flamelab · 2010-04-11 16:59:32

Ηmm, I'm pretty sure that there has been damage to /var/lib/pacman

Is anything in there ?

lilsirecho · 2010-04-11 17:51:17

flamelab:

There is 696 packages in /var/lib/pacman/local........

EDIT: I apologize for the shift in the problem which is now that the system doesn't boot due to uuid not being recognized. This occurred when using the force command to enable pacman upgrade to kernel 33.

Last edited by lilsirecho (2010-04-11 18:10:10)

lilsirecho · 2010-04-14 05:22:49

Solved the problem by re-installing (dd)from backup drive having no pacman-cage installed. This guaranteed pacman db would be recognized in the problem drive.

Pacman then properly installed kernel 33 in the main drive and the system responds correctly.

SleepyFloyd · 2010-04-14 10:30:23

I had the same problem two days ago, caused by a faulty pacman upgrade. Disk ran full while installing a plenthora of updates on a very outdated box.
pacman -Qi wouldn't recognoze anything, pretty much breaking the whole system. Did a quick reinstall and everything is fine now.

Arch Linux

#1 2010-04-09 17:36:16

Pacman does not upgrade (Solved)

#2 2010-04-09 22:34:06

Re: Pacman does not upgrade (Solved)

#3 2010-04-09 23:41:18

Re: Pacman does not upgrade (Solved)

#4 2010-04-10 00:48:36

Re: Pacman does not upgrade (Solved)

#5 2010-04-10 02:44:19

Re: Pacman does not upgrade (Solved)

#6 2010-04-11 15:47:24

Re: Pacman does not upgrade (Solved)

#7 2010-04-11 16:59:32

Re: Pacman does not upgrade (Solved)

#8 2010-04-11 17:51:17

Re: Pacman does not upgrade (Solved)

#9 2010-04-14 05:22:49

Re: Pacman does not upgrade (Solved)

#10 2010-04-14 10:30:23

Re: Pacman does not upgrade (Solved)

Board footer