Andrew Paprocki wrote: > 1) When built with modules disabled, and libata handling the sata + > pata (AMD CS5536) connections, the pata drives come _after_ the sata > drives (i.e. w/ 2 sata drives, the first IDE drive is sdc). This makes > boot configuration more complicated if booting off the pata drive. Is > there any way to control which order the drives are assigned when not > building w/ modules? Please use mount-by-LABEL or UUID. > 2) The drives display that they support udma6 in hdparm -I, but only > udma5 is being used. And hdparm -i only shows up to udma2.. ? For SATA, UDMA mode doesn't matter at all. As long as you're in DMA mode, the only thing that matters is PHY link speed and whether NCQ is enabled. > ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 In both cases, SError is indicating transmission problem. Handshake error and Unrecognized FIS type in the first case, 10b to 8b decode error and CRC error on the second case. I can't tell why but signals flying through those redish cables are getting corrupted. There have been quite a few cases of bad PSU causing transmission failures on SATA or you might have a bad controller and/or cables. The best way to debug this kind of problem is by elimination - by swapping hardware piece by piece you can find out which one is causing the problem. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
