Arch Linux

estol

Member

Registered: 2011-03-04

Posts: 10

System "broken" after pacman -Syu

Hi there,

I ran a pacman -Syu today, without reading the news, so I didn't ignore filesystem and glibc. Now the system is totally broken, cannot initiate new ssh sessions, and commands like ls or pacman, or everything I tried so far except cd gives the following error:

bash: /usr/bin/ls: No such file or directory

The system is not yet upgraded to systemd, I was about to do it after this system upgrade.

I realize this is bleeding edge, not bleeding flat, so I should bring my own parachute, but I have no idea how to fix this.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,642

Re: System "broken" after pacman -Syu

That is so 2012  

You might try this
Also, look at this article

Note that you cannot chroot in as you will have the same problem in a chroot environment.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

estol

Member

Registered: 2011-03-04

Posts: 10

Re: System "broken" after pacman -Syu

That is so 2012  

You might try this
Also, look at this article

Note that you cannot chroot in as you will have the same problem in a chroot environment.

Thank you for the suggestions. I tried it, and made things worse. When booting it says:

Waiting 10 seconds for device /dev/disk/by-uuid/[uuid] ...

Error device /dev/disk/by-uuid/[uuid] not found.

Skipping fsck

Error unable to find root device /dev/disk/by-uuid/[uuid].

You are being dropped to a recovery shell, type "exit" to try and continue booting.

sh: can't access tty, turning job control off.

Very same on the fallback as well.

The strangest thing is, that the recovery shell does not respond to keyboard, while GRUB, and the BIOS did.

estol

Member

Registered: 2011-03-04

Posts: 10

Re: System "broken" after pacman -Syu

Okay, this turned out to be way too messy, so I decided to reinstall the system. Now fighting with systemd...