On 24/01/13 00:29, arnaud gaboury wrote: > On Wed, Jan 23, 2013 at 2:12 PM, Allan McRae <allan@xxxxxxxxxxxxx> wrote: > >> On 24/01/13 00:08, arnaud gaboury wrote: >>> >>> My issue maybe comes from the upgrade of glibc 2.17-2 from testing. >>> I have now /lib --> usr/lib and lib64/ ----> usr/lib. >>> /usr/lib64 ----> lib >>> >>> Is this the expected structure after the upgrade ? >>> >> >> Yes >> >> Give the complete package list of what was upgraded. >> >> Allan >> > > Allan, > > thank your help. Please find all the pacman logs in chronoligal order with > some explainations. > Sorry for the long logs > To summarize, I first upgraded on m system. > > [2013-01-22 19:38] kalu: synchronized database testing > [2013-01-22 19:38] kalu: synchronized database core > [2013-01-22 19:38] kalu: synchronized database extra > [2013-01-22 19:38] kalu: synchronized database community-testing > [2013-01-22 19:38] kalu: synchronized database community > [2013-01-22 19:38] kalu: synchronized database multilib-testing > [2013-01-22 19:38] kalu: synchronized database multilib > [2013-01-22 19:38] kalu: starting sysupgrade... > [2013-01-22 19:40] kalu: Failed to commit sysupgrade transaction: > conflicting files > [2013-01-22 19:43] Running 'pacman -Syu' > [2013-01-22 19:43] synchronizing package lists > [2013-01-22 19:43] starting full system upgrade > [2013-01-22 20:04] Running 'pacman -S bash' > [2013-01-22 20:05] Running 'pacman -S filesystem' > [2013-01-22 20:05] Running 'pacman -S glibc' > [2013-01-22 20:05] call to execv failed (No such file or directory) > [2013-01-22 20:05] upgraded glibc (2.17-1 -> 2.17-2) > So there was a file conflict - not sure what, but for next time, just deal with that... > > The upgrade went bad, and I made the mistake to #pacman -S glibc. It broke > immediatly my filesystem. > Then I log out and boot with Ubuntu Live CD. I chroot and tried many things > with no sucess. My bad, as I realized this morning I mounted the wrong > /dev/sdb partition as /usr . > I then boot my system on fallback. Here again, I tried to finish the > upgrade with no sucess. > I then boot with Archiso, and couldn-t finish as execv was not found. > I then downgraded glibc and filesystem, and tried again to upgrade > correctly, with no sucess. > <snip> That is a lot of going around in circles... Make sure everything is updated, then run "pacman -Qk -r /mnt" to check all the files are ready. It seems you are using the Arch install CD, so run "arch-chroot /mnt" then "mkinitcpio -p linux". Then try booting. We need some details of what is happening when it fails to give any more help. Allan