Hi, I did a big update last night from rawhide and other than the Noveau problem with GDM which has been updated, I didn't notice any problems. Then my system crashed... When I rebooted inittab was missing and udev was unable to find anything (I had loads of udev failures for finding anything within /dev).

As yet, I'm unable to get that machine to reboot and return to a desktop (it will get through to being able to log in, but as it can't find any of the groups or users, it can't be logged in). I can boot from a RIPLinux disc and mount the drive, so everything is still there (which is good). Any ideas on how to fix this problem? I've not seen any other reports on here so far. TTFN Paul -- It's only me, only me and no-one else.

Hi, I did a big update last night from rawhide and other than the Noveau problem with GDM which has been updated, I didn't notice any problems. Then my system crashed... When I rebooted inittab was missing and udev was unable to find anything (I had loads of udev failures for finding anything within /dev). As yet, I'm unable to get that machine to reboot and return to a desktop (it will get through to being able to log in, but as it can't find any of the groups or users, it can't be logged in). I can boot from a RIPLinux disc and mount the drive, so everything is still there (which is good). Any ideas on how to fix this problem? I've not seen any other reports on here so far.

On Thu, 2 Apr 2009, Panu Matilainen wrote: > On Wed, 1 Apr 2009, Paul F. Johnson wrote: > >> Hi, >> >> I did a big update last night from rawhide and other than the Noveau >> problem >> with GDM which has been updated, I didn't notice any problems. Then my >> system >> crashed... >> >> When I rebooted inittab was missing and udev was unable to find anything >> (I >> had loads of udev failures for finding anything within /dev). >> >> As yet, I'm unable to get that machine to reboot and return to a desktop >> (it >> will get through to being able to log in, but as it can't find any of the >> groups or users, it can't be logged in). >> >> I can boot from a RIPLinux disc and mount the drive, so everything is >> still >> there (which is good). >> >> Any ideas on how to fix this problem? I've not seen any other reports on >> here >> so far. > > Do you have a yum.log of this system available? In bug 492947, according to > yum.log "something" has *erased* half the system (including setup etc) in > what appears to be a separate transaction, which will certainly end up in > missing /etc/passwd and such. > And did you run yum-complete-transaction after an aborted transaction where X died, by any chance?