public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Groth <johan.groth@linux-grotto.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Scsi errors with Megaraid 300-8x
Date: Tue, 22 Aug 2006 15:45:09 +0100	[thread overview]
Message-ID: <44EB1875.3020403@linux-grotto.org.uk> (raw)

Hi,
ever since I upgraded my server from a dual Opteron 244 (mobo Tyan 2885) 
system to a dual dual-core Opteron 285 (mobo Tyan 2895) system, I'm 
getting read errors that freezes the system which leads to my disk based 
backup software stopped working (faubackup). I think it is faubackup 
that triggers the bug.

I get these errors in the log:
Aug 20 06:35:08 jaguar kernel: sd 2:1:0:0: SCSI error: return code = 0x40001
Aug 20 06:35:56 jaguar kernel: end_request: I/O error, dev sda, sector 
616924530
Aug 20 06:36:03 jaguar kernel: sd 2:1:0:0: SCSI error: return code = 0x40001
Aug 20 06:36:03 jaguar kernel: end_request: I/O error, dev sda, sector 
616924538
Aug 20 06:36:03 jaguar kernel: sd 2:1:0:0: SCSI error: return code = 0x40001
Aug 20 06:36:03 jaguar kernel: end_request: I/O error, dev sda, sector 
616924546
Aug 20 06:36:03 jaguar kernel: sd 2:1:0:0: SCSI error: return code = 0x40001
Aug 20 06:36:03 jaguar kernel: end_request: I/O error, dev sda, sector 
616924554
Aug 20 06:36:07 jaguar kernel: sd 2:1:0:0: SCSI error: return code = 0x40001
Aug 20 06:36:07 jaguar kernel: end_request: I/O error, dev sda, sector 
616924562
Aug 20 06:36:07 jaguar kernel: sd 2:1:0:0: SCSI error: return code = 0x40001
Aug 20 06:36:07 jaguar kernel: end_request: I/O error, dev sda, sector 
616924570
Aug 20 06:36:07 jaguar kernel: sd 2:1:0:0: SCSI error: return code = 0x40001
Aug 20 06:36:07 jaguar kernel: end_request: I/O error, dev sda, sector 
616924578
Aug 20 06:36:07 jaguar kernel: sd 2:1:0:0: SCSI error: return code = 0x40001
Aug 20 06:36:07 jaguar kernel: end_request: I/O error, dev sda, sector 
616924538

The last sector is repeated until I reboot the machine. The only 
difference I've made to the raid configuration is that sdc is now 2x250 
MB instead of 4x120MB, but that array is the target not the source (sda).
The raid HW is an LSI Megaraid 300-8x with the following configuration:

Host: scsi0 Channel: 01 Id: 00 Lun: 00
   Vendor: MegaRAID Model: LD 0 RAID0  312G Rev: 814D
   Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi0 Channel: 01 Id: 01 Lun: 00
   Vendor: MegaRAID Model: LD 1 RAID0  312G Rev: 814D
   Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi0 Channel: 01 Id: 02 Lun: 00
   Vendor: MegaRAID Model: LD 2 RAID0  474G Rev: 814D
   Type:   Direct-Access                    ANSI SCSI revision: 02

I'm running debian sid stock kernel 2.6.17.

Other hw changes that may, may not affect the kernel:
CPU: dual core, hence the kernel sees 4 cpus, before 2.
Removed a sound card, a CS46xx card and am using internal sound instead.
Installed a DVB-T Freeview card (digital TV).
More RAM, 2GB instead 1.

Should mention that I used to use 2.6.16 on the old system, but I've 
checked in the kernel tree and no changes has been made to the megaraid 
drivers since April, I think.

Can anyone help me?
Please, CC me as I'm not subscribed.

Regards,
Johan

             reply	other threads:[~2006-08-22 14:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 14:45 Johan Groth [this message]
2006-08-23 15:27 ` Scsi errors with Megaraid 300-8x Mark Lord
2006-08-23 15:42   ` Johan Groth
2006-08-23 15:45     ` Justin Piszcz
2006-08-23 15:48       ` Johan Groth
2006-08-23 15:53         ` Justin Piszcz
2006-08-23 15:57           ` Johan Groth
2006-08-23 15:59             ` Justin Piszcz
2006-08-24 14:48         ` Mark Lord
2006-08-24 15:09           ` Johan Groth
2006-08-24 16:57             ` Mark Lord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44EB1875.3020403@linux-grotto.org.uk \
    --to=johan.groth@linux-grotto.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox