filesystem Update Error /bin exists in filesystem

Scimmia · 2013-06-04 03:14:12

stayupthetree, check the sticky. Basically, you need to boot to an install disk, mount your filesystems to /mnt, run pacman --root /mnt -S filesystem, then subscribe to the arch-announce mailing list.

If you get errors upgrading filesystem, there's plenty of info in the sticky about what to do.

Trilby · 2013-06-04 03:15:30

~~Three~~two things to do:
1) Thanks for the image, but please resize it or move it offsite and link to it - it's too big for the forum guidelines.
2) You'll need to chroot (wiki page "change root") from a live media to fix your system. Once chrooted, follow the front page news item to properly update
~~3) (mostly optional) Install systemd-sysvcompat; I'm pretty sure from your results you don't have it yet.~~

EDIT: nevermind 3, you probably do have it (but still check). The error is because it is looking in /sbin/ for init.

Last edited by Trilby (2013-06-04 03:17:43)

jasonwryan · 2013-06-04 03:20:05

Merging with the stickied thread...

stayupthetree · 2013-06-04 03:54:55

I followed these instructions https://bbs.archlinux.org/viewtopic.php … 5#p1282055
when I do 'chroot .' I get 'chroot: failed to run command /bin/zsh: No such file or directory

Scimmia · 2013-06-04 03:58:05

use the command I gave you instead of chrooting. By installing from outside, you avoid chrooting into a pretty b0rked system.

If you want to/need to chroot, you can use "chroot /usr/bin/bash" or "arch-chroot /usr/bin/bash", but know that without the symlinks provided by filesystem, just about all scripts will refuse to run, as well as anything that calls anything in /bin /sbin or /usr/sbin directly instead of relying on $PATH.

stayupthetree · 2013-06-04 04:29:44

Holy ish that ultimately was simple. Had to decipher what all the "fix the packages" was about, but worked it out. Thank you Scimmia for your patience!

akanski · 2013-06-04 05:34:08

Scimmia wrote:

akanski, without using --force, pacman won't overwrite files it doesn't think are already owned by the package being upgraded. If you make those symlinks, they won't be owned by any package and pacman will just throw the error that /bin and /sbin already exist. I'm not sure why you were able to do it with 2013.01.
Believe me, everyone appreciate people helping out, it's been a hell of a day with this update both here and on IRC.

After everything is running well on Arch Linux; why cannot @kamillo, as root, remove those "ugly" symlinks (/bin & /sbin) previously made by him and install filesystem package just after in order to avoid any glitch in the future?

If I remember rightly, I did remove my symbolic link for /usr/lib64 when I saw pacman warning rather than to force its installation and then I installed such a package without any issue, as I never use --force with anything in core repo.

On the other hand, I believe in what you said, you can bet on that. In fact, I'm also sure that this "black Monday" has been "a hell of a day" by reading only this thread. After all, many people had a lot of trouble with /lib merging as well.

However, unless @kamillo has got AUR packages using /bin and /sbin, I think that making those symlinks ought to solve provisionally the booting problem (#106), even if this quick "fix" is quite unorthodox, I definitely know :-)

By the way, thanks for your patience and dedication.

Last edited by akanski (2013-08-19 19:10:01)

sullivanva · 2013-06-04 06:11:38

I think you need to put a lot more information out there on the things that need to be fixed.

Homemade scripts, startup scripts ...

I ran this to find files using /bin/bash in /etc/.

#find /etc -type f -exec grep -l "/bin/bash" {} \;
/etc/cron.hourly/0anacron
/etc/shells
/etc/passwd
/etc/ifplugd/netctl.action
/etc/X11/xinit/xinitrc.d/30-dbus
/etc/cron.d/0hourly
/etc/lxdm/Xsession
/etc/ImageMagick-6/mime.xml
/etc/passwd.OLD
/etc/rc.d/x11vnc
/etc/rc.d/ntpdate
/etc/rc.d/ntpd
/etc/rc.d/ppp
/etc/default/useradd
/etc/passwd-
/etc/skel/.xsession

graph · 2013-06-04 06:30:39

@Sullivana (#133)

If I understand your question correctly, that won't be a problem, since /usr/bin/bash will be symlinked to /bin/bash by the filesystem package. At least that's my understanding.

Scimmia · 2013-06-04 06:36:54

Yes, with /bin being a symlink to usr/bin, things can invoke bash just fine with #/bin/bash.

akanski, it can work, a lot just depends on how much he has to do. If he has a bunch of work that needs to be done in a chroot, it's probably his best option.

akanski · 2013-06-04 07:37:20

@Scimmia,

Yes, using `chroot` is a better option, I agree. However, bear in mind that @kamillo said everything was fine after running `pacman -Syu --ignore filesystem` until he rebooted, so he could have forgotten to install this package just before rebooting.

For that reason, I think that there is no symbolic link in his Arch rootfs, unless he has got AUR packages using /bin and /sbin directories, hence I fail to see why he has to do a lot of things to fix these two mere symlinks. In effect, a full chroot environment with net connection is much more than a simple command as `chroot <mount_point> /usr/bin/bash` (https://wiki.archlinux.org/index.php/Chroot). That's overly time consuming, moreover, not everybody is a guru on the inhospitable console

On the other hand, if that were the case, I'd rather make a backup of AUR problematic binaries and fix this stuff later.

Last edited by akanski (2013-06-04 09:53:56)

Allan · 2013-06-04 08:33:54

graph wrote:

If I understand your question correctly, that won't be a problem, since /usr/bin/bash will be symlinked to /bin/bash by the filesystem package. At least that's my understanding.

Correct. There is no way ever that /bin/bash will not work on an Arch system.

mibadt · 2013-06-04 10:19:11

Hi,
Till this morning i had a functional Arch_64/KDE system.
Like many, trying to upgrade messed my system.
I chrooted and followed most instructions in the "latest news" in https://www.archlinux.org/.
Everything went OK except the last command which failed due to "existing /usr/sbin in filesystem).\
Please advise!

Thanks

WorMzy · 2013-06-04 10:33:51

Like many, you should read the existing topics about this issue. Particularly the one that's stickied at the top of this subforum.

fukawi2 · 2013-06-04 11:22:40

Merging

coellobranco · 2013-06-04 11:24:21

I have a problem... i did https://www.archlinux.org/news/binaries … ervention/ but... now... syslinux no r00lz.... Error----.-..... cant find /bin/systemd .. aprox...
If I pulse TAB in syslinux and add init=/usr/bin/systemd roolz... but the system not run.... all errors... i think that the route /usr/bin not run.... but I followed the instructions https://www.archlinux.org/news/binaries … ervention/

help?

Trilby · 2013-06-04 11:33:54

Coellobranco,

If English is a second language, I think you'll find most users here will be very patient in working with you as you try to communicate clearly. However, in this very short post, there is a massive number of problems with your writing; none of them look like issues from English not being a first language, but rather from laziness. Please make an effort to communicate clearly.

Last edited by Trilby (2013-06-04 11:40:14)

jakobcreutzfeldt · 2013-06-04 11:36:46

a) add init=/usr/lib/systemd/systemd to your kernel line
b) once booted, install systemd-syvcompat. This will allow you to remove what you added in (a).

isaksen · 2013-06-04 11:38:17

pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -
error: cannot determine ownership of directory '/bin'
error: cannot determine ownership of directory '/sbin'
error: cannot determine ownership of directory '/usr/sbin'
dbus-core 1.6.4-1
initscripts 2012.09.1-1
libmysqlclient 5.5.28-1
mysql 5.5.28-1
mysql-clients 5.5.28-1
netcfg 2.8.10-1
sendmail 8.14.5-1
sysvinit 2.88-8

So I just executed the commands as fast as I could...

# pacman -Syu --ignore filesystem,bash
# pacman -S bash
# pacman -Su

But in step 1. it says "Fix any non-official packages" what does fix mean?

And what should I do?

Allan · 2013-06-04 11:41:23

The instructions assumed you had updated within the last two months.

jakobcreutzfeldt · 2013-06-04 11:41:25

"non-official packages" = packages not in the Arch repos, which would mean all of those listed in your first output.

You need to check their PKGBUILD files and make sure they install all binaries only to /usr/bin and then re-install them.

bdjnk · 2013-06-04 11:54:19

I was very worried about getting it wrong. Read through this post, as well as Binaries move to /usr/bin requiring update intervention, and followed the directions carefully. Everything went smoothly! Thank you devs!

Antoine · 2013-06-04 12:57:12

akanski wrote:

@Scimmia,
Yes, using `chroot` is a better option, I agree. However, bear in mind that @kamillo said everything was fine after running `pacman -Syu --ignore filesystem` until he rebooted, so he could have forgotten to install this package just before rebooting.

Heh. I have two machines. One is for testing stuff like this. I did exactly that: "pacman -Syu --ignore filesystem" and then stupidly rebooted and came up in the rootfs, or the intramfs or whatever. Hmm. But I fixed it! I created the necessary symlinks in new_root (unmounted it first; remounted it to have it read-write), and then instructed Grub that

 init=/usr/lib/systemd/systemd

(also turned off the "quiet" option) which allowed me to boot (with some stuff missing -- like wireless, but my wired connection worked).
Then I upgraded my (forturnately for me) only 2 AUR packages. Then I removed the symlinks I'd made and upgraded the filesystem and rebooted and HELLO!

So for my other system, I followed the instructions very carefully, and it went without a hitch.

diterius · 2013-06-04 14:01:00

Today faced with this situation:

ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own.
sh: can't access tty; job control turned off
[rootfs/]#

but successfully solved it with live usb

I did everything what electric_indigo adviced to point 4

electric_indigo wrote:

1. Boot into a LiveCD.
2. Open terminal, log in as root.
3.
# cd /
# mkdir BrokenArch
# mount /dev/[Arch's partition here] BrokenArch
# cd BrokenArch
# ln -s usr/bin bin
# ln -s usr/sbin sbin
# mount --bind /dev dev
# mount --bind /proc proc
# mount --bind /run run
# mount --bind /sys sys

then

#chroot . /usr/bin/bash
#pacman -S filesystem
/bin exists...etc

ok...rename /bin to /bin_old, /usr/sbin/ to /usr/sbin_old, remove /sbin link at all
then again

#pacman -S filesystem

it installs without any errors
At last reboot and remove live usbflash

Last edited by diterius (2013-06-04 14:09:26)

whaler · 2013-06-04 14:25:08

I read the announcement on Arch's homepage, upgraded and rebooted and all is fine, except: KDE will not launch...!

startx, i.e. xorg, comes back with:

 Couldn't exec ck-launch-session: No such file or directory
xinit: connection to X server lost

In X.0.log:

 (EE) Failed to load module "modesetting" (module does not exist,0)
 (EE) Failed to load module "fbdev" (module does not exist, 0)

In /var/log/errors.log:

 User login: pam_systemd (login:session):
Failed to connect to system bus: Did not receive a reply. Possible causes include...(etc.).

Do I need to somehow tweak systemd? I have no idea what is wrong...

Except for the missing GUI, the system seems to be running fine.

Last edited by whaler (2013-06-04 14:32:59)

Arch Linux

#126 2013-06-04 03:14:12

Re: filesystem Update Error /bin exists in filesystem

#127 2013-06-04 03:15:30

Re: filesystem Update Error /bin exists in filesystem

#128 2013-06-04 03:20:05

Re: filesystem Update Error /bin exists in filesystem

#129 2013-06-04 03:54:55

Re: filesystem Update Error /bin exists in filesystem

#130 2013-06-04 03:58:05

Re: filesystem Update Error /bin exists in filesystem

#131 2013-06-04 04:29:44

Re: filesystem Update Error /bin exists in filesystem

#132 2013-06-04 05:34:08

Re: filesystem Update Error /bin exists in filesystem

#133 2013-06-04 06:11:38

Re: filesystem Update Error /bin exists in filesystem

#134 2013-06-04 06:30:39

Re: filesystem Update Error /bin exists in filesystem

#135 2013-06-04 06:36:54

Re: filesystem Update Error /bin exists in filesystem

#136 2013-06-04 07:37:20

Re: filesystem Update Error /bin exists in filesystem

#137 2013-06-04 08:33:54

Re: filesystem Update Error /bin exists in filesystem

#138 2013-06-04 10:19:11

Re: filesystem Update Error /bin exists in filesystem

#139 2013-06-04 10:33:51

Re: filesystem Update Error /bin exists in filesystem

#140 2013-06-04 11:22:40

Re: filesystem Update Error /bin exists in filesystem

#141 2013-06-04 11:24:21

Re: filesystem Update Error /bin exists in filesystem

#142 2013-06-04 11:33:54

Re: filesystem Update Error /bin exists in filesystem

#143 2013-06-04 11:36:46

Re: filesystem Update Error /bin exists in filesystem

#144 2013-06-04 11:38:17

Re: filesystem Update Error /bin exists in filesystem

#145 2013-06-04 11:41:23

Re: filesystem Update Error /bin exists in filesystem

#146 2013-06-04 11:41:25

Re: filesystem Update Error /bin exists in filesystem

#147 2013-06-04 11:54:19

Re: filesystem Update Error /bin exists in filesystem

#148 2013-06-04 12:57:12

Re: filesystem Update Error /bin exists in filesystem

#149 2013-06-04 14:01:00

Re: filesystem Update Error /bin exists in filesystem

#150 2013-06-04 14:25:08

Re: filesystem Update Error /bin exists in filesystem

Board footer