Hello, On Fri, Jul 11, 2014 at 10:06:14PM +0100, Nuno Magalhães wrote: > # dmesg |grep ata4 > [ 0.914589] ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma > 0xf308 irq 20 > [ 2.356417] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > [ 2.364553] ata4.00: ATA-9: WDC WD10EFRX-68PJCN0, 01.01A01, max UDMA/133 > [ 2.364556] ata4.00: 268435455 sectors, multi 1: LBA NCQ (depth 31/32) > [ 2.372541] ata4.00: n_sectors mismatch 268435455 != 1953525168 > [ 2.372543] ata4.00: revalidation failed (errno=-19) > [ 2.372590] ata4: limiting SATA link speed to 1.5 Gbps > [ 2.372592] ata4.00: limiting speed to UDMA/133:PIO3 > [ 7.824219] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > [ 7.833088] ata4.00: n_sectors mismatch 268435455 != 1953525168 > [ 7.833091] ata4.00: revalidation failed (errno=-19) > [ 7.833135] ata4.00: disabled So, the device initially reports that it doesn't support LBA48 and then later changes its mind later on for some reason. That's weird. I wonder whether the controller is meddling with the IDENTIFY data. AFAICS, there isn't anything in ATA spec which would make a device change whether it reports 48 bit support or not. Can you please try the followings? 1. After boot is complete, re-trigger device attach by doing echo - - - > /sys/class/scsi_host/hostN/scan 2. Boot with libata.force=dump_id and report full dmesg after boot. 3. Boot with libata.force=nohrst and see whether anything changes. Thanks. -- 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
