DriveReady SeekComplete Error ignorieren?
Ich ärgere mich von Zeit zu Zeit mit diesen "DriveStatusError" bei diversen
PCs, obwohl die HD keine Probleme hat. Auch in diesem Fall lief vorher
badblocks (-svw) fehlerfrei durch. An und für sich merke ich bis jetzt bei
diesem neu aufgesetzten Rechner keine Probleme.
Was würdet ihr tun? Unten ist ein Auszug aus den messages.
Al
Sep 19 21:17:05 client2 kernel: XFS mounting filesystem hda2
Sep 19 21:17:05 client2 kernel: XFS mounting filesystem hda12
Sep 19 21:17:05 client2 kernel: XFS mounting filesystem hda11
Sep 19 21:17:05 client2 kernel: XFS mounting filesystem hda13
Sep 19 21:17:05 client2 kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 19 21:17:05 client2 kernel: hda: dma_intr: error=0x84 { DriveStatusError
BadCRC }
Sep 19 21:17:05 client2 kernel: ide: failed opcode was: unknown
Sep 19 21:17:05 client2 kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 19 21:17:05 client2 kernel: hda: dma_intr: error=0x84 { DriveStatusError
BadCRC }
Sep 19 21:17:05 client2 kernel: ide: failed opcode was: unknown
Sep 19 21:17:05 client2 kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 19 21:17:05 client2 kernel: hda: dma_intr: error=0x84 { DriveStatusError
BadCRC }
Sep 19 21:17:05 client2 kernel: ide: failed opcode was: unknown
Sep 19 21:17:05 client2 kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 19 21:17:05 client2 kernel: hda: dma_intr: error=0x84 { DriveStatusError
BadCRC }
Sep 19 21:17:05 client2 kernel: ide: failed opcode was: unknown
Sep 19 21:17:05 client2 kernel: ide0: reset: success
Sep 19 21:17:05 client2 kernel: 8139too Fast Ethernet driver 0.9.27
Sep 19 21:17:05 client2 kernel: ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 17
(level, low) -> IRQ 177
Sep 19 21:17:05 client2 kernel: eth0: RealTek RTL8139 at 0xd100,
00:4f:4e:0f:8b:93, IRQ 177
Sep 19 21:17:05 client2 kernel: ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 20
(level, low) -> IRQ 169
Sep 19 21:17:05 client2 kernel: sata_via(0000:00:0f.0): routed to hard irq
line 4
Sep 19 21:17:05 client2 kernel: ata1: SATA max UDMA/133 cmd 0xD600 ctl 0xD702
bmdma 0xDA00 irq 169
Sep 19 21:17:05 client2 kernel: ata2: SATA max UDMA/133 cmd 0xD800 ctl 0xD902
bmdma 0xDA08 irq 169
Sep 19 21:17:05 client2 kernel: ata1: dev 0 ATA, max UDMA/133, 398297088
sectors: lba48
Sep 19 21:17:05 client2 kernel: ata1: dev 0 configured for UDMA/133
Sep 19 21:17:05 client2 kernel: scsi0 : sata_via
Sep 19 21:17:05 client2 kernel: ata2: no device found (phy stat 00000000)
Sep 19 21:17:05 client2 kernel: scsi1 : sata_via
Sep 19 21:17:05 client2 kernel: Vendor: ATA Model: Maxtor 6B200M0
Rev: BANC
Sep 19 21:17:05 client2 kernel: Type: Direct-Access
ANSI SCSI revision: 05
Sep 19 21:17:05 client2 kernel: SCSI device sda: 398297088 512-byte hdwr
sectors (203928 MB)
Sep 19 21:17:05 client2 kernel: SCSI device sda: drive cache: write back
Sep 19 21:17:05 client2 kernel: SCSI device sda: 398297088 512-byte hdwr
sectors (203928 MB)
Sep 19 21:17:05 client2 kernel: SCSI device sda: drive cache: write back
Sep 19 21:17:05 client2 kernel: /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3
Sep 19 21:17:05 client2 kernel: Attached scsi disk sda at scsi0, channel 0, id
0, lun 0
Sep 19 21:17:05 client2 kernel: ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 16
(level, low) -> IRQ 185
Reply to: