Russell Sloan wrote: > Yes, it looks like it's trying very hard to talk to the drive (which > is a good thing under normal circumstances), but the drive isn't > there anymore. It's SATA hardware is powered down at this point. It > doesn't sound like the right way of doing things, but it's the > behavior of the drive I'm working with. > > I actually have a 5-disk RAID that I'm working with, 3 connected > directly to a SiI 3124 and two behind a 4726 PMP. The messages for > the 3 direct connects are the same. I see similar activity for the 3 > PMP drives. > > Attached is a text file with a complete listing of the activity for > each of the 5 drives after the command is issued to each. Ah, right. After the timeout, libata error handling kicks in and tries to verify that the drive is there and working. As the device is completely unresponsive, it takes some time before libata EH to give up the device. I honestly don't know how to solve this. :-( -- 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
