Scsi errors with Megaraid 300-8x

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Scsi errors with Megaraid 300-8x
    • From: Mark Lord <[email protected]>

• Prev by Date: Re: [ckrm-tech] [RFC][PATCH 2/7] UBC: core (structures, API)
• Next by Date: Re: [PATCH 1/3] futex_find_get_task: remove an obscure EXIT_ZOMBIE check
• Previous by thread: [PATCH 1 of 1] x86_64: Put .note.* sections into a PT_NOTE segment in vmlinux
• Next by thread: Re: Scsi errors with Megaraid 300-8x
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]