filesystem Update Error /bin exists in filesystem

jasonwryan · 2013-06-17 00:40:09

https://wiki.archlinux.org/index.php/Chroot#Change_root

copacetic · 2013-06-17 00:54:57

Thanks everyone! I'm writing this from my arch install. I just chrooted in (properly this time) and did:

pacman -Syy
pacman -S bash
mkinitcpio -p linux

Then I exited the chroot, unmounted and restarted. Voila I'm back online. Thanks again!

Scimmia · 2013-06-17 01:56:53

Just for people finding this later, the reinstall of bash was unnecessary. The problem is that the kernel was updated after bash but before filesystem. With the bash binaries already moved and no /bin symlink in place yet, /bin/bash couldn't be found. Since you completed the update, the /bin symlink was in place (part of the new filesystem package) and /bin/bash was valid again, so all that really needed to be done was to regenerate the initramfs with that last command.

copacetic, since you did pacman -Syy, make sure you do a pacman -Su or -Syu before trying to install anything else.

Last edited by Scimmia (2013-06-17 01:58:35)

cfr · 2013-06-17 02:48:53

Oops. Sorry. I must have missed that bash hadn't been ignored either.

sol.invictus · 2013-06-17 03:33:21

First question do I have to move catalyst-utils?

 ~]$ pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -
catalyst-utils 13.1-5

So catalyst-utils should be in one the /bin /sbin /usr/sbin directorys right?

When I run

~]$ pacman -Qqo  /usr/sbin | pacman -Qm -
catalyst-utils 13.1-5

So the catalyst-utils should be in /usr/sbin? But when I look in the directory using ls -l the catalyst-utils is not thare.

When I run this

~]$ find / -name catalyst-utils 2>/dev/null
/usr/share/licenses/catalyst-utils

So catalyst-utils is not in /usr/bin but /usr/share/licenses so I don't have to move it?

Second question regarding non-official repos

my /etc/pacman.conf

#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta    = 0.7
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
#Color
#TotalDownload
CheckSpace
#VerbosePkgLists

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

[xorg113]
SigLevel = Optional TrustAll
Server = http://catalyst.wirephire.com/repo/xorg113/$arch

#[testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

#[community-testing]
#Include = /etc/pacman.d/mirrorlist

[community]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

When I run

 ~]$ paclist xorg113 | awk ' { print $1 } ' | pacman -Ql - | grep ' /s\?bin/\| /usr/sbin/'
[AMD@Hawk ~]$

So I have no files in /bin/ /usr/sbin/ relating to the xorg113 repo to move right?

Last edited by sol.invictus (2013-06-17 03:35:59)

Scimmia · 2013-06-17 04:21:00

It doesn't mean catalyst-utils is "in" those dirs, it means that the package includes those dirs and probably has some file in them. If you're curious, try "pacman -Ql catalyst-utils | grep ' /s\?bin\| /usr/sbin' "

Anyway, it means that catalyst-utils isn't in a repo, so where's it from? The AUR, being dropped there after being removed from the official repos, I would guess? If so, check the AUR page, you'll find you're way behind on updates and the problem has already been fixed.

And yes, on the non-official repo, if the command returned nothing, you're fine.

Last edited by Scimmia (2013-06-17 05:05:45)

podosinovik · 2013-06-17 05:14:35

Hi. I messed up my archlinux install too.
I did

pacman -Syu --ignore bash,filesystem

and then forgot to finish update and just reboot. Reboot was not all right and then I got a rootfs shell. How can I finish my update now. Can I do it without LiveCD?

fukawi2 · 2013-06-17 05:39:50

Merging with existing sticky thread.

HalosGhost · 2013-06-17 05:41:48

podosinovik wrote:

Can I do it without LiveCD?

You could do it with a LiveUSB…

All the best,

-HG

podosinovik · 2013-06-17 07:23:22

fukawi2 I don't get why this is not a right place for my question.
I've read this topic and don't find out how to fix my problem. Sorry.
I've seen occasions when people update bash and not filesystem, but my situation is a bit different, I didn't update bash.
And I have this access to inet in a different place than my home computer so I hoped to find useful hints here.

jasonwryan · 2013-06-17 07:43:46

podosinovik wrote:

fukawi2 I don't get why this is not a right place for my question.

This thread is the right place for your question. There are at least a
couple of other people who found themselves in the same situation and, using the
advice provided here, worked their way through it.

Find a Live CD, read back through this thread and, once you are chrooted in,
finish the procedure you started then prematurely terminated.

podosinovik · 2013-06-17 09:25:03

jasonwryan thank you. I've thought it was different situation.

Reznor · 2013-06-17 10:18:58

I have tried to do an upgrade like described on homepage.
Accidentaly I forgot to upgrade bash and filesystem after upgrading whole system.
Now I am stuck at rootfs, because /sbin/init is not found (Bailing out you're on your own message).
I mounted root on /mnt then cd, then mounted proc, sysfs, dev, devpts.
Then I downgraded kernel to previous version with pacman -U, also I've done the same for bash and glibc and did grub-install /dev/sda
It still drops me to rootfs.
Currently I am waiting a new optical drive for my laptop to arrive, so I have to fix this without reinstall or live cd.
Any ideas what else should I do?

Last edited by Reznor (2013-06-17 10:20:04)

karol · 2013-06-17 11:07:48

You can use liveUSB if your system can boot off a pendrive.

fsckd · 2013-06-17 11:16:05

Merged in Reznor's thread; original title was "Stuck at rootfs after upgrade".

akanski · 2013-06-18 00:43:42

podosinovik wrote:

Hi. I messed up my archlinux install too.
I did
pacman -Syu --ignore bash,filesystem
and then forgot to finish update and just reboot. Reboot was not all right and then I got a rootfs shell. How can I finish my update now. Can I do it without LiveCD?

Yes, you can. This might be useful to you in the worst-case scenario:
https://bbs.archlinux.org/viewtopic.php … 0#p1282780

Alternatively, you can install both packages manually after downloading them in that different place (#635). If so, just do the foregoing from 1 to 3, mount a drive with those files and then run `pacman -U <package_name>.pkg.tar.xz` to install them.

After that, perform a safe reboot of your computer:

echo s > /proc/sysrq-trigger
echo u > /proc/sysrq-trigger
echo b > /proc/sysrq-trigger

___

N.B.

(1) If that's the case, make sure you mount additional disk partitions such as /usr, /var, etc.

(2) If you didn't flush data to disk (s) before rebooting, let me know.

Last edited by akanski (2013-06-23 22:18:06)

akanski · 2013-06-18 00:44:41

@Reznor,

Cast your eye over my previous post.

Last edited by akanski (2013-06-18 05:30:02)

rabcor · 2013-06-18 11:24:58

it gives me this error

                                                                                                                               
error: failed to commit transaction (conflicting files)
filesystem: /usr/sbin exists in filesystem
Errors occurred, no packages were upgraded.

how should i proceed? i need to update filesystem in order to update pacman

Last edited by rabcor (2013-06-18 11:25:07)

mariusmeyer · 2013-06-18 11:25:36

Search and read the news page.

Trilby · 2013-06-18 11:26:29

*sigh*

Read the front page news. Read the stickied thread that has now grown to astronomical proportions with other users asking exactly the same question ... because they also failed to read the front page news or the stickied thread that was only slightly less astronomically large at the time.

rabcor · 2013-06-18 11:40:34

stickied thread? i see none (at least not in the applications & desktop environments, would be nice if you could have given me a link to what you're referring to.) and i'm sorry to be asking the exact same question as many other users.

if you meant these news i was trying to run "pacman -Syu" when i got the error. and i get the same if i try to "pacman -Su glibc"

i assume you did not mean this since that news post itself is older than my linux installation.

Last edited by rabcor (2013-06-18 11:41:29)

Trilby · 2013-06-18 11:44:54

The stickied thread is in the pacman subforum. The news item is the very first one at the top of the page of the front page news. You had to skip over it to go digging for the older ones.

karol · 2013-06-18 11:58:15

rabcor, just have a look at the Arch Linux home page or search the forums.

rabcor · 2013-06-18 12:12:13

I like the "Ctrl+F" button to find things i'm looking for online instead of reading tons of stuff till i just so happen to chance upon the word i was looking for. and i was searching for "filesystem"

Regardless of that, this didn't seem to work for me, i get the same error as before when i run the final command (pacman -Su)

So basically i should move the contents of /usr/sbin to /usr/bin to be able to finish the update? (the contents are a very big deal to me, it's my keyboard driver, and i worked for a week to make it work right in a programming language i didn't even understand (C) i'd rather not break them)

Last edited by rabcor (2013-06-18 12:15:23)

karol · 2013-06-18 12:15:20

What' is the name of the offending package?
How is this driver packaged? Can you e.g. update the PKGBUILD for it?

Arch Linux

#626 2013-06-17 00:40:09

Re: filesystem Update Error /bin exists in filesystem

#627 2013-06-17 00:54:57

Re: filesystem Update Error /bin exists in filesystem

#628 2013-06-17 01:56:53

Re: filesystem Update Error /bin exists in filesystem

#629 2013-06-17 02:48:53

Re: filesystem Update Error /bin exists in filesystem

#630 2013-06-17 03:33:21

Re: filesystem Update Error /bin exists in filesystem

#631 2013-06-17 04:21:00

Re: filesystem Update Error /bin exists in filesystem

#632 2013-06-17 05:14:35

Re: filesystem Update Error /bin exists in filesystem

#633 2013-06-17 05:39:50

Re: filesystem Update Error /bin exists in filesystem

#634 2013-06-17 05:41:48

Re: filesystem Update Error /bin exists in filesystem

#635 2013-06-17 07:23:22

Re: filesystem Update Error /bin exists in filesystem

#636 2013-06-17 07:43:46

Re: filesystem Update Error /bin exists in filesystem

#637 2013-06-17 09:25:03

Re: filesystem Update Error /bin exists in filesystem

#638 2013-06-17 10:18:58

Re: filesystem Update Error /bin exists in filesystem

#639 2013-06-17 11:07:48

Re: filesystem Update Error /bin exists in filesystem

#640 2013-06-17 11:16:05

Re: filesystem Update Error /bin exists in filesystem

#641 2013-06-18 00:43:42

Re: filesystem Update Error /bin exists in filesystem

#642 2013-06-18 00:44:41

Re: filesystem Update Error /bin exists in filesystem

#643 2013-06-18 11:24:58

Re: filesystem Update Error /bin exists in filesystem

#644 2013-06-18 11:25:36

Re: filesystem Update Error /bin exists in filesystem

#645 2013-06-18 11:26:29

Re: filesystem Update Error /bin exists in filesystem

#646 2013-06-18 11:40:34

Re: filesystem Update Error /bin exists in filesystem

#647 2013-06-18 11:44:54

Re: filesystem Update Error /bin exists in filesystem

#648 2013-06-18 11:58:15

Re: filesystem Update Error /bin exists in filesystem

#649 2013-06-18 12:12:13

Re: filesystem Update Error /bin exists in filesystem

#650 2013-06-18 12:15:20

Re: filesystem Update Error /bin exists in filesystem

Board footer