[arch-general] The pacman upgrading error has been solved
Hi all: I really appreciate Emil Lundberg, Paul Gideon Dann, Temlin Oliv?r, , Guus Snijders' great suggestion, you are right, that's my fault to use /dev/mapper/arch_root_image as the root partition, now I can login the system,it seems my system is working now. There are two things I do today (my mistakes) based on your suggestion: 1. Instead of using /dev/mapper/ arch_root_image, I use /dev/sda3 as my root partition, and mount first. 2. I copy the files /bin/* to /mnt/bin, so that the error message "failed to run command /bin/sh, no such file or directory" will not exists. I don't see this solution in the internet, I am just think it by myself, so maybe this can help other people with the same problem if what I have done is correct. I don't know how to appreciate all of you, the community. I am so glad to fix this problem now. During the process, I have learned a lot of things, and become more familiar with arch linux, and also love it more (I always love the things more when I get more familiar with). The feeling is strange, at beginning, I see that problem, I have no idea, and become very worried about that. I am considering that time I am failers, just hoping some angel can come and solve that problem for me ... But now, I start learning these things, about what's happening, and with your help, I become more and more confident. Thank you all. I hope my experience can benefit other people, especially the new archer, I want to tell you, don't be afraid, go ahead, start learning, asking good question, and then finally you can fix your problems! The last thing I will do is format the window system of my laptop, install arch linux :) Renzhi Cao Cell: 573-825-8874 Email : rcrg4@mail.missouri.edu<https://bluprd0112.outlook.com/owa/redir.aspx?C=HgdIKZwfkkG-ZqHZQdR5l5Qjeol9gdAIEexz2Okb9KSvfYJfxGlJ7wHelHyOveteZCNx50ztf78.&URL=mailto%3arcrg4%40mail.missouri.edu> http://web.missouri.edu/~rcrg4/
On Monday 10 Mar 2014 15:48:15 Cao, Renzhi wrote:
I really appreciate Emil Lundberg, Paul Gideon Dann, Temlin Oliv?r, , Guus Snijders' great suggestion, you are right, that's my fault to use /dev/mapper/arch_root_image as the root partition, now I can login the system,it seems my system is working now. There are two things I do today (my mistakes) based on your suggestion: 1. Instead of using /dev/mapper/ arch_root_image, I use /dev/sda3 as my root partition, and mount first. 2. I copy the files /bin/* to /mnt/bin, so that the error message "failed to run command /bin/sh, no such file or directory" will not exists. I don't see this solution in the internet, I am just think it by myself, so maybe this can help other people with the same problem if what I have done is correct.
That's great news :) The solution with copying /bin/* to /mnt/bin is a very radical solution, and I wouldn't normally recommend it, because potentially it could cause other problems (overwriting files that belong to many packages). That's because /bin/* was the files from the live CD, and /mnt/bin is your installed system, and they will have different versions of many packages. I'm glad it worked for you, though! If your system is working, any difference in the version of packages will be resolved naturally as you continue to update your system and new packages are installed, and those files are replaced.
I don't know how to appreciate all of you, the community. I am so glad to fix this problem now. During the process, I have learned a lot of things, and become more familiar with arch linux, and also love it more (I always love the things more when I get more familiar with). The feeling is strange, at beginning, I see that problem, I have no idea, and become very worried about that. I am considering that time I am failers, just hoping some angel can come and solve that problem for me ... But now, I start learning these things, about what's happening, and with your help, I become more and more confident. Thank you all. I hope my experience can benefit other people, especially the new archer, I want to tell you, don't be afraid, go ahead, start learning, asking good question, and then finally you can fix your problems! The last thing I will do is format the window system of my laptop, install arch linux :)
This a really great result. What I love most about ArchLinux is that with some curiosity and courage, anything about the system can be understood, and a lot can be learned! Make sure you keep taking backups of your data, though! It's fun at all if you lose all your data :p Paul
Thanks Paul! The reason why I copy /bin/* to /mnt/bin is my/mnt/bin is not exists. I don't know what happens, it seems this is deleted when I try to fix my problem. I will see if my system works well, if not, I will be back again :) Indeed, I learn a lot and now becomes more confident! I will tell my adviser to do the backups for all the systems. If someday I lose the data, I will share that "good news" to you immediately, and I believe that will make a lot of fun for you and the community! Renzhi Cao Cell: 573-825-8874 Email : rcrg4@mail.missouri.edu http://web.missouri.edu/~rcrg4/ ________________________________________ From: arch-general <arch-general-bounces@archlinux.org> on behalf of Paul Gideon Dann <pdgiddie@gmail.com> Sent: Monday, March 10, 2014 10:10 AM To: arch-general@archlinux.org Subject: Re: [arch-general] The pacman upgrading error has been solved On Monday 10 Mar 2014 15:48:15 Cao, Renzhi wrote:
I really appreciate Emil Lundberg, Paul Gideon Dann, Temlin Oliv?r, , Guus Snijders' great suggestion, you are right, that's my fault to use /dev/mapper/arch_root_image as the root partition, now I can login the system,it seems my system is working now. There are two things I do today (my mistakes) based on your suggestion: 1. Instead of using /dev/mapper/ arch_root_image, I use /dev/sda3 as my root partition, and mount first. 2. I copy the files /bin/* to /mnt/bin, so that the error message "failed to run command /bin/sh, no such file or directory" will not exists. I don't see this solution in the internet, I am just think it by myself, so maybe this can help other people with the same problem if what I have done is correct.
That's great news :) The solution with copying /bin/* to /mnt/bin is a very radical solution, and I wouldn't normally recommend it, because potentially it could cause other problems (overwriting files that belong to many packages). That's because /bin/* was the files from the live CD, and /mnt/bin is your installed system, and they will have different versions of many packages. I'm glad it worked for you, though! If your system is working, any difference in the version of packages will be resolved naturally as you continue to update your system and new packages are installed, and those files are replaced.
I don't know how to appreciate all of you, the community. I am so glad to fix this problem now. During the process, I have learned a lot of things, and become more familiar with arch linux, and also love it more (I always love the things more when I get more familiar with). The feeling is strange, at beginning, I see that problem, I have no idea, and become very worried about that. I am considering that time I am failers, just hoping some angel can come and solve that problem for me ... But now, I start learning these things, about what's happening, and with your help, I become more and more confident. Thank you all. I hope my experience can benefit other people, especially the new archer, I want to tell you, don't be afraid, go ahead, start learning, asking good question, and then finally you can fix your problems! The last thing I will do is format the window system of my laptop, install arch linux :)
This a really great result. What I love most about ArchLinux is that with some curiosity and courage, anything about the system can be understood, and a lot can be learned! Make sure you keep taking backups of your data, though! It's fun at all if you lose all your data :p Paul
On Monday 10 Mar 2014 16:20:25 Cao, Renzhi wrote:
Thanks Paul! The reason why I copy /bin/* to /mnt/bin is my/mnt/bin is not exists. I don't know what happens, it seems this is deleted when I try to fix my problem. I will see if my system works well, if not, I will be back again :)
This is because everything in /bin was moved to /usr/bin, and /bin was supposed to become a symlink to /usr/bin. When you do this: ls -la / Do you see: /bin -> usr/bin /lib -> usr/lib /lib64 -> usr/lib /sbin -> usr/bin Hopefully, you will. If not, you need to do some more work.
Indeed, I learn a lot and now becomes more confident! I will tell my adviser to do the backups for all the systems. If someday I lose the data, I will share that "good news" to you immediately, and I believe that will make a lot of fun for you and the community!
:) Paul
Hi, Paul: I have run ls -la /, and I do see /bin->usr/bin, ..., it seems that's a good news, cheers! Thank you so much! Renzhi Cao Email : rcrg4@mail.missouri.edu http://web.missouri.edu/~rcrg4/ ________________________________________ From: arch-general <arch-general-bounces@archlinux.org> on behalf of Paul Gideon Dann <pdgiddie@gmail.com> Sent: Monday, March 10, 2014 10:33 AM To: arch-general@archlinux.org Subject: Re: [arch-general] The pacman upgrading error has been solved On Monday 10 Mar 2014 16:20:25 Cao, Renzhi wrote:
Thanks Paul! The reason why I copy /bin/* to /mnt/bin is my/mnt/bin is not exists. I don't know what happens, it seems this is deleted when I try to fix my problem. I will see if my system works well, if not, I will be back again :)
This is because everything in /bin was moved to /usr/bin, and /bin was supposed to become a symlink to /usr/bin. When you do this: ls -la / Do you see: /bin -> usr/bin /lib -> usr/lib /lib64 -> usr/lib /sbin -> usr/bin Hopefully, you will. If not, you need to do some more work.
Indeed, I learn a lot and now becomes more confident! I will tell my adviser to do the backups for all the systems. If someday I lose the data, I will share that "good news" to you immediately, and I believe that will make a lot of fun for you and the community!
:) Paul
I don't know how to appreciate all of you, the community. I am so glad to fix this problem now. During the process, I have learned a lot of things, and become more familiar with arch linux, and also love it more (I always love the things more when I get more familiar with). The feeling is strange, at beginning, I see that problem, I have no idea, and become very worried about that. I am considering that time I am failers, just hoping some angel can come and solve that problem for me ... But now, I start learning these things, about what's happening, and with your help, I become more and more confident. Thank you all. I hope my experience can benefit other people, especially the new archer, I want to tell you, don't be afraid, go ahead, start learning, asking good question, and then finally you can fix your problems!
No problem at all! We've all been there at some point, clueless, with a broken system. Sooner or later you manage to fix it, and through the experience you gain an improved understanding of how things work. Solving one problem also helps you solve the next, even if they're very different. Gradually learning more and more as my needs change is one of the things I love about Linux, and Arch in particular. Welcome to the community!
Indeed! I like arch linux, now I am more confident about solving the problems. Thank you all! Renzhi Cao Cell: 573-825-8874 Email : rcrg4@mail.missouri.edu http://web.missouri.edu/~rcrg4/ ________________________________________ From: arch-general <arch-general-bounces@archlinux.org> on behalf of Emil Lundberg <lundberg.emil@gmail.com> Sent: Monday, March 10, 2014 12:55 PM To: General Discussion about Arch Linux Subject: Re: [arch-general] The pacman upgrading error has been solved
I don't know how to appreciate all of you, the community. I am so glad to fix this problem now. During the process, I have learned a lot of things, and become more familiar with arch linux, and also love it more (I always love the things more when I get more familiar with). The feeling is strange, at beginning, I see that problem, I have no idea, and become very worried about that. I am considering that time I am failers, just hoping some angel can come and solve that problem for me ... But now, I start learning these things, about what's happening, and with your help, I become more and more confident. Thank you all. I hope my experience can benefit other people, especially the new archer, I want to tell you, don't be afraid, go ahead, start learning, asking good question, and then finally you can fix your problems!
No problem at all! We've all been there at some point, clueless, with a broken system. Sooner or later you manage to fix it, and through the experience you gain an improved understanding of how things work. Solving one problem also helps you solve the next, even if they're very different. Gradually learning more and more as my needs change is one of the things I love about Linux, and Arch in particular. Welcome to the community!
participants (3)
-
Cao, Renzhi (MU-Student)
-
Emil Lundberg
-
Paul Gideon Dann