[lkml]   [1996]   [Jul]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Old (1.2.13) kernel question
Todd Graham Lewis ( wrote:
: On Fri, 19 Jul 1996, Wayne Buttles wrote:

: > Jul 12 23:24:09 kernel: SCSI disk error : host 0 id 1 lun 0 return code= 2
: > Jul 12 23:24:09 kernel: scsidisk I/O error: dev 0812, sector 7372840
: > Jul 12 23:24:09 kernel: Kernel panic: EXT2-fs panic (device 8/18):
: > ext2_read_inode: unable to read i-node block - inode=921604, block=3686420
: >
: > 8/18 is my root filesystem on a seagate baracuda. I read that these get
: > REAL hot--maybe it is heat induced? This is a normal compaq tower server
: > with stock fans, and this error has happened multiple times (with
: > different sectors and inodes).

: Yep, this would be my guess. Is the pattern of errors consistent with
: the heat theory? I.e., do you not see any errors after a long power-off,
: but do after sustained activity? I bet that were you to leave it off for
: a few hours and reboot it, then you wouldn't see any errors for a while,
: and that were you to undertake any heavy file-access programs, then you
: would start seeing them.

I had a Maxtor that would overhead a voltage regulator in about
5 minutes, then fail and hang up the SCSI bus _HARD_.

I simply took it off the SCSI chain, powered it up, and waited
for a few minutes. Powered down and w/my finger determined the
hottest component. Duct taped a 5v fan to it.

This drive outlived by 3 YEARS the other 5 drives we got in
1990. (they were in NeXT boxes - and I got this one because
it was the _first_ to show signs of failure...)

 \ /
  Last update: 2005-03-22 13:38    [W:0.029 / U:0.352 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site