You are not logged in.
It might be worth splitting thread as we are in testing forum...users are going to get confused..
Mr Green
Offline
indianahorst wrote:When I came to # pacman -Su, I still got the "exists in filesystem" error. I hadn't the time to fix it at the moment, so I shutdown my system.
Why did you start updating at all then??
Use a liveCD / live USB, chroot, fix the 'exist in the filesystem' errors and open a separate thread if you need further help.
I'm trying it... bootet Parted Magic from USB, chrooted, but
# chroot /mnt/root/ /bin/bash
chroot: can't execute '/usr/bin/bash': No such file or directory
# chroot /mnt/root/ /usr/bin/bash
chroot: can't execute '/usr/bin/bash': No such file or directory
Any hints?
/bin, /sbin, and /usr/sbin are all symbolic links to /usr/bin... and in /usr/bin is just a very small subset of core programs!
Offline
Hello,
First of all: I dont use testing or unofficial repos, just the official ones.
A few hours ago, I updated my system following the instructions on
https://www.archlinux.org/news/binaries … ervention/
Step 1-4 were flawlessly, but:
following Step 5, I did
# pacman -Syu --ignore filesystem,bash
# pacman -S bash
When I came to
# pacman -Su
, I still got the "exists in filesystem" error. I hadn't the time to fix it at this moment, so I shutdown my system.
Now I startet it again and just get the error
Error: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good Luck
[rootfs /]#
/bin, /sbin, and /usr/sbin are all symbolic links to /usr/bin/
I already booted Parted Magic from Live USB and tried to chroot, but that failed because of the missing bash executable in /usr/bin/.
Is there still a way to fix it?
Offline
When I came to
# pacman -Su
, I still got the "exists in filesystem" error. I hadn't the time to fix it at this moment, so I shutdown my system.
I think we need a facepalm emoticon.
Anyway, do the /bin, /sbin, and /usr/sbin dirs exist? If so, what's in them?
Online
Allan is the man, it broke my system already up and running after a simple changeroot
sudo f'ed it up for me.
box1: Arch (linux-3.17-rc5)
box2: Gentoo (linux-3.17-rc5)
wm: subtle
Offline
indianahorst wrote:When I came to
# pacman -Su
, I still got the "exists in filesystem" error. I hadn't the time to fix it at this moment, so I shutdown my system.
I think we need a facepalm emoticon.
It wasn't clear to me, that after the execution of
# pacman -Syu --ignore filesystem,bash
# pacman -S bash
would be in an unbootable stage! There is nowhere a hint in this direction!
Anyway, do the /bin, /sbin, and /usr/sbin dirs exist? If so, what's in them?
The /bin, /sbin, and /usr/sbin dirs exist, but they are just symlinks to /usr/bin/.
Offline
UPDATE:
I personally fixed this by running '# rm -rf /bin; rm -rf /usr/sbin' then '# pacman -Su'. Seems to be working now but YMMV.
FYI this is also happening on NON-testing repos.
The update has passed [testing] and is now available in th non-testing repos.
https://bbs.archlinux.org/viewtopic.php … 4#p1281714
Offline
So everything is symlinked correctly, but /usr/bin/bash doesn't exist? Or /usr/bin/init? Sounds like the first pacman update didn't work. You'll need an arch boot disk so you can use pacman with the -r option to reinstall things. Start with systemd-sysvcompat and bash then see if you can arch-chroot.
Online
The /bin, /sbin, and /usr/sbin dirs exist, but they are just symlinks to /usr/bin/.
Good.
It wasn't clear to me, that after the execution of
# pacman -Syu --ignore filesystem,bash # pacman -S bash
would be in an unbootable stage! There is nowhere a hint in this direction!
The news item and the update instructions said you need to
# pacman -Syu --ignore filesystem,bash
# pacman -S bash
# pacman -Su
Why did you assume that some parts are optional or can be performed later?
Offline
This has gone mainstream. Moving from testing to Pacman & Package Upgrade Issues.
Note to other moderators: As this is someone exceptional, I left a forwarding link for this in 'Testing' on purpose.
Last edited by ewaller (2013-06-03 15:48:52)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Oh, and once you get in, just run "pacman -Syu" and see if everything's fine afterwards. If not, try "pacman -Q | pacman -Qk | grep warning" to see what packages need reinstalled.
Online
Error: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good Luck
[rootfs /]#
Same problem here...
But i can't execute "pacman -S bash"... pacman not exists...
Last edited by Visp (2013-06-03 18:14:45)
Offline
Merging with the stickied thread...
Offline
Error: Root device mounted successfully, but /sbin/init does not exist. Bailing out, you are on your own. Good Luck [rootfs /]#
Same problem here...
But i can't execute "pacman -S bash"... pacman not exists...
mount "new_root" to /mnt
then pacman -Ur /mnt/var/cache/pkg/bash....
same for filesystem...
Offline
mount "new_root" to /mnt
then pacman -Ur /mnt/var/cache/pkg/bash....
same for filesystem...
Thanks for your answer.
But i have this error when "pacman -Su bash"
error: could not open file: /etc/mtab: No such file or directory
error: could not determine filesystem mount points
error: failed to commit transaction (unexpected error)
Errors ocurred, no packages were upgraded.
Last edited by Visp (2013-06-03 19:04:46)
Offline
Hello,
well i kinda tried to upgrade ...
First i got stuck with that nice move /bin.. pacma's msg, so i quckly checked and just moved all in /usr/bin -> reboot and nothing. Then i booted from another hdd (got replaced by ssd a while back, rsynced) and mounted the ssd and was be able to install the filesystem update with.
pacman --root /mnt -S filesystem
Rebooted and still the same: cant find sbin/init.
So i checked and iam stuck here now.
sbin is "now" only owned by filesystem:
pacman --root /mnt -Qo /mnt/usr/sbin
/mnt/usr/sbin is owned by filesystem 2013.05-2
Any tips how to get ti up and running?
Some Intel CPU + HD6970 repos: [all testing] + [mesa-git]
Offline
What exactly did you do when you say "just moved all in /usr/bin"?
Do /bin and /sbin exist? They should be symlinks to usr/bin.
Last edited by Scimmia (2013-06-03 18:54:13)
Online
Read the news before upgrading or subscribe to arch-announcement mailing list, your issue is well covered. I updated with no issues.
Offline
Merging with the stickied thread...
Offline
I moved all real files and links on no "bin" files in /usr/bin from [/bin, /sbin, /usr/bin].
#ls -l /mnt/
bin -> usr/bin
...
sbin -> usr/bin
...
#ls -l /mnt/usr/
...
sbin -> bin
...
Some Intel CPU + HD6970 repos: [all testing] + [mesa-git]
Offline
ergoschnuffel, just how much did you move?!? You should have only moved files like that that you put there, anything put there by pacman should be moved by pacman. Try "pacman -Syu --root /mnt", see if you get errors.
Online
I moved all, tho did a remount and update via host pacman (pacman -Syu --root /mnt). Rebooted on ssd and its working ... kinda robust thingy.
Well thanks Scimmia.
Some Intel CPU + HD6970 repos: [all testing] + [mesa-git]
Offline
For those who ended up in an unbootable state. I assume you have previous versions of all recently updated packages in pacman's cache.
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
# chroot .
4. Open /BrokenArch/var/log/pacman.log and find the recently updated packages.
5.
# cd /var/cache/pacman/pkg
# pacman -U [list all the previous versions of recently updated packages here, use full filenames with *.pkg.tar.xz estensions. probably just few of the packages caused the problem, but I reinstalled them all]
5. Before confirming downgrade in pacman, open another terminal and log in as root.
6. In the new terminal
# rm /BrokenArch/bin
# rm /BrokenArch/sbin
7. Now you can confirm the downgrade in the first terminal.
8. When the downgrade is complete, perform it once more to correctly execute all post-install scripts.
EDIT: 8.5.
# exit
9. (edited)
# cd /
# umount /BrokenArch
10. reboot
Last edited by electric_indigo (2013-06-03 20:38:13)
Offline
Upgrades of this type typically result in me performing a complete re-installation of Arch Linux. Much to my surprise there were no problems. My thanks to the AUR maintainers. None of the 9 AUR packages I have installed required re-packaging.
Edit: I have read nearly all the posts under this topic and I am amazed that I survived this upgrade. Granted, I was fortunate to have no AUR packages requiring re-building, but is it possible I'm actually learning something, even if it is only to read the current news.
Last edited by czubek (2013-06-13 19:28:09)
Offline
Trying to do the regular sudo pacman -Syu and get:
Total Installed Size: 587.90 MiB
Net Upgrade Size: -19.05 MiB
:: Proceed with installation? [Y/n] y
(93/93) checking keys in keyring [######################] 100%
(93/93) checking package integrity [######################] 100%
(93/93) loading package files [######################] 100%
(93/93) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
filesystem: /bin exists in filesystem
filesystem: /sbin exists in filesystem
filesystem: /usr/sbin exists in filesystem
systemd-sysvcompat: /usr/bin/poweroff exists in filesystem
Errors occurred, no packages were upgraded.
I have no clue why it's complaining about /bin, /sbin, /usr/sbin and my poweroff script that i've linked in containing:
shutdown -h now
I'm almost afraid of rebooting the machine now because i'm not sure of the severity of /bin being in my "filesystem" (which it should, it just frightens me that it complains about such a thing).
Any ideas to why or how to begin debugging this?
Offline