Re: Drive errors in boot logs, but NOT in smartctl, and still runs ok after completing boot. What's wrong with this drive?

On Sat, Apr 29, 2017, at 11:25 AM, Robert S wrote:
> Number 199 is indicating a problem. *USUALLY* it's cable related. Try 
> replacing the sata cable and see if the raw value quits climbing. If you 
> don't feel like playing with it, you can also change the sata port it's 
> plugged into on the motherboard (or add-in card).

Wow. Nice call, I woulda never have found that!  Never thought that a cable problem would allow the drive to boot and work afterwards ...

Swapped  the cable, and :

dmesg | egrep -i "ata2|ata-2"
	[    2.771065] ata2: SATA max UDMA/133 abar m1024@0xf9fff800 port 0xf9fffa80 irq 22
	[    3.259806] ata2: softreset failed (device not ready)
	[    3.262990] ata2: applying PMP SRST workaround and retrying
	[    3.439709] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
	[    3.455067] ata2.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
	[    3.458119] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
	[    3.467512] ata2.00: configured for UDMA/133

Thanks a LOT!

p.s. that "applying PMP SRST workaround and retrying" appears to be the kernel successfully working around a problem becuase of "CONFIG_SATA_PMP=y" in the kernel config.  Not sure that I can do anything abt that without compiling the kernel with a different option.  Or whether I need to.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot