problems with gdm after crash
 

Hello.

I had a crash recently and a couple of inodes got corrupted.
fsck deleted one of them. After that gdm does not start automatically in run
mode 5 like it used to. It tries to start though and complains to /var/log/messages:
Mar 18 02:13:58 h147n2fls34o874 gdm[1032]: gdm_auth_secure_display: Error getting hentry for h147n2fls34o874

This is repeated five times with different pids. Then it says:
Mar 18 02:15:18 h147n2fls34o874 gdm[1024]: Failed to start the display server several times in a short time period; disabling display :0

When I manually run X and then gdm from the sys console I can log in
as root but gnome complains about not being able to resolve my
internet adress. The following lines are added to /var/log/messages:

Mar 18 02:17:18 h147n2fls34o874 gdm[1091]: gdm already running. Aborting!
Mar 18 02:17:22 h147n2fls34o874 gdm[1094]: gdm_auth_secure_display: Error getting hentry for h147n2fls34o874
Mar 18 02:17:30 h147n2fls34o874 gdm(pam_unix)[1094]: session opened for user root by (uid=0)
Mar 18 02:17:36 h147n2fls34o874 modprobe: modprobe: Can't locate module sound-slot-0
Mar 18 02:17:36 h147n2fls34o874 modprobe: modprobe: Can't locate module sound-service-0-0
Mar 18 02:17:40 h147n2fls34o874 gnome-name-server[1274]: starting
Mar 18 02:17:40 h147n2fls34o874 gnome-name-server[1274]: name server starting
Mar 18 02:17:40 h147n2fls34o874 gnome-name-server[1276]: starting
Mar 18 02:17:40 h147n2fls34o874 gnome-name-server[1276]: name server was running on display, exiting
Mar 18 02:17:40 h147n2fls34o874 kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Mar 18 02:17:40 h147n2fls34o874 kernel: sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
Mar 18 02:17:44 h147n2fls34o874 gconfd (root-1287): starting (version 1.0.4), pid 1287 user 'root'
Mar 18 02:17:44 h147n2fls34o874 gconfd (root-1287): Successfully registered `OAFIID:gconfd:19991118'
Mar 18 02:17:48 h147n2fls34o874 xinetd[1298]: warning: can't get client address: Transport endpoint is not connected

This is really weird because I can "dig" to look up my IP. Obviously I do have
connectivity since I'm writing this post!

It seems to me there is some kind of problem with X host authentication.
Maybe the inode that was deleted belonged to some file which is critical
to X authentication? What should I look for?

TIA!

turns out it was a problem with dhcp
 

Adding -D to dhcpcd's arguments (in /sbin/ifup) seems to help.
Why isn't -D default? *shrug*