That is my fault. Do I also need to remove files in /usr/bin as you said? Or you mean /usr/sbin, /sbin, /bin? Since that is what I see the error from at beginning. There are a lot of files in /sbin, should I remove all of them? Let me check my system in my lab and I will reply you later for details, thank you very much! Sent from my iPhone On Mar 7, 2014, at 8:58, Thomas or Bächler <thomas@xxxxxxxxxxxxx> wrote: > Am 07.03.2014 15:51, schrieb Caorenzhi: >> Yes, I try pacman -Su, and they said the /usr/sbin is exists. I am thinking that is ok, so I reboot the system. > > The instructions explicitly stated that this is NOT okay. > >> I have a cd to load the system, and I have another computer to download packages and have a external hard disk to use, like copy files there. >> Is there still any way to solve my problem? > > Sure there is. > > Boot from a recent Arch Linux live CD, mount your file systems to /mnt > and run > arch-chroot /mnt /usr/bin/bash > > Then make sure there are no files left in /usr/sbin, /sbin and /usr/bin > - most likely, you need to uninstall a package that you built yourself - > you can properly rebuild it later and install it again. Or you need to > uninstall a package that used to be part of Arch, but it no longer needed. > > When you are done, pacman -Su should work flawlessly (the package is > already in your cache, so no network is required). To be safe, run > 'mkinitcpio -P' so your system boots correctly. > >
