Hi Chris,
On Tue, 29 May 2012, Chris Cappuccio wrote:
The drive wasn't responding. It's likely to be the drive itself, not
some failure on the controller or magic in the wire. SSDs are not the
ultra-reliable machines they're made out to be, in my experience. The
firmware probably crashed.
Hi David,
On Tue, 29 May 2012, David Burgess wrote:
That said, I purchased a 128GB Petrol to upgrade a client's laptop.
Less than a week later the thing had secure-erased itself. I wasn't
too bothered by it, after all, some percentage of anything is going to
fail at some point, and I'm not
Hi Bob,
On Tue, 29 May 2012, Bob Bishop wrote:
On 29 May 2012, at 17:41, Chris Wilson wrote:
[...]So I suspect there's nothing wrong with the drive; it may be a firmware
bug,
but I was unable to apply firmware fixes using OCZ's updater for Linux. [etc]
You are running the latest firmware
Hi Philippe,
On Tue, 29 May 2012, Philippe Vanhaesendonck wrote:
This probably does not help too much, but FYI I am running Debian Wheezy
on my net6501 with an OCZ Vertex-3 SSD, and no problem encountered so
far...
Thanks for that data point. What exact kernel are you running?
Cheers,
On Wed, 30 May 2012 11:49:29 +0100 (BST), Chris Wilson
chris-soek...@aptivate.org wrote:
Thanks for that data point. What exact kernel are you running?
Chris,
I am using the the (almost) stock Debian Wheezy kernel which is Linux 3.2
I say 'almost', because I have to recompile to get pch_uart
On Tue, May 29, 2012 at 10:41 AM, Chris Wilson
chris-soek...@aptivate.org wrote:
I'm testing my first net6501 with an OCZ Petrol SSD. Everything seemed OK, got
the OS installed, then I started getting checksum mismatches from rsync, then
I/O errors, and then the drive stopped working
This probably does not help too much, but FYI I am running Debian Wheezy on my
net6501 with an OCZ Vertex-3 SSD, and no problem encountered so far...
--
Philippe
On 29/05/12 18:41, Chris Wilson wrote:
Hi all,
I'm testing my first net6501 with an OCZ Petrol SSD. Everything seemed OK, got
As a matter of general troubleshooting, I'd recommend trying the drive in a
PC (or other machine) running Linux, trying the same thing with a different
hard drive with the Soekris board, and swapping out cables with new in both
scenarios... with those errors, seems likely that the drive controller
Chris Wilson [chris-soek...@aptivate.org] wrote:
But after a power off (not just a hard reset) the drive is fine again!
Some people are seeing issues with Debian kernels (like this one) and
multiple
drives appearing to fail at the same time, but working fine after a reboot:
