On Thu, May 17, 2012 at 1:29 PM, francis picabia <[email protected]> wrote: > I did a couple of upgrades from DVD to a Redhat 4 > system to bring it up to 6.3. It runs on software MD > raid. > > On boot, it fails to mount anything other than the root > raid /dev/md0 because the devices for md1 through md4 > are missing in /dev. If I manually recreate them from > MAKEDEV I can fsck and mount md1 through md4 fine > under the maintenance mode. > > I thought perhaps MAKEDEV could create the whole /dev > tree, but it doesn't. If udev is the way to do this now, > how do I get it to populate /dev. There might be an earlier > error happening from whatever process which does this, > but if I can try it by hand, I might see what it is. > > I notice healthy systems have a udevd -d running. > If I try this manually in maintenance mode, > I get back: > > udevd[714]: error getting socket: Invalid argument
I had trouble seeing the earlier part of the screen over my web based KVM console before, but at the physical console I can shift-page up to scroll back and udevd is indeed the earliest error on the console: Starting udev: udevd[549]: error getting socket: Invalid argument _______________________________________________ rhelv6-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv6-list
