On 15 Jan, Mark Knecht wrote: > On Thu, Jan 14, 2010 at 6:10 PM, walt <w41...@gmail.com> wrote: >> On 01/14/2010 01:33 PM, Mark Knecht wrote: >>> >>> Hi, >>> An old machine hadn't been turned on in a few months. I decided I >>> try getting it up to date so I went through an emerge cycle to see if >>> I could get things going. It was a little picky about upgrading udev >>> but at the time I thought it had gone OK, but possibly not. emerge >>> -DuN @system completed without errors, running it again said there was >>> nothing to update, python-updater ran fine, as did revdep-rebuild. >>> However when I rebooted I see messages when starting udev: >>> >>> inotify_init failed: fnction not implemented... >> >> inotify_init is provided by glibc, so that seems to be important. That >> machine seems to have some mismatched components, but which ones? >> >> It's important that glibc be compiled with the kernel headers that are >> actually installed on your machine, so the order of package upgrading >> does matter, at least when system libs like glibc are involved. >> >> E.g. if glibc was updated *before* the kernel-headers package then you >> might expect such problems. Of course, I have no idea if that's what >> happened to you. >> >> On my x86 I have linux-headers-2.6.27-r2 and glibc-2.10.1-r1. I see >> that all of my linux-headers files are dated 2009-08-24, and glibc >> was updated just this week. You may want to check to see which of >> those packages was installed earlier. >> >> Does the machine run well enough that you can reinstall both glibc >> and udev again? > > Not right now. After the boot complains that the super block isn't > right the disk is getting mounted read only. I cannot even edit a file > with vi.
Try booting by using a rescue CD (www.sysresccd.org) fsck your root disk chroot to your root disk then try to repair your system (e.g. building/installing a new kernel) Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
