On Thu, 20 Jul 2000, richard lashmore wrote:
> Unattached inode 86734
> /dev/hda3: Unexpected inconsistency: Run fsck manually
> (ie without -a or -p options)
> An error occured during the file system check dropping you to a shell the system
>will reboot when yoy leave the shell
> Give root password for maintenance
> or type Control-D for normal startup
> so I put in the password then a Startx command
That's your first problem.
Your system has not been shutdown properly, and now has an error on the
hard disk. It has booted up into single user mode {I.E. for you to fix
the problem}, and has in fact told you what to do in the rrror
messages. You need to type this once you have booted up and entered the
root password
fsck.ext2 /dev/hda3
Answer YES to any questions you are asked.
Once this is done, type exit, and your machine should reboot. Then you
should be able to login properly - unless you get another error on another
partition, in which case you'll have to perform the same operation for the
/dev/hdaX number listed until they're all fixed.
> which then come up with the following....
> xauth error in locking authority file /root/xauthority
> fatal server error
> could not create lock file in /tmp.tx0- lock
> When reporting a problem relating to a server crash, please send the full server
>output, ot just the last messages
> X11Transocket UNIXconnect : cant connect: errno=111 giving up
> Xinit connection refused errno 111) unable to connect to server
> Xinit No such problem (errno 31) server error
>
> So that is what I get on startup.
That's because of the error condition, and the fact that the filesystems
aren't mounted properly. Do what I listed above, and you should be OK.
> Im quite worried about it and have no idea about anything to do with the system but
>there is a 'reconfigure Gnome displays'
> or something option in the background pallet and you can be reasonably sure thats
>were Ive mucked it up.
> I would really appreciate any help I could get
To avoid this situation in future, you MUST learn how to shut your system
down properly.
As root, type
sync; sync; shutdown -h now
once you've finished using the machine, then WAIT until it says "System
Halted" before you turn the power off. Do NOT just turn the power off, or
hit reset - this can damage your filesystem.
DaZZa
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
