filesystem Update Error /bin exists in filesystem

karol · 2013-06-04 14:27:38

whaler, please edit your post.
Use [ code ] tags for posting snippets of code and command output
It's much more readable and easier on the eyes.

Edit: Thanks :-)

Last edited by karol (2013-06-04 14:28:29)

Trilby · 2013-06-04 14:34:37

whaler, I'm guessing as you followed the instructions, you removed consolekit (which you should have removed long ago). But you still try to envoke it from your xinitrc.

Replace ck-launch-session with dbus-launch. e.g.:

exec dbus-launch --exit-with-session <kdestartupcommand>

whaler · 2013-06-04 14:38:22

karol wrote:

Thanks :-)

I didn't like it myself :-) I must be posting too seldom...

Now, how can I get KDE up and running?

coellobranco · 2013-06-04 14:49:22

sorry for my english!!!!!!

jakobcreutzfeldt I've done what you say, but does not start the system.

http://img805.imageshack.us/img805/4688/img5922u.jpg

-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --

jakobcreutzfeldt · 2013-06-04 14:55:59

Hostia!

When you performed the latest system updates, with the manual intervention for bash and filesystem, were there any errors?

whaler · 2013-06-04 15:07:05

Trilby wrote:

whaler, I'm guessing as you followed the instructions, you removed consolekit (which you should have removed long ago). But you still try to envoke it from your xinitrc.
Replace ck-launch-session with dbus-launch. e.g.:
exec dbus-launch --exit-with-session <kdestartupcommand>

Spot on!
I had that line, but with ck-launch-session inserted before startkde; erasing it made KDE come up instantly. Thanks a lot.

Talking about removing apps, I noticed that hwd (in Extra) depends on ddxinfo-arch (only in AUR), and likewise with pkgstats and dcron, respectively. Not a biggie

Last edited by whaler (2013-06-04 15:08:27)

Trilby · 2013-06-04 15:12:24

main repo packages can't depend on aur packages. Perhaps you need to update your database (odd, as this was necessary for the upgrade). Hwd is in the aur - perhaps it has only recently been dropped from extra, but it is not in the repos now.

karol · 2013-06-04 15:13:33

pkgstats depends on cron - e.g. cronie is in the official repos.
You can also use systemd calendar units for that https://bugs.archlinux.org/task/33238

krash · 2013-06-04 15:29:52

Hi everyone! Sorry about silly question but I still has problem with

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/]#

I have no chance to use liveUsb (or liveCD). Please can you tell me if there is a possibility to fix that issue ?

Thanks.

Trilby · 2013-06-04 15:41:53

Krash, you should edit your kernel line in your bootloader. Exactly how to do this depends on which bootloader you are using. With syslinux you'd hit TAB at the menu. With grub I believe the 'e' key will allow you to edit the line.

Then, if you have systemd-syvcompat installed, you should just delete the init=... parameter from the kernel line. If not, then you'll have to specify the full path to systemd.

This will only apply for that boot, but once booted you can edit your bootloader config to make the change permanent.

EDIT: hopefully this will work - I guess I am assuming the upgrade proceeded without error. If there was an error in the upgrade somewhere and you still tried to reboot, then I believe you will need a live CD/usb to recover.

Last edited by Trilby (2013-06-04 15:43:28)

Scimmia · 2013-06-04 15:50:47

You *may* be able to get back into the system, but we need to know how far you got in the update. What exactly have you done and what errors did you get?

southerncross · 2013-06-04 16:00:09

I read the news on the homepage, and reading this thread I'm slowly starting to understand what's going on. But forgive me, it's all very unclear. I just have two questions:

1) What does "fixing files" mean in "1) Fix any non-official packages with files in /bin, /sbin or /usr/sbin to put those files in /usr/bin. The list of packages that are not in a repo that need to be fixed can be generated using.."
-> does it mean we move them? does it mean we erase them? does it mean we change their ownership? I'm really confused.

2) at the end of the process that's described do we need to have a boot disc/live cd ready to continue the process?

Thanks.

krash · 2013-06-04 16:00:57

Thanks for the help! I've really forgotten that I can edit kernel options on boot )

But it seems to me that I will need to use LiveUSB (or something similar) because even if I use init=/usr/lib/systemd/systemd - systemd doesn't see /bin/mount...

but we need to know how far you got in the update

Too far ). Filesystem was the only thing that wasn't updated before reboot ).

Anyway thanks for your help!

coellobranco · 2013-06-04 16:15:17

no, i follow archlinux.org info... letter to letter... can i solve this problem with a usb/live?....

Trilby · 2013-06-04 16:32:01

southerncross wrote:

2) at the end of the process that's described do we need to have a boot disc/live cd ready to continue the process?

Absolutely not needed for normal circumstances. But it's a good idea to have around in case of a problem. If you follow the instructions carefully and pay attention to pacman output, there would be no need for using a live cd/usb.

And this is no insult to anyone - I didn't pay enough attention on one of my machines - but having the live usb there, it was easy to recover.

A live usb/cd for arch is like a seat belt in a car. You should really never need it, but you should always have it.

Scimmia · 2013-06-04 16:42:20

If you followed the instructions to the letter, you won't be in this situation, so don't start insisting that you did. You don't have the filesystem package installed, which is done in the last step.

Yes, the simplest way to solve this is with the install disk. There's multiple threads in the Pacman Upgrades forum about this with all of the info you need.

Last edited by Scimmia (2013-06-04 16:43:01)

Scimmia · 2013-06-04 16:49:01

krash wrote:

but we need to know how far you got in the update
Too far ). Filesystem was the only thing that wasn't updated before reboot ).

Anyway thanks for your help!

Excellent, this could be fixable then without an install disk.

From the rescue prompt, remount new_root as rw. Create symlinks for /new_root/usr and /new_root/sbin pointing to usr/bin (notice no preceding slash). At that point, your system should be bootable. Once back into the system, remove the symlinks and run pacman -Su to install the filesystem package.

Last edited by Scimmia (2013-06-04 16:52:23)

krash · 2013-06-04 17:08:39

Scimmia wrote:

krash wrote:
but we need to know how far you got in the update
Too far ). Filesystem was the only thing that wasn't updated before reboot ).

Anyway thanks for your help!
Excellent, this could be fixable then without an install disk.
From the rescue prompt, remount new_root as rw. Create symlinks for /new_root/usr and /new_root/sbin pointing to usr/bin (notice no preceding slash). At that point, your system should be bootable. Once back into the system, remove the symlinks and run pacman -Su to install the filesystem package.

ln -s usr/bin /new_root/usr
ln: /new_root/usr/bin: File exists

same is for sbin

P.s. used this one

akanski wrote:

ln -s usr/bin /<mount_point>/bin
ln -s usr/bin /<mount_point>/sbin

Scimmia · 2013-06-04 17:11:13

krash, then you ignored problems earlier in the process. What's in /new_root/bin and /new_root/sbin?

diederick76 · 2013-06-04 17:45:13

At my laptop, step two results in:

diederick@bob:~/ $ pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -
grub 0.97-21
grub 0.97-21
diederick@bob:~/ $ pacman -Qs grub
local/grub 0.97-21 (base)
    A GNU multiboot boot loader

Grub is not something I compiled myself. I'm unsure how to proceed. Can somebody tell me how to resolve this?

Thanks!

Scimmia · 2013-06-04 17:52:18

Grub 0.97 was removed from the main repos nearly a year ago. I would suggest switching to syslinux, but if you want to keep grub 0.97, it's available as grub-legacy in the AUR.

diederick76 · 2013-06-04 18:00:41

Scimmia wrote:

Grub 0.97 was removed from the main repos nearly a year ago. I would suggest switching to syslinux, but if you want to keep grub 0.97, it's available as grub-legacy in the AUR.

I have switched to syslinux. I probably missed the instruction to upgrade grub as part of that. Thanks.

jasonwryan · 2013-06-04 18:07:17

Merging with the stickied thread...

jasonwryan · 2013-06-04 18:18:12

Merging with the stickied thread...

Archimaredes · 2013-06-04 18:55:35

I screwed up like some others and had an unbootable system, but I just booted the live USB, mounted, removed /bin, /sbin, and /usr/sbin, and reinstalled filesystem which created the symlinks fine.

Actually much more easily fixed than I had imagined, I thought I screwed up big time.

Arch Linux

#151 2013-06-04 14:27:38

Re: filesystem Update Error /bin exists in filesystem

#152 2013-06-04 14:34:37

Re: filesystem Update Error /bin exists in filesystem

#153 2013-06-04 14:38:22

Re: filesystem Update Error /bin exists in filesystem

#154 2013-06-04 14:49:22

Re: filesystem Update Error /bin exists in filesystem

#155 2013-06-04 14:55:59

Re: filesystem Update Error /bin exists in filesystem

#156 2013-06-04 15:07:05

Re: filesystem Update Error /bin exists in filesystem

#157 2013-06-04 15:12:24

Re: filesystem Update Error /bin exists in filesystem

#158 2013-06-04 15:13:33

Re: filesystem Update Error /bin exists in filesystem

#159 2013-06-04 15:29:52

Re: filesystem Update Error /bin exists in filesystem

#160 2013-06-04 15:41:53

Re: filesystem Update Error /bin exists in filesystem

#161 2013-06-04 15:50:47

Re: filesystem Update Error /bin exists in filesystem

#162 2013-06-04 16:00:09

Re: filesystem Update Error /bin exists in filesystem

#163 2013-06-04 16:00:57

Re: filesystem Update Error /bin exists in filesystem

#164 2013-06-04 16:15:17

Re: filesystem Update Error /bin exists in filesystem

#165 2013-06-04 16:32:01

Re: filesystem Update Error /bin exists in filesystem

#166 2013-06-04 16:42:20

Re: filesystem Update Error /bin exists in filesystem

#167 2013-06-04 16:49:01

Re: filesystem Update Error /bin exists in filesystem

#168 2013-06-04 17:08:39

Re: filesystem Update Error /bin exists in filesystem

#169 2013-06-04 17:11:13

Re: filesystem Update Error /bin exists in filesystem

#170 2013-06-04 17:45:13

Re: filesystem Update Error /bin exists in filesystem

#171 2013-06-04 17:52:18

Re: filesystem Update Error /bin exists in filesystem

#172 2013-06-04 18:00:41

Re: filesystem Update Error /bin exists in filesystem

#173 2013-06-04 18:07:17

Re: filesystem Update Error /bin exists in filesystem

#174 2013-06-04 18:18:12

Re: filesystem Update Error /bin exists in filesystem

#175 2013-06-04 18:55:35

Re: filesystem Update Error /bin exists in filesystem

Board footer