Re: Boot problem after crashed update
On 2011-05-12 12:53 +0200, Jochen Schulz wrote:
>> udevd[58]: error: runtime directory '/run/udev' not writable, for
>> now falling back to '/dev/.udev'
>
> That looks like you are actually running testing or unstable.
FWIW, the error message has not been present in udev versions before
168, and that version is only in unstable.
> A similar
> issue has hit my sid machein recently. Descriptions of the problem and
> solutions have been discussed here.
The best thing is to ignore the udev error message, it's actually
harmless.
>> run-init: /sbin/init: No such file or directory
>
> Ouch. Can you confirm that /sbin/init still exists on your root
> filesystem? You mentioned that you have another distro on the same
> machine, so you can use that to inspect the filesystem. I'd do an fsck,
> too.
>
>> 7) I then tried to run the rescue system from the debian installation
>> dvd:
>> - Executing a shell in /dev/sda3 (my root) fails without any
>> meaningful error message.
>
> If it doesn't mean anything to you, it still may mean something to us.
I suspect that Simon has upgraded libc6 to 2.13-3 and got hit by bug
#626450¹ (sometimes unstable actually deserves its name…).
Sven
¹ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626450
Reply to: