5

filesystem upgrade - manual intervention required

view full story
linux-howto

http://www.archlinux.org – Tom Gundersen wrote: When upgrading to filesystem-2011.12 there will be a conflict with /etc/mtab. Install the package as follows: pacman -S filesystem --force It is strongly advised to avoid the --force or -f switch as it is not safe. However, in this particular case it is needed as deleting /etc/mtab manually would break pacman. The reason for the conflict is that the file used to be generated at boot and hence not owned by any package. Now it is a symlink to /proc/self/mounts owned by filesystem. This change means that initscripts no longer requires write access to the rootfs (though other (Distributions)

sine's picture
Submitted by sine on 12/20/2011 – Made popular on 12/20/2011

Stories similar to filesystem upgrade - manual intervention required

Tom Gundersen wrote: As of filesystem-2012.6-2 the folders /var/run and /var/lock will be replaced by symlinks to /run and /run/lock, respectively. On most systems this is already the case, as initscripts create the symlinks on boot.

thanks abveritas for the information. then you must do the following:sudo pacman -Syu Y

conflict with /etc/mtab sudo pacman -S filesystem -f

sudo pacman -Syu Ycorrect?vlw fwi, Holmes

hi,i wanted to update my arch with pacman.because pacman -Syu did not work i looked at archlinux.org and found this(http://www.archlinux.org/news/filesystem-upgrade-manual-intervention-req...)and this(http://www.archlinux.org/news/the-lib-directory-becomes-a-symlink/).but i hit the wrong tab and executed:pacman -Syu --ignore glibcpacman -Suinstead of:pacman -Syu --ignore filesystem &&

No GUI after updates 31 weeks 5 hours ago

Thanks for the reply, abveritas. System is fixed now. Here's how I got into -- and out of -- this mess:Initially, I ran:  pacman -Syu --ignore filesystem && pacman -S filesystem --force && pacman -S chakra-initThe chakra-init sync failed due to conflicts -- I don't recall conflict descriptions.

I was unable to upgrade filesystem to latest version, /lib and /lib64 exists.

And I can't just remove the link, otherwise all binaries would fail to run,

Any thought?

# pacman -S filesystem :: filesystem is in IgnorePkg/IgnoreGroup. Install anyway?

I imagine the answer to this problem is SOMEWHERE but I can't find the solution. I ran sudo pacman -Syu and got this error message with mkinitcpio: ERROR: file not found: '/usr/lib/modprobe.d/usb-load-ehci-first.conf'I saw this bug but my config file is cut off before the mentioned "line 36," so it doesn't help me.

Hey guys, I'm getting a "exists in filesystem" error when upgrading, so I checked to see if the files were owned by anything, and they're both owned by mkinitcpio... what should I do? One site said to force install them but I'm nervous about that

I think you need to reinstall your old version of glibc. For example:pacman -U /var/cache/pacman/pkg/glibc-2.16.0-1-x86_64.pkg.tar.xzYou may need to force this install. I believe that should be safe. Do NOT on any account force the upgrade to the new version, though - only force the reinstall of the version you untarred.Rationale: you untarred glibc rather than installing it using pacman.

pacman -S filesystem should have updated filesystem so you are in the clear there. Now just do pacman -Su as listed in https://wiki.archlinux.org/index.php/De … iki:usrlib.This problem has been covered many times. Search the forums for how other people solved updating glibc and filesystem.

fsckd https://bbs.archlinux.org/profile.php?id=26525

2012-07-29T15:03:27Z