Date: Mon, 13 Feb 2012 23:12:40 +0100 From: Willem Jan Withagen <wjw@digiware.nl> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: "stable@freebsd.org" <stable@freebsd.org> Subject: Re: Troube with SSD Message-ID: <4F398AD8.7010609@digiware.nl> In-Reply-To: <20120213162810.GA75832@icarus.home.lan> References: <4F2940C1.10901@digiware.nl> <20120201143942.GA96012@icarus.home.lan> <4F2960A7.8040705@digiware.nl> <20120201163556.GA97343@icarus.home.lan> <4F297FD5.7090809@digiware.nl> <4F39372E.5030105@digiware.nl> <20120213162810.GA75832@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13-2-2012 17:28, Jeremy Chadwick wrote: > On Mon, Feb 13, 2012 at 05:15:42PM +0100, Willem Jan Withagen wrote: >> On 2012-02-01 19:09, Willem Jan Withagen wrote: >>> On 2012-02-01 17:35, Jeremy Chadwick wrote: > The SATA PHY counters for the disk, kept in GP log area 0x11, look > perfectly fine. The 11 you see at offset 0xa are completely fine; > nothing to worry about there. > > Sadly the SSD does not support GP log area 0x04. > > Overall I see no real problems with the drive itself given the > information above, which is literally all I can go off of. Sorry I > can't be of more assistance past this point; honestly your drive looks > fine given what I can tell. Only Corsair would be able to help at this > point, but it's unlikely any Tier 1 individual would know how to > troubleshoot this kind of thing. I'll let it run, until it disconnects again, and I'll check to see what the SATA stats are. Perhaps there is something that triggers. But that might take a few days.... Last time it took 23 days under my regular load to be dropped from the bus. --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F398AD8.7010609>