| To: | Robert Rusek <rrusek@teknuts.com> |
|---|---|
| Subject: | Re: Indy SCSI Errors |
| From: | Florian Lohoff <flo@rfc822.org> |
| Date: | Fri, 10 May 2002 11:32:32 +0200 |
| Cc: | linux-mips@oss.sgi.com |
| In-reply-to: | <C0F41630CD8B9C4680F2412914C1CF070164C2@WH-EXCHANGE1.AD.WEIDERPUB.COM> |
| Organization: | rfc822 - pure communication |
| References: | <20020509154327.GB6197@paradigm.rfc822.org> <C0F41630CD8B9C4680F2412914C1CF070164C2@WH-EXCHANGE1.AD.WEIDERPUB.COM> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.3.28i |
On Thu, May 09, 2002 at 09:31:01AM -0700, Robert Rusek wrote:
> I am familiar with the error that you are referring to. I just fixed it
> by upgrading to kernel 2.4.17. The error that I am describing, should I
> just ignore it and just do a fsck on my main drive every month? I have
> three drives sda1, sdb1, and sdc1 and it only seems to happened on the
> sda1. My sda2 is the swap drive, would that be affecting my sda1 ?
If its not the error i fixed a couple of months ago i would
suspect bad hardware - Either ram or disk. I wouldnt ignore it.
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Heisenberg may have been here.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Debian on Indy., James Simmons |
|---|---|
| Next by Date: | Re: howto pass ramdisk loaddress to kernel, Guido Guenther |
| Previous by Thread: | RE: Indy SCSI Errors, Robert Rusek |
| Next by Thread: | copy_mount_options, Rick Spanbauer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |