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 and then No /sbin/udevd found running; None killed and then * Checking root filesystem fsck.ext3: No such file or directory while trying to open /dev/sda7 and then messages about the superblock being wrong. The machines accepts me logging in and the file system seems to be there but the machine is clearly not happy. Maybe this isn't worth the effort and I'd be better off doing a new install, but before I go down that path I thought I'd see what actions I might take first. The kernel hasn't been changed. (2.6.29 vintage so not horribly old) I do think that gcc and glibc got upgraded with @system. Note that before the @system update there were two drives in the system, /dev/sda and /dev/hda. After the update it started showing /dev/sda twice so I unplugged the second drive. (It was video storage on on old MythTV backend and should be necessary at all.) Now the system shows one drive but fails as above. Ideas? Thanks, Mark
