On Nov 12, 2007 1:04 AM, Tejun Heo <htejun@xxxxxxxxx> wrote: > Matheus Izvekov wrote: > >> Indeed removing the jumper of sdb made it be recognised as SATA2. But > >> sdc, what the problem is really about, is neither SATA2, not has any > >> jumper whatsoever. but both the manufacturer and libata claim it > >> supports NCQ. > >> > > > > Anything i could do to help debug this? or perhaps it makes more sense > > to just blacklist NCQ for this particular drive? > > Timeouts on modern SATA disks usually indicate hardware problem. > > * unstable power supply (this is quite common) > * faulty cable or poorly seated connectors > * faulty drive or controller (seems rare) > > Please apply common hardware debugging method - isolate problem by > changing configuration piece-by-piece and finding out to which component > the error actually belongs to. > > -- > tejun > Tried everything, short of trying the hd on another controller, but the problem persists. - 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
