[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#462229: I'm currently experiencing the same problem.



Debian server is a VMware server host.  Each time a VM experiences  moderate disk activity I typically see the following messages:

 kernel: ata1: EH complete
 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
 kernel: ata1.00: (BMDMA stat 0x20)
 kernel: ata1.00: tag 0 cmd 0x25 Emask 0x1 stat 0x41 err 0x4 (device error)
 kernel: ata1: EH complete
 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
 kernel: ata1.00: (BMDMA stat 0x20)
 kernel: ata1.00: tag 0 cmd 0x25 Emask 0x1 stat 0x41 err 0x4 (device error)
 kernel: sd 0:0:0:0: SCSI error: return code = 0x08000002
 kernel: sda: Current: sense key: Aborted Command
 kernel:     Additional sense: No additional sense information
 kernel: end_request: I/O error, dev sda, sector 1378451324
 kernel: raid1: sda7: rescheduling sector 1315267616
 kernel: ata1: EH complete
 kernel: SCSI device sda: 1465149168 512-byte hdwr sectors (750156 MB)
 kernel: sda: Write Protect is off
 kernel: sda: Mode Sense: 00 3a 00 00
 kernel: SCSI device sda: drive cache: write back
 kernel: SCSI device sda: 1465149168 512-byte hdwr sectors (750156 MB)
 kernel: sda: Write Protect is off
 kernel: sda: Mode Sense: 00 3a 00 00
 kernel: raid1: sda7: redirecting sector 1315267616 to another mirror
 kernel: SCSI device sda: drive cache: write back

Hardware is as follows:

Asus M2N-E Motherboard - NVIDIA nForce 570 Ultra MCP Chipset
AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: WDC WD7500AAKS-0 Rev: 30.0
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: WDC WD7500AAKS-0 Rev: 30.0
  Type:   Direct-Access                    ANSI SCSI revision: 05

I've run Wester Digital extensive diagnostics against both of the disks and each reports back "No Errors".  I don't think I was expierencing this prior to a recent kernel upgrade.  Currently the kernel is:

2.6.18-6-amd64

May try to roll kernel back to see if problem occurs.

Reply to: