Re: linux isn't robust enough to handle bad sector??

[Reco <recoverym4n@enotuniq.net>]

	Hi.

On Sun, Sep 20, 2020 at 08:53:20PM -0700, David Christensen wrote:
> > Second,
> > 
> > SATA Phy Event Counters (GP Log 0x11)
> > ID      Size     Value  Description
> > 0x000a  2            2  Device-to-host register FISes sent due to a COMRESET
> > 0x0001  2            0  Command failed due to ICRC error 0
> > 
> > [1] helpfully states:
> > 
> > CRC error during data transfer
> > This is indicated by ICRC bit in the ERROR register and means that
> > corruption occurred during data transfer. Up to ATA/ATAPI-7, the
> > standard specifies that this bit is only applicable to UDMA transfers
> > but ATA/ATAPI-8 draft revision 1f says that the bit may be applicable to
> > multiword DMA and PIO.
> > 
> > 
> > So, it's either a damaged SATA cable, or a damaged SATA port on a
> > motherboard.
> 
> Without specialized test equipment, about all I can do is buy surplus hardware and apply a process of elimination.

I'd do the same, starting with SATA cable (the cheapest part of the
equation).

Reco