Andrea Conti <[email protected]> [10-05-29 10:08]: > > ata1.00: failed command: READ DMA > > ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in > > res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) > > ata1.00: status: { DRDY ERR } > > ata1.00: error: { ICRC ABRT } > > ata1: soft resetting link > > ata1.00: configured for UDMA/33 > > ata1: EH complete > > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 > > I think you have driver issues. Might also be the cabling, but I doubt > it as faulty SATA cables are in my experience quite rare. > > WD drives are known not to get along too well with VIA SATA1 controllers: > > http://www.viaarena.com/forums/showthread.php?t=38871 > http://forums.gentoo.org/viewtopic-t-794855.html > > What kernel version are you using? > What does the kernel say when it first detects the disk? > > Do you get the same errors under a recent kernel (try the latest gentoo > install cd) ? > > My experience with WD "advanced format" drives has been positive so far, > especially considering how cheap they are... The only gripe I have is > that they report not only having a 512B *logical* sector size in the > response to ATA INFO commands (which is fine, as they have a translation > layer), but also a 512B *physical* sector size, which is wrong and > causes partitioning tools to use the wrong alignment. > All the five 1TB drives I have behave this way, and from what I read > this is not an isolated behavior... > > andrea >
Hi Andrea, I tried these kernels (all vanilla): 2.6.32.13 2.6.33.5 2.6.34.0 This is, what I cut from the dmegs out (I hope to get all relevant infos...if you missing something, I save the complete dmesg output to disk for later refrence...): sata_via 0000:00:0f.0: version 2.6 sata_via 0000:00:0f.0: PCI INT B -> GSI 20 (level, low) -> IRQ 20 sata_via 0000:00:0f.0: routed to hard irq line 10 scsi0 : sata_via PM: Adding info for scsi:host0 PM: Adding info for No Bus:host0 scsi1 : sata_via PM: Adding info for scsi:host1 PM: Adding info for No Bus:host1 ata1: SATA max UDMA/133 cmd 0xd000 ctl 0xc800 bmdma 0xb800 irq 20 ata2: SATA max UDMA/133 cmd 0xc400 ctl 0xc000 bmdma 0xb808 irq 20 pata_via 0000:00:0f.1: version 0.3.4 pata_via 0000:00:0f.1: PCI INT A -> GSI 20 (level, low) -> IRQ 20 scsi2 : pata_via PM: Adding info for scsi:host2 PM: Adding info for No Bus:host2 scsi3 : pata_via PM: Adding info for scsi:host3 PM: Adding info for No Bus:host3 ata3: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14 ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15 skge 0000:00:0a.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 skge 0000:00:0a.0: PCI: Disallowing DAC for device skge: 1.13 addr 0xf9c00000 irq 17 chip Yukon-Lite rev 9 PM: Adding info for No Bus:eth0 skge 0000:00:0a.0: eth0: addr 00:15:f2:18:b0:20 sky2: driver version 1.27 usbcore: registered new interface driver usblp Aligment: I used fdisk -cu -S 56 /dev/sda to align my partitions, which seems to work. Do I have to replace my motherboard/graphics card/RAM/... only because WD cannot talk to and/or vice versa? By the way: Can I use PCI cards on newer motherboards with PCIe-slots??? Best regards, mcc -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
