Re: [TCLUG:3932] fatal X error

[Nate Carlson <natecars@infiniteloop.com>]

It would be a good idea to fsck the disk, and watch for any fatal-type
errors on the drive. It could be that you just had some files get
corrupted.. if that dosen't help, you've either got a flaky controller or
a bad drive.

----
Nate Carlson
the infinite loop
natecars@infiniteloop.com

On Fri, 5 Feb 1999, Tim Wilson wrote:

> Good morning,
> 
> The workstation on my desk has been acting a little flakey lately. This
> morning when I came into work I found that X had died sometime during the
> night and gave the following message:
> 
> Fatal server error:
> Caught signal 11. Server aborting
> 
> When reporting a problem related to the server crash... [blah, blah, blah]
> 
> xinit: connection to X server lost.
> 
> [root@galileo /root]# EXT2-fs error (device 03:06): ext2_write_inode: bad
> inode number: 10319
> 
> This obviously appears to be a problem on the HD, but does anyone know how
> serious this might be? Will fsck likely fix it?
> 
> -Tim
> 
> --
> Timothy D. Wilson			"A little song, a little dance,
> University of MN, chem. dept.		a little seltzer down your 
> wilson@chem.umn.edu			pants."   -Chuckles the Clown
> Phone: (612) 625-9828                       as eulogized by Ted Baxter
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tclug-list-unsubscribe@listserv.real-time.com
> For additional commands, e-mail: tclug-list-help@listserv.real-time.com
> Try our website: http://tclug.real-time.com
>