filesystem Update Error /bin exists in filesystem

Scimmia · 2013-06-10 19:35:43

Read the front page.

westy · 2013-06-10 19:37:39

Ah hehe, thanks... will follow that.

Sorry, I don't often hit the homepage!

Scimmia · 2013-06-10 19:39:20

westy wrote:

Ah hehe, thanks... will follow that.
Sorry, I don't often hit the homepage!

In that case, I suggest you subscribe to the arch-announce mailing list so you get notification of these important news items.

westy · 2013-06-10 19:40:20

Scimmia wrote:

In that case, I suggest you subscribe to the arch-announce mailing list so you get notification of these important news items.

Thanks, I'll do that.

jasonwryan · 2013-06-10 19:41:51

Merging with the stickied thread...

evilx_systems · 2013-06-11 02:06:10

Sorry, but I'm a complete noob to arch and I've been trying to upgrade the image on my Galaxy Note 10.1 and I've had some of the problems already mentioned in this thread. I'd be most appreciative of any assistance. My image is fairly old, as it was posted by someone on the xdadev forums months ago:
http://forum.xda-developers.com/showthr … ?t=2070139

step #1
pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -

yielded nothing, I let it go for a couple minutes and then hit Ctrl+C. Should I have waited longer?

step #2
paclist <repo> | awk ' { print $1 } ' | pacman -Ql - | grep ' /s\?bin/\| /usr/sbin/'

gave me an error, from reading the forum I saw that I needed to insert the actual name of the repo in the command and it still did not work...it appeared that paclist was not on my system.
as I could not run paclist I went ahead with step 3

step#3
find /bin /sbin /usr/sbin -exec pacman -Qo -- {} + >/dev/null

ran and it gave me nothing. I let it go for a couple minutes and then hit Ctrl+C. Should I have waited longer?

Step #4
I think my filesystem was mounted, not sure how I should have checked.

Step #5. part 1
pacman -Syu --ignore filesystem,bash

seemed to go fine. After this ran, I went back and ran step #2, paclist now worked, but gave me no hits, repeated steps 3,4 again nothing

did step #5 part 2
pacman -S bash

seemed to go fine, no problems

did step #5 part 3
pacman -Su

and got an error that /sbin still existed. I checked sbin and rc.d was still in the directory, owned by filesystem and initscripts. I moved /sbin to /sbin_old and repeated step #5.3 and the upgrade seemed to complete, however after reboot my system wouldn't load. Ran e2fsck on the image and there where a gazillion errors. Any tips on where I went wrong? I'd really like to get my image upgraded so I'm not stuck in android.

esuhl · 2013-06-11 02:17:45

Scimmia wrote:

Try this: https://bbs.archlinux.org/viewtopic.php … 3#p1283343

Ah! Perfect -- thanks! Finishing the update seems to have fixed the problem.

karol wrote:

Please search the forum, the wiki ...
Chroot using a liveCD/liveUSB and install systemd-sysvcompat.

Sorry -- I tried. Whatever search terms I was using didn't bring up the thread Scimmia linked to. I already have systemd-sysvcompat installed. But thanks anyway.

WorMzy wrote:

esuhl: If you get that error, you either:
1) were using initscripts (unsupported for half a year now) and uninstalled them to get the update to go through but didn't install systemd-sysvcompat or update your bootloader with init=/usr/lib/systemd/systemd
or
2) didn't complete the update before you restarted, and your filesystem package is out-of-date.

It was the latter -- some packages didn't update properly, then (for reasons unknown) I lost the network connection and the ability to mount USB keys, before rebooting.

Anyway, all sorted now. Thank you all for your help! :-)

esuhl · 2013-06-11 02:41:20

evilx_systems wrote:

did step #5 part 3
pacman -Su
and got an error that /sbin still existed. I checked sbin and rc.d was still in the directory, owned by filesystem and initscripts. I moved /sbin to /sbin_old and repeated step #5.3 and the upgrade seemed to complete, however after reboot my system wouldn't load. Ran e2fsck on the image and there where a gazillion errors. Any tips on where I went wrong? I'd really like to get my image upgraded so I'm not stuck in android.

I think the problem is that you have initscripts installed (which is no longer supported). Have a look here:

https://www.archlinux.org/news/end-of-i … s-support/
https://www.archlinux.org/news/systemd- … allations/

Trilby · 2013-06-11 02:47:39

evilx, you should not have to interrupt those commands with Ctrl-C, they should complete quickly and either provide output or exit with no output. Breaking out of them early both negates their purpose of checking if something will conflict, and is indicative of a deeper problem. Does running that command with everything up to, but excluding, the pipe produce output?

EDIT: also, that's an ARM processor isn't it? So you're using archlinuxARM? You should ask on their forums as that is a different distro and the particulars are going to be different - comparing across the systems may only add more confusion to an already confusing task.

Last edited by Trilby (2013-06-11 02:51:07)

WonderWoofy · 2013-06-11 02:52:47

evilx, since you are using Arch on a galaxy tab 10.1, you are using Arch Linux ARM. You need to post your question on their boards, as these are for x86 and amd64 support only.

jasonwryan · 2013-06-11 02:56:31

evilx_systems wrote:

Sorry, but I'm a complete noob to arch and I've been trying to upgrade the image on my Galaxy Note 10.1

Please use the Arch ARM boards for support fo that architecture:
https://bbs.archlinux.org/viewtopic.php?id=153431

darkreaper476 · 2013-06-11 03:31:55

Scimmia wrote:

darkreaper, this thread was originally in the testing forum, which is what you're seeing.
Did you follow the instructions on the front page? Nothing reported by the first three commands?

Yes I updated all my AUR packages with pacaur. I also have a pretty big list that uses /bin /sbin /usr/sbin.... I would prefer to not have to uninstall them.. One being Bash.... lol

bash-4.2.045-1 cdrkit-1.1.11-2 coreutils-8.21-1 cryptsetup-1.6.1-1 device-mapper-2.02.98-3 dhclient-4.2.5-1 dhcpcd-5.6.8-1 e2fsprogs-1.42.7-1 filesystem-2013.03-2 fuse-2.9.2-1 glibc-2.17-5 inetutils-1.9.1-5 iproute2-3.9.0-1 kmod-13-1 libatasmart-0.19-1 libsasl-2.1.26-3 lsof-4.87-1 lvm2-2.02.98-3 modemmanager-0.7.990-4 net-tools-1.60.20120804git-2 networkmanager-0.9.8.0-3 pm-utils-1.4.1-5 ppp-2.4.5-5 rtmpdump-20121203-1 sed-4.2.2-2 shadow-4.1.5.1-5 systemd-204-2 systemd-sysvcompat-204-2 sysvinit-tools-2.88-10 tar-1.26-3 udisks2-2.1.0-2 usbmuxd-1.0.8-1 util-linux-2.23.1-1 v4l-utils-0.9.5-1 wpa_supplicant-2.0-3 zvbi-0.2.33-5..

I am also not using testing, but I know AUR packages are no more stable. lol

Thanks

cfr · 2013-06-11 03:37:20

@darkreaper476,
Please post the command you used to generate that list. If you followed the instructions in the news, those packages should not for the most part be identified as problematic.

evilx_systems · 2013-06-11 05:40:17

thanks for the tip, I'll see if anyone on the arch linux forums for my processor can help...

sardina · 2013-06-11 09:45:09

Hi guys, after reading the directives on the front page, I successfully updated my system.

But when I rebooted, system went into emergency mode, giving me root login and suggesting to run "journalctl -xb".

Browsing the forum, I saw Scimmia's fix guide at post #265 here, I followed it, reinstalling filesystem, but nothing changed. I also tried unlinking bin, sbin and usr/sbin first, with no luck.

Here's my "journalctl -xb":

EDIT: external linked due to its length: http://pastebin.com/nw577hSD

Even by (trying) reading it I don't understand how to fix this, could someone help me, please?

I have /home mounted on a different partition, could this affect the problem anyway?

TIA

Last edited by sardina (2013-06-11 10:01:20)

Awebb · 2013-06-11 10:43:34

No, /home should not have anything to do with this problem. Boot from the installer, mount your partitions and chroot into the system (pretty much the same way you would, when installing Arch). Then check if the files are where they should be. Repair from there if not.

sardina · 2013-06-11 13:04:21

Ok, the point is: how do I know if the files are where they should be?

I currently have 3 links to /usr/bin, which are /bin /sbin and /usr/sbin. If I remove them and reinstall filesystem package, they are restored.

So I guess they're right.

Which way could I repair then?

Trilby · 2013-06-11 13:33:23

sardina, this doesn't seem to be a problem directly related to this update, so it may be best to start a new thread. I'm not very used to journalctl output, but it seems the relevant lines are the inability to mount your fat32 partitions. Are your system partitions fat32?

sardina · 2013-06-11 13:47:36

I think it was trying to mount my usb pen driver, since it was plugged.

I'll take your advice and start a new thread...

trixrabbit · 2013-06-11 17:43:50

Hi,trying to fix a problem that occured yesterday (couldn't update my system because of errors). I think my problem is caused because I renamed /bin by mistake and I had to go back with arch.iso and change it back to /bin. Anaway now my system won't boot because of dependency errors:

[FAILED] Failed to start udev Coldplug all Devices.
[FAILED] Failed to start Creat static device nodes in /dev
[TIME] Timed out waiting for device dev-sfa1.device
[DEPEND] Dependency failed for /boot
[DEPEND] Dependency failed for Local File Systems
...
Give root password for maintenance (or type control-D to continue):

So now I'm booted on archiso, I mounted my / (/dev/sda3 in my case) on /mnt, then I tried arch-root /mnt and I get :

 chroot:failed to run command "/bin/sh": No such file or directory

so I went in /mnt/bin and it's true there is no sh command, also I'm not sure what what to do once I log in chroot.
I don't know what to do and don't want to try too much things without knowing if I'll just break my system more.

I think maybe some base fonction are missing or maybe links because of the renaming mistake ?

would upgrading with pacman --root /mnt -Syu fix it?

thanks

jasonwryan · 2013-06-11 17:58:18

Merging with the sticky...

cfr · 2013-06-11 18:50:24

@trixrabbit,
Does /mnt/usr/bin/sh exist? If so, try reinstalling the filesystem package without chrooting. Either use packstrap aimed at /mnt or use pacman specifying the location for the root and database. (pacstrap is probably simplest.)

trixrabbit · 2013-06-11 22:08:59

thank you for the answer and sorry for the trouble or reposting, I thought the topic I started didn't work since I usually check in profile and posts to see the answers of my post.

So I looked in /mnt/usr/bin and there was just bash,sh and something else. But I had a file called /mnt/usr/bin.b that I made went I was trying to fix it with all my previous bin, so I just recopied all the files back into /mnt/usr/bin. I tried to boot, it booted properly to the login on tty1, only netcfg failed but I guess this isn't the problem here. Then I wrote my login/pw and it just said :

stoppping Getty on tty1...
stopped Getty on tty1
starting Getty on tty1...
started Getty on tty1

a few seconds pass...
and then it brings me back to login, after a while there is a timeout and I don't see the stopping/starting phase

So I rebooted on the iso again, I used :

pacstrap /mnt base

So it sync'd, core is up to date, then I get warnings :

i.e. warning : "thisfile-124-123-123" is up to date --reinstallating
...
resolving dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
::gcc: requires gcc-libs=4.8.0-2
==>ERROR: failed to install packages to new root

I forgot to mention I'm using CK kernel for duo-core, maybe that was a problem when sync'ing with pacstrap?

thanks for help, hopefully I can fix this

cfr · 2013-06-11 22:16:01

What *exactly* did you do when you initially ran into the error why trying to update? If you had read the news and followed the instructions, you should have dealt with obsolete packages such as netcfg.

trixrabbit · 2013-06-11 23:09:23

I was trying to install blender 3d, and it was missing a library so instead of updating my system I did the mistake of just installing the library (libpng), then all my other programs pretty much stopped working, I could log in openbox at that point but couldn't do anything except reboot/shutdown. I didn't read to news to be honest that was probably my mistake. And now I can't log it like the error described above.

Arch Linux

#476 2013-06-10 19:35:43

Re: filesystem Update Error /bin exists in filesystem

#477 2013-06-10 19:37:39

Re: filesystem Update Error /bin exists in filesystem

#478 2013-06-10 19:39:20

Re: filesystem Update Error /bin exists in filesystem

#479 2013-06-10 19:40:20

Re: filesystem Update Error /bin exists in filesystem

#480 2013-06-10 19:41:51

Re: filesystem Update Error /bin exists in filesystem

#481 2013-06-11 02:06:10

Re: filesystem Update Error /bin exists in filesystem

#482 2013-06-11 02:17:45

Re: filesystem Update Error /bin exists in filesystem

#483 2013-06-11 02:41:20

Re: filesystem Update Error /bin exists in filesystem

#484 2013-06-11 02:47:39

Re: filesystem Update Error /bin exists in filesystem

#485 2013-06-11 02:52:47

Re: filesystem Update Error /bin exists in filesystem

#486 2013-06-11 02:56:31

Re: filesystem Update Error /bin exists in filesystem

#487 2013-06-11 03:31:55

Re: filesystem Update Error /bin exists in filesystem

#488 2013-06-11 03:37:20

Re: filesystem Update Error /bin exists in filesystem

#489 2013-06-11 05:40:17

Re: filesystem Update Error /bin exists in filesystem

#490 2013-06-11 09:45:09

Re: filesystem Update Error /bin exists in filesystem

#491 2013-06-11 10:43:34

Re: filesystem Update Error /bin exists in filesystem

#492 2013-06-11 13:04:21

Re: filesystem Update Error /bin exists in filesystem

#493 2013-06-11 13:33:23

Re: filesystem Update Error /bin exists in filesystem

#494 2013-06-11 13:47:36

Re: filesystem Update Error /bin exists in filesystem

#495 2013-06-11 17:43:50

Re: filesystem Update Error /bin exists in filesystem

#496 2013-06-11 17:58:18

Re: filesystem Update Error /bin exists in filesystem

#497 2013-06-11 18:50:24

Re: filesystem Update Error /bin exists in filesystem

#498 2013-06-11 22:08:59

Re: filesystem Update Error /bin exists in filesystem

#499 2013-06-11 22:16:01

Re: filesystem Update Error /bin exists in filesystem

#500 2013-06-11 23:09:23

Re: filesystem Update Error /bin exists in filesystem

Board footer