[SOLVED] After pacman update, system no longer boots

Question

Updated pacman packages, and half-way through the upgrade proces fails (it mentions not being able to find package-control).  Upon investigating, I notice no programs are working.  I ls /usr/bin and it is empty!  In a panic, I restart the machine, and it no longer boots up. 
My boot is on sda3 and /root is sda5.
When bash starts up, it loads the kernel fine, and then after a second it panics and exclaims: "No init found. Try passing init=bootarg". 
I load up my trusty Arch livecd and fsck the partitions.  Fsck claims both partitions are clean.  I am able to mount them and examine the file structure: all files look like they are there.  I then try to chroot the mounted partition (sda5, my /root), and get the error that "/bin/bash" is not found, even though it is there in the correct directory.  Not sure what to do now.
My grub entry, which has always worked fine prior to this:
legacy_kernel '/linux344-ck' 'acpi_osi=Linux' 'root=/dev/sda5' 'rootfstype=ext4' 'init=/sbin/init' 'pcie_aspm=force' 'acpi_backlight=vendor' 'i915.i915_enable_rc6=1' 'i915.i915_enable_fbc=1' 'i915.lvds_downclock=1' 'ipv6.disable=1' 'i915.semaphores=1' 'modprobe.blacklist=bluetooth,uvcvideo' 'ro'
legacy_initrd '/initramfs-linux-fallback.img' '/initramfs-linux-fallback.img'
UPDATE: solved issue.  I didn't read the news.  Upgrading via pacman broke my system because of this.  Now I know!  System is running smooth again.
Last edited by corruptz0r (2012-07-15 20:26:53)

Answer 1

Huh. I guess the problem was a couple of stale and crusty {,f}getty .service files, and an obsolete slim.service file I created a while back.
Removing them fixed my problem, although tty1 still shows boot messages (not a problem, and may not even be "new" behaviour)
Cheers Tomegun.