Re: [arch-general] Cannot recover pacman upgrade fails problem
Hi, Thank you for giving suggestions, I have tried the one you suggest, and here is the result: #ls /mnt/sda2 boot/,grub/,home/,initramfs-fallback.img,,initramfs.img,lost+fount/,memtest86+/,syslinux/,vmlinuz-linux #ls /mnt/sda3 /boot,dev/,etc/,home/,opt/,lost+found/,proc/,root/,run/,srv/,usr/,var/,sys/. I am considering sda2 as boot partition, sda3 as my home directory, which is the highest level of my system before it crashes. And I try the following two options: 1. #mount /dev/sda2 /mnt #mount /dev/sda3 /mnt/home #arch-chroot /mnt mount: mount point /mnt/proc does not exist Error = failed to set up API filesystems in arch-chroot 2. #mount /dev/sda3 /mnt #mount /dev/sda2 /mnt/boot #arch-chroot /mnt failed to run command /bin/sh, no such file or directory When I try using /dev/mapper/arch_root-image as root partition, the arch-chroot works, that's why I am using that. Is there any problem in my command? Thank you very much! Renzhi Cao Email : rc...@mail.missouri.edu From: arch-general arch-general-boun...@archlinux.org on behalf of Emil Lundberg lundberg.e...@gmail.com Sent: Sunday, March 9, 2014 11:18 PM To: General Discussion about Arch Linux Subject: Re: [arch-general] Cannot recover pacman upgrade fails problem I'm not completely sure this is your problem, but the first thing that jumps out at me is # mount /dev/mapper/arch_root-image /mnt I'm pretty sure /dev/mapper/arch_root-image is the live system image, not your root partition. It looks to me like you need /dev/sda2 or /dev/sda3 as root (mounted at /mnt) and the other mounted at /mnt/home or /mnt/boot. The fdisk -l output doesn't tell which partition is for which mount point (except that sda1 is a swap partition), so you'll need to figure out which goes where. You could try mounting them all and looking at their contents: # mkdir -p /mnt/sda2 # mkdir -p /mnt/sda3 # mount /dev/sda2 /mnt/sda2 # mount /dev/sda3 /mnt/sda3 # ls /mnt/sda2 # ls /mnt/sda3 That should give you a hint on where to mount each partition. Then see what you need to do from there. I hope that helps a bit. :) On Mon, Mar 10, 2014 at 12:51 PM, Cao, Renzhi (MU-Student) rc...@mail.missouri.edu wrote: Hi, all: I really have no idea for the pacman upgrading fails issue, so I summarize the problem I meet, and the things I try, if any one can give me suggestions of what I miss something or I do something wrong, I really appreciate, if not, I hope this summation can benefit some other people who meets the same problem. The initial problem: After using pacman -Syu --ignore filesystem to upgrade my arch linux, and reboot, get the following message: ERROR: device '/dev/disk/by-uuid/3f51b ...' not found. Skipping fsck. ERROR: Unable to find root device '/dev/disk/by-uuid/3f51b ...'. You are being dropped to a recovery shell. You are being dropped to a recovery shell Type exit to try and continue booting sh: cant access tty; job control turned off. [ramfs /]# _ The solution may be used to solve this problem : https://wiki.archlinux.org/index.php/pacman#Q:_After_updating_my_system.2C_I_get_a_.22unable_to_find_root_device.22_error_after_rebooting_and_my_system_will_no_longer_boot I first try the first method, not work, and then try the second method: The following is the command I run and the output after I use a live CD for my system: (People have similar problem can consider it) #fdisk -l /Dev/sda : 2000.4 GB. Device boot|start|end|blocks|id|systems /dev/sda1 … Linux swap/solaris /dev/sda2 … Linux /dev/sda3 … Linux Disk /dev/mapper/arch_root-image Units ... Sectorsize ... #mount /dev/mapper/arch_root-image /mnt #mount /dev/sda3 /mnt/home #mount /dev/sda2 /mnt/boot #arch-chroot /mnt #pacman-key --init #pacman-key --populate archlinux(This command is needed for the signiture, it takes me a while to figure out this). #pacman -Syu mkinitcpio systemd linux (133/133) 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 Errors occurred, no packages were upgraded. (I Check this website for the solution: https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention) #pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm – (you may get different output, the following is mine) sysvinit-tool 2.88-9 lilo 23.2-3 grub-common 2.00-1 sysvinit-tool 2.88-9 lilo 23.2-3 #pacman -R lilo #pacman -Syu --ignore filesystem,bash #pacman -S grub #pacman -S sysvinit-tools #pacman -S systemd #pacman -S bash #pacman -Su #pacman -Syu mkinitcpio systemd linux (now for me, this command can run successfully) #exit, and umount, reboot After rebooting, I get the following error: /dev/sda3: clean ... ERROR: root device
Re: [arch-general] Cannot recover pacman upgrade fails problem
Hi, I use this system for almost one year, and don't update the system. I have tried mount /dev/sda3 as the root directory. And I try one thing before chroot: #mkdir /mnt/bin #cp /bin/* /mnt/bin #arch-chroot /mnt Now I can go to the chroot jail. And surprised to me, I run the following command, and I don't see any fails: #mv /bin/* /usr/bin/ #rmdir /bin #pacman -Syu mkinitcpio systemd linux . Now I am going to reboot my system, hopefully, it's going to work. Thanks. Renzhi Cao Email : rc...@mail.missouri.edu From: arch-general arch-general-boun...@archlinux.org on behalf of Paul Gideon Dann pdgid...@gmail.com Sent: Monday, March 10, 2014 9:13 AM To: arch-general@archlinux.org Subject: Re: [arch-general] Cannot recover pacman upgrade fails problem On Monday 10 Mar 2014 14:52:23 Cao, Renzhi wrote: Hi, Thank you for giving suggestions, I have tried the one you suggest, and here is the result: #ls /mnt/sda2 boot/,grub/,home/,initramfs-fallback.img,,initramfs.img,lost+fount/,memtest8 6+/,syslinux/,vmlinuz-linux #ls /mnt/sda3 /boot,dev/,etc/,home/,opt/,lost+found/,proc/,root/,run/,srv/,usr/,var/,sys/. I am considering sda2 as boot partition, sda3 as my home directory, which is the highest level of my system before it crashes. And I try the following two options: 1. #mount /dev/sda2 /mnt #mount /dev/sda3 /mnt/home #arch-chroot /mnt mount: mount point /mnt/proc does not exist Error = failed to set up API filesystems in arch-chroot 2. #mount /dev/sda3 /mnt #mount /dev/sda2 /mnt/boot #arch-chroot /mnt failed to run command /bin/sh, no such file or directory When I try using /dev/mapper/arch_root-image as root partition, the arch-chroot works, that's why I am using that. Is there any problem in my command? Thank you very much! What do you get when you run the lsblk command? It looks to me as though: /dev/sda3 = / /dev/sda2 = /boot The lsblk command should help a lot if the device-mapper is involved (e.g. if you used LVM). What's the history here? Is this an old box that you set up with Arch as a hobby project and now you just got back to it? Why was there such a long wait before an update? Do you remember the choices you made when you set it up (e.g. partitions etc...)? Paul
Re: [arch-general] Cannot recover pacman upgrade fails problem
Hi, Oliver Temlin: Thank you, it seems my system is working now! Thank you very much!!! From: arch-general arch-general-boun...@archlinux.org on behalf of Temlin Olivér tem...@gmail.com Sent: Monday, March 10, 2014 9:27 AM To: General Discussion about Arch Linux Subject: Re: [arch-general] Cannot recover pacman upgrade fails problem On Mar 10, 2014 4:18 PM, Cao, Renzhi (MU-Student) rc...@mail.missouri.edu wrote: Hi, I use this system for almost one year, and don't update the system. I have tried mount /dev/sda3 as the root directory. And I try one thing before chroot: #mkdir /mnt/bin #cp /bin/* /mnt/bin #arch-chroot /mnt Now I can go to the chroot jail. And surprised to me, I run the following command, and I don't see any fails: #mv /bin/* /usr/bin/ #rmdir /bin #pacman -Syu mkinitcpio systemd linux . Now I am going to reboot my system, hopefully, it's going to work. Thanks. Renzhi Cao Email : rc...@mail.missouri.edu Hello, If that should work, then try upgrading filesystem asap, and expect many '/usr/bin/file already exists in filesystem' errors on subsequent updates. Make sure, that they are unowned according to pacman (pacman -Qo /path/to/file), and remove them before continuing. Also make sure to never reboot between removing the files and upgrading these packages. --Oliver Temlin
[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 : rc...@mail.missouri.eduhttps://bluprd0112.outlook.com/owa/redir.aspx?C=HgdIKZwfkkG-ZqHZQdR5l5Qjeol9gdAIEexz2Okb9KSvfYJfxGlJ7wHelHyOveteZCNx50ztf78.URL=mailto%3arcrg4%40mail.missouri.edu http://web.missouri.edu/~rcrg4/
Re: [arch-general] The pacman upgrading error has been solved
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 : rc...@mail.missouri.edu http://web.missouri.edu/~rcrg4/ From: arch-general arch-general-boun...@archlinux.org on behalf of Paul Gideon Dann pdgid...@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
Re: [arch-general] The pacman upgrading error has been solved
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 : rc...@mail.missouri.edu http://web.missouri.edu/~rcrg4/ From: arch-general arch-general-boun...@archlinux.org on behalf of Paul Gideon Dann pdgid...@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
Re: [arch-general] The pacman upgrading error has been solved
Indeed! I like arch linux, now I am more confident about solving the problems. Thank you all! Renzhi Cao Cell: 573-825-8874 Email : rc...@mail.missouri.edu http://web.missouri.edu/~rcrg4/ From: arch-general arch-general-boun...@archlinux.org on behalf of Emil Lundberg lundberg.e...@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!
[arch-general] Cannot recover pacman upgrade fails problem
Hi, all: I really have no idea for the pacman upgrading fails issue, so I summarize the problem I meet, and the things I try, if any one can give me suggestions of what I miss something or I do something wrong, I really appreciate, if not, I hope this summation can benefit some other people who meets the same problem. The initial problem: After using pacman -Syu --ignore filesystem to upgrade my arch linux, and reboot, get the following message: ERROR: device '/dev/disk/by-uuid/3f51b ...' not found. Skipping fsck. ERROR: Unable to find root device '/dev/disk/by-uuid/3f51b ...'. You are being dropped to a recovery shell. You are being dropped to a recovery shell Type exit to try and continue booting sh: cant access tty; job control turned off. [ramfs /]# _ The solution may be used to solve this problem : https://wiki.archlinux.org/index.php/pacman#Q:_After_updating_my_system.2C_I_get_a_.22unable_to_find_root_device.22_error_after_rebooting_and_my_system_will_no_longer_boot I first try the first method, not work, and then try the second method: The following is the command I run and the output after I use a live CD for my system: (People have similar problem can consider it) #fdisk -l /Dev/sda : 2000.4 GB. Device boot|start|end|blocks|id|systems /dev/sda1 … Linux swap/solaris /dev/sda2 … Linux /dev/sda3 … Linux Disk /dev/mapper/arch_root-image Units ... Sectorsize ... #mount /dev/mapper/arch_root-image /mnt #mount /dev/sda3 /mnt/home #mount /dev/sda2 /mnt/boot #arch-chroot /mnt #pacman-key --init #pacman-key --populate archlinux(This command is needed for the signiture, it takes me a while to figure out this). #pacman -Syu mkinitcpio systemd linux (133/133) 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 Errors occurred, no packages were upgraded. (I Check this website for the solution: https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention) #pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm – (you may get different output, the following is mine) sysvinit-tool 2.88-9 lilo 23.2-3 grub-common 2.00-1 sysvinit-tool 2.88-9 lilo 23.2-3 #pacman -R lilo #pacman -Syu --ignore filesystem,bash #pacman -S grub #pacman -S sysvinit-tools #pacman -S systemd #pacman -S bash #pacman -Su #pacman -Syu mkinitcpio systemd linux (now for me, this command can run successfully) #exit, and umount, reboot After rebooting, I get the following error: /dev/sda3: clean ... ERROR: root device mounted successfully, but /sbin/init does not exist. Bailing out, you are on your own. Good luck. Sh: cannot access tty: job control turned off. [rootfs/]# _ (I check this website for the solution:1. Add init=/bin/systemd to the kernel line, based on https://bbs.archlinux.org/viewtopic.php?id=146388 2. Add init=/usr/lib/systemd/systemd to the kernel line, based on https://bbs.archlinux.org/viewtopic.php?id=166423) None of them work for me. Here is the command I run in rootfs : #ls bin,buildconfig,config,dev,etc,hooks,init,init_functions,lib,lib_64,new_root,proc,run,root,sys,tmp,usr. I check the folder new_root, it is my system's root folder before it crashes. I don't know how this new folder comes, I am guessing I do something wrong for arch-chroot? I checked : #ls -l /sbin/init 7 Mar, /sbin/init - busybox ( the same output for ls -l /bin/init) #ls -l /bin/systemd No such file #ls -l /usr/lib/systemd/systemd No such file It seems I miss something, and I remember I do reinstall the grub and sysvinit-tools before I quit arch-chroot. Welcome to ask me questions for some details if you have the same problem, and welcome to give me suggestions. ? Thank you all! Renzhi Cao Email : rc...@mail.missouri.eduhttps://bluprd0112.outlook.com/owa/redir.aspx?C=HgdIKZwfkkG-ZqHZQdR5l5Qjeol9gdAIEexz2Okb9KSvfYJfxGlJ7wHelHyOveteZCNx50ztf78.URL=mailto%3arcrg4%40mail.missouri.edu
Re: [arch-general] Problems of using pacman and updating the filesystem
Hi, I can reinstall the system any time, but I can learn more when trying to fix the problem. Thank you very much! Renzhi Cao Email : rc...@mail.missouri.edu From: arch-general arch-general-boun...@archlinux.org on behalf of Bigby James anokn...@gmail.com Sent: Saturday, March 8, 2014 12:13 AM To: General Discussion about Arch Linux Subject: Re: [arch-general] Problems of using pacman and updating the filesystem On Sat, Mar 08, 2014 at 03:56:28AM +, Cao, Renzhi (MU-Student) wrote: I plan to use : dd if=/dev/hda bs=512 count=1 21 | grep GRUB dd if=/dev/hda bs=512 count=1 21 | grep LILO to check the bootloader I have. I am really new to arch linux, but I want to fix that problem. It seems I almost fix the problem, just solve the lilo and grub-common problem. If I reinstall arch linux, that could be more difficult for me, and I am afraid of losing my data in the system. Renzhi Cao Email : rc...@mail.missouri.edu Well, obviously you're going to make backups before you go about messing with highly sensitive parts of your system, especially when using dd, right? And take my word, and the word of every other Archer for it: If reinstalling by following the *Beginner's Guide* is too difficult for you, the previously posted, advanced update guide will be much harder, and Arch is likely not the right distribution for you.
Re: [arch-general] Problems of using pacman and updating the filesystem
Ok, I have about 2T data there, I need to go by a external disk to back up the data, and then updating the system. Thank you so much! Renzhi Cao From: arch-general arch-general-boun...@archlinux.org on behalf of Ralf Mardorf ralf.mard...@alice-dsl.net Sent: Saturday, March 8, 2014 11:56 AM To: arch-general@archlinux.org Subject: Re: [arch-general] Problems of using pacman andupdating the filesystem On Sat, 2014-03-08 at 17:49 +, Cao, Renzhi (MU-Student) wrote: By the way, I am thinking the upgrading process will only influence the system, not my data partition. I still need suggestions, am I think that correct? Or lack of experience. Correct, but accidents happen, so _backup_ your data.
Re: [arch-general] Problems of using pacman and updating the filesystem
I see, so I can continue upgrading the system. This time, I only want to upgrade the system, and rebuild the kernel. When I need other operations, I will backup all data first. I will continue posting, thank you! Renzhi Cao Email : rc...@mail.missouri.edu http://web.missouri.edu/~rcrg4/ From: arch-general arch-general-boun...@archlinux.org on behalf of Ralf Mardorf ralf.mard...@alice-dsl.net Sent: Saturday, March 8, 2014 12:04 PM To: arch-general@archlinux.org Subject: Re: [arch-general] Problems of using pacman andupdating the filesystem On Sat, 2014-03-08 at 17:49 +, Cao, Renzhi (MU-Student) wrote: By the way, I am thinking the upgrading process will only influence the system, not my data partition. I still need suggestions, am I think that correct? Or lack of experience. Correct, but accidents happen, so _backup_ your data. On Sat, 2014-03-08 at 17:58 +, Cao, Renzhi (MU-Student) wrote: Ok, I have about 2T data there, I need to go by a external disk to back up the data, and then updating the system. Thank you Sorry for my broken English. I guess accidents happen does mean that sometimes data is touched by upgrades, but it isn't. I wanted to say that when fixing a broken install, then you could make a mistake, an accident, that will damage your data. Btw., please don't top post,
Re: [arch-general] Problems of using pacman and updating the filesystem
Hi,
Continue previous email, I think the warning of core does not exists if
fixed.
I try this command: #pacman -Syu mkinitcpio systemd linux
Finally, it shows:
error: failed to commit transaction (conflicting files)
filesystem: /bin exists in filesystem
filesystem: /sbin exists in filesystem
filesystem: /usr/sbin exists in filesystem
Errors occurred, no packages were upgraded.
I try : #pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm –( based on
the instruction from:
https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/)
I get the following information:
sysvinit-tool 2.88-9
lilo 23.2-3
grub-common 2.00-1
sysvinit-tool 2.88-9
lilo 23.2-3
How can I fix this?
I checked the /bin,/sbin,/usr/sbin, I find out the following file may
contain the package need to fixed:
/sbin/lilo
/usr/sbin/liloconfig
/usr/sbin/lilo-uuid-diskid
/usr/sbin/grub-bios-setup,
grub-mkconfig,ofpathname,reboot,sparc64setup,install,mknetdir,probe,set-default
#find /bin /sbin /usr/sbin -exec pacman -Qo -- {} + /dev/null , have no
output
I don't have any packages in IgnorePkg or IgnoreGroup.
Thank you all.
Renzhi Cao
Email : rc...@mail.missouri.edu
From: arch-general arch-general-boun...@archlinux.org on behalf of Cao,
Renzhi (MU-Student) rc...@mail.missouri.edu
Sent: Friday, March 7, 2014 3:52 PM
To: General Discussion about Arch Linux
Subject: Re: [arch-general] Problems of using pacman and updating the
filesystem
Hi,
Before my system crash, I try this link:
https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/
And I only get few non-official packages in /bin, /sbin, usr/sbin:
sysvinit-tool 2.88-9
lilo 23.2-3
grub-common 2.00-1
sysvinit-tool 2.88-9
lilo 23.2-3
Today, I use arch chroot to the system, and run : #pacman -Qqo /bin /sbin
/usr/sbin | pacman -Qm –
I get a long list, for a lot of files:
grub common 2.0.0
lilo 23.2-3
linux-atm 2.5.2-2
openssh 6.2p1-1
ppp 2.4.5-4
sudo
syslinux
vpnc
util-linux
wireless_tool
.
A lot, I cannot list all of them. And I try this command: #find /bin /sbin
/usr/sbin -exec pacman -Qo -- {} + /dev/null
I get the warning:
Warning: database file for core does not exist
Warning: database file for extra does not exist
Warning: database file for community does not exist
By the way, the network problem is fixed, now my system can connect to
the internet to download packages.
What should I do now? Should I use mv command to move all files in
/bin,/sbin,/usr/sbin to /usr/bin directly?
Can I still update the filesystem in this case?
Thank you all helping me.
Renzhi Cao
Email : rc...@mail.missouri.edu
From: arch-general arch-general-boun...@archlinux.org on behalf of Simon
Brand simon.br...@postadigitale.de
Sent: Friday, March 7, 2014 1:23 AM
To: General Discussion about Arch Linux
Subject: Re: [arch-general] Problems of using pacman and updating the
filesystem
Am 07.03.2014 08:13, schrieb Caorenzhi:
Hi, there are some files in /sbin,/usr/sbin. Should I just remove them
directly and then run pacman -s filesystem? I find out that I cannot access
the internet this time, can I still use that command?
Sent from my iPhone
On Mar 7, 2014, at 1:07, Simon Brand simon.br...@postadigitale.de wrote:
Am 07.03.2014 07:49, schrieb Cao, Renzhi (MU-Student):
Now, for my problem, is there any way to repair that? Or you think I should
reinstall my arch linux system?
I am not a fan of reinstalling only to fix the system, but you should
update more frequently ;)
Chroot into your system, then look into /bin, /sbin and /usr/sbin, there
shouldnt be any files. You can try then
pacman -S filesystem
Good luck!
Where are these files from? Are they from some AUR packages?
You can check this with
pacman -Qo /path/to/file
Do NOT remove then. If they are from AUR packages, remove them, update
filesystem and then reinstall them.
You could probably try to move them to /usr/bin and then update.
You need the internet to download the new filesystem package. You could
download it on another system, check the signature, copy it to the
broken system and then install it with pacman -U /path/to/package
You should know best, how to access the internet in your network.
The livesystem only trys to dhcpcd, do you have WLan?
Re: [arch-general] Problems of using pacman and updating the filesystem
Thank you. Could you give me more details about updating them? I am new to arch linux, can I try to uninstall them, and later after my problem solved, install the new one by pacman? Renzhi Cao Email : rc...@mail.missouri.edu From: arch-general arch-general-boun...@archlinux.org on behalf of Doug Newgard scimmi...@outlook.com Sent: Friday, March 7, 2014 8:23 PM To: General Discussion about Arch Linux Subject: Re: [arch-general] Problems of using pacman and updating the filesystem From: rc...@mail.missouri.edu Date: Fri, 7 Mar 2014 19:30:59 -0600 To: arch-general@archlinux.org Subject: Re: [arch-general] Problems of using pacman and updating the filesystem Hi, it seems your method is really complex. Is there any simple way? For my case, do you know how to fix the problem of lilo and grub-common? Sent from my iPhone Yeah, but either updating them to something that's actually in the repos or by updating the PKGBUILD to not put files in the old dirs and rebuild.
Re: [arch-general] Problems of using pacman and updating the filesystem
I am not sure which one is used as my boot loader, could you please tell me how to check that? I am thinking using this following command: #pacman -Rs lilo #pacman -Rs grub-common #pacman -S grub Is that correct? Thank you so much! Renzhi Cao Email : rc...@mail.missouri.edu From: arch-general arch-general-boun...@archlinux.org on behalf of WorMzy Tykashi wormzy.tyka...@gmail.com Sent: Friday, March 7, 2014 8:52 PM To: General Discussion about Arch Linux Subject: Re: [arch-general] Problems of using pacman and updating the filesystem On 8 March 2014 02:23, Doug Newgard scimmi...@outlook.com wrote: From: rc...@mail.missouri.edu Date: Fri, 7 Mar 2014 19:30:59 -0600 To: arch-general@archlinux.org Subject: Re: [arch-general] Problems of using pacman and updating the filesystem Hi, it seems your method is really complex. Is there any simple way? For my case, do you know how to fix the problem of lilo and grub-common? Sent from my iPhone Yeah, but either updating them to something that's actually in the repos or by updating the PKGBUILD to not put files in the old dirs and rebuild. s:but:by: To clarify -- grub-comon is now simply grub (grub itself was dropped to the AUR some time ago, and grub2 was renamed 'grub' in it's place). If you are using grub2 as your boot loader, install the grub package from your chroot, and remove the lilo and grub-common packages. If you are booting with lilo, remove grub-common and update lilo.(now at 24.0-3 in the AUR). WorMzy
Re: [arch-general] Problems of using pacman and updating the filesystem
I plan to use : dd if=/dev/hda bs=512 count=1 21 | grep GRUB dd if=/dev/hda bs=512 count=1 21 | grep LILO to check the bootloader I have. I am really new to arch linux, but I want to fix that problem. It seems I almost fix the problem, just solve the lilo and grub-common problem. If I reinstall arch linux, that could be more difficult for me, and I am afraid of losing my data in the system. Renzhi Cao Email : rc...@mail.missouri.edu From: arch-general arch-general-boun...@archlinux.org on behalf of WorMzy Tykashi wormzy.tyka...@gmail.com Sent: Friday, March 7, 2014 9:44 PM To: General Discussion about Arch Linux Subject: Re: [arch-general] Problems of using pacman and updating the filesystem On 8 March 2014 03:29, Cao, Renzhi (MU-Student) rc...@mail.missouri.edu wrote: I am not sure which one is used as my boot loader, could you please tell me how to check that? I am thinking using this following command: #pacman -Rs lilo #pacman -Rs grub-common #pacman -S grub Is that correct? Thank you so much! Renzhi Cao Email : rc...@mail.missouri.edu You are new to Arch Linux, but you have an Arch Linux system that pre-dates the usr-bin move from over seven months ago? :/ You don't even know what boot loader you're using?? Give up with this installation. Reinstall Arch from an up-to-date installation media, and follow the beginner's guide. I think you will learn more by doing this than trying to fix your current installation. Regards, WorMzy
[arch-general] Problems of using pacman and updating the filesystem
Hi, I get some problems about pacman. At beginning, I use pacman -Syu to update the system, and then I cannot login the system. I checked the internet, and then use CD to load the system, and use pacman -Syu mkinitcpio systemd linux, and get the following information: (133/133) 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 Errors occurred, no packages were upgraded. After this, I use the following command to update the system: pacman -Syu --ignore filesystem,bash pacman -S bash and then reboot, get the following information: ERROR: root device mounted successfully, but /sbin/init does not exist. Bailing out, you are on your own. Good luck. Sh: cannot access tty: job control turned off. ? I really appreciate if anyone can help me to solve this problem, it seems I damage the file system. Is there any way to go back to the previous system, or repair this error? Thank you all. Renzhi Cao Email : rc...@mail.missouri.eduhttps://bluprd0112.outlook.com/owa/redir.aspx?C=HgdIKZwfkkG-ZqHZQdR5l5Qjeol9gdAIEexz2Okb9KSvfYJfxGlJ7wHelHyOveteZCNx50ztf78.URL=mailto%3arcrg4%40mail.missouri.edu
Re: [arch-general] Problems of using pacman and updating the filesystem
Thank you! You are right, what I did is based on that link: https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ Now, for my problem, is there any way to repair that? Or you think I should reinstall my arch linux system? Renzhi Cao Email : rc...@mail.missouri.edu From: arch-general arch-general-boun...@archlinux.org on behalf of Ralf Mardorf ralf.mard...@alice-dsl.net Sent: Friday, March 7, 2014 12:27 AM To: arch-general@archlinux.org Subject: Re: [arch-general] Problems of using pacman and updating the filesystem PS: https://wiki.archlinux.org/index.php/arch_filesystem_hierarchy It does link to https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ ;)
