OCZ SDD drives destroyed by hard reset or power off?

I am getting the unpleasant feeling that my SDD is dying, again.

I have done a button style power off and one or two hard resets
recently. And now I am getting a CHKDSK error.

In any case, if the indication is correct, this will be the second
OCZ SDD that has gone belly up in my system.

On 17 Dec 2011 22:26:39 GMT, John Doe wrote:

I am getting the unpleasant feeling that my SDD is dying, again.


Although I don't use RAID, it seems like the only way to prevent down
time.

I have done a button style power off and one or two hard resets
recently. And now I am getting a CHKDSK error.

In any case, if the indication is correct, this will be the second
OCZ SDD that has gone belly up in my system.

On Sat, 17 Dec 2011 22:26:39 +0000, John Doe rearranged some electrons to
say:

I am getting the unpleasant feeling that my SDD is dying, again.

I have done a button style power off and one or two hard resets
recently. And now I am getting a CHKDSK error.

In any case, if the indication is correct, this will be the second OCZ
SDD that has gone belly up in my system.

Even solid state disks are not immune to failure. I recently had one
that admittedly is not in an office environment (it is in an amateur
radio repeater system) go bad after 3 years of 24/7 operation. The
failure mode was interesting... the system was still running (CentOS
Linux) but I could no longer write to any of the filesystem. Reads
worked fine, and the kernel was still running (without logging anything,
though). Once I rebooted it, it refused to start back up. We replaced
it, and restored the system with a backup. You do have a current backup,
don't you??

david none nospam.com wrote:

John Doe rearranged some electrons to say:

I am getting the unpleasant feeling that my SDD is dying,
again.

I have done a button style power off and one or two hard resets
recently. And now I am getting a CHKDSK error.

In any case, if the indication is correct, this will be the
second OCZ SDD that has gone belly up in my system.

Even solid state disks are not immune to failure. I recently
had one that admittedly is not in an office environment (it is
in an amateur radio repeater system) go bad after 3 years of
24/7 operation. The failure mode was interesting... the system
was still running (CentOS Linux) but I could no longer write to
any of the filesystem. Reads worked fine, and the kernel was
still running (without logging anything, though). Once I
rebooted it, it refused to start back up. We replaced it, and
restored the system with a backup. You do have a current
backup, don't you??

Lots. I would be off-line for at least 30 minutes...

I suppose a diagnostics utility from OCZ might be useful, but I
haven't looked (yet).

On 12/17/2011 5:26 PM, John Doe wrote:
I am getting the unpleasant feeling that my SDD is dying, again.

I have done a button style power off and one or two hard resets
recently. And now I am getting a CHKDSK error.

In any case, if the indication is correct, this will be the second
OCZ SDD that has gone belly up in my system.

I recently (last week) had my OCZ SSD start acting badly. It was pretty
much unusable. I contacted OCZ to go through the procedure to send it
back. Jeff, a tech guy there emailed me to update the firmware on my
SSD. I did and it fixed the drive. I did have to erase the drive
(sometimes you don't) but I had a backup image on another drive, so
there was no loss.

Charlie

On Sun, 18 Dec 2011 20:28:14 +0000 (UTC), david
wrote:

On Sat, 17 Dec 2011 22:26:39 +0000, John Doe rearranged some electrons to
say:

I am getting the unpleasant feeling that my SDD is dying, again.

I have done a button style power off and one or two hard resets
recently. And now I am getting a CHKDSK error.

In any case, if the indication is correct, this will be the second OCZ
SDD that has gone belly up in my system.

Even solid state disks are not immune to failure. I recently had one
that admittedly is not in an office environment (it is in an amateur
radio repeater system) go bad after 3 years of 24/7 operation. The
failure mode was interesting... the system was still running (CentOS
Linux) but I could no longer write to any of the filesystem. Reads
worked fine, and the kernel was still running (without logging anything,
though). Once I rebooted it, it refused to start back up. We replaced
it, and restored the system with a backup. You do have a current backup,
don't you??

What you're seeing isn't a failure per se, but rather the drive
reached the end of the expected write life. There were no sectors
left that were listed as ok to write to so the drive went read-only.

Loren Pechtel lorenpechtel hotmail.com wrote:

david none nospam.com wrote:
John Doe rearranged some electrons to say:

I am getting the unpleasant feeling that my SDD is dying,
again.

I have done a button style power off and one or two hard
resets recently. And now I am getting a CHKDSK error.

In any case, if the indication is correct, this will be the
second OCZ SDD that has gone belly up in my system.

Even solid state disks are not immune to failure. I recently
had one that admittedly is not in an office environment (it is
in an amateur radio repeater system) go bad after 3 years of
24/7 operation. The failure mode was interesting... the system
was still running (CentOS Linux) but I could no longer write to
any of the filesystem. Reads worked fine, and the kernel was
still running (without logging anything, though). Once I
rebooted it, it refused to start back up. We replaced it, and
restored the system with a backup. You do have a current
backup, don't you??

What you're seeing isn't a failure per se, but rather the drive
reached the end of the expected write life. There were no
sectors left that were listed as ok to write to so the drive
went read-only.

Then the manufacturer claims of 1.5 million hours mean time
between failure (MTBF) were all bogus. In that case, hopefully
they have stopped making those silly claims.

In message m someone
claiming to be John Doe typed:

Loren Pechtel lorenpechtel hotmail.com wrote:

What you're seeing isn't a failure per se, but rather the drive
reached the end of the expected write life. There were no
sectors left that were listed as ok to write to so the drive
went read-only.

Then the manufacturer claims of 1.5 million hours mean time
between failure (MTBF) were all bogus. In that case, hopefully
they have stopped making those silly claims.

I don't think MTBF means what you think it means; A sample size of 1
isn't sufficient to determine whether it's bogus or not.

--
It's always darkest before dawn. So if you're going to
steal your neighbor's newspaper, that's the time to do it.

DevilsPGD Still-Just-A-Rat-In-A-Cage crazyhat.net wrote:

In message 4eeeb35a$0$5498$c3e8da3$eb767761 news.astraweb.com someone
claiming to be John Doe jdoe usenetlove.invalid typed:

Loren Pechtel lorenpechtel hotmail.com wrote:

What you're seeing isn't a failure per se, but rather the drive
reached the end of the expected write life. There were no
sectors left that were listed as ok to write to so the drive
went read-only.

Then the manufacturer claims of 1.5 million hours mean time
between failure (MTBF) were all bogus. In that case, hopefully
they have stopped making those silly claims.

I don't think MTBF means what you think it means; A sample size of 1
isn't sufficient to determine whether it's bogus or not.

Are you drunk?

--














--
It's always darkest before dawn. So if you're going to
steal your neighbor's newspaper, that's the time to do it.



Path: news.astraweb.com!border6.newsrouter.astraweb.com! news-out.octanews.net!indigo.octanews.net!news.glorb.co m!feeder.erje.net!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: DevilsPGD Still-Just-A-Rat-In-A-Cage crazyhat.net
Newsgroups: alt.comp.hardware.pc-homebuilt
Subject: OCZ SDD drives destroyed by hard reset or power off?
Date: Sun, 18 Dec 2011 22:26:25 -0800
Organization: Disorganized
Lines: 20
Message-ID: lbfte79o4oiurfd8q0ts9rud3irvvt9fkk 4ax.com
References: 4eed171f$0$2326$c3e8da3$460562f1 news.astraweb.com jclicu$l5k$1 dont-email.me 0r9te7docoeaeee09465dorkfgsar5mlj4 4ax.com 4eeeb35a$0$5498$c3e8da3$eb767761 news.astraweb.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: individual.net UIJ2l+Ka9afc13b4Xg38dQkOHT6mKFj/3F4XDp/ZdHHf2n2lZj
Cancel-Lock: sha1:HZCd9LKhJ40lv++uGfOkqHLF7i8=
X-Newsreader: Forte Agent 6.00/32.1186

Loren Pechtel wrote:
On Sun, 18 Dec 2011 20:28:14 +0000 (UTC), david
wrote:

On Sat, 17 Dec 2011 22:26:39 +0000, John Doe rearranged some electrons to
say:

I am getting the unpleasant feeling that my SDD is dying, again.

I have done a button style power off and one or two hard resets
recently. And now I am getting a CHKDSK error.

In any case, if the indication is correct, this will be the second OCZ
SDD that has gone belly up in my system.
Even solid state disks are not immune to failure. I recently had one
that admittedly is not in an office environment (it is in an amateur
radio repeater system) go bad after 3 years of 24/7 operation. The
failure mode was interesting... the system was still running (CentOS
Linux) but I could no longer write to any of the filesystem. Reads
worked fine, and the kernel was still running (without logging anything,
though). Once I rebooted it, it refused to start back up. We replaced
it, and restored the system with a backup. You do have a current backup,
don't you??

What you're seeing isn't a failure per se, but rather the drive
reached the end of the expected write life. There were no sectors
left that were listed as ok to write to so the drive went read-only.

It's more likely to be a firmware issue. SSD drives have their own
processor inside, and a firmware load. And the SSD drive is "busy"
internally, even when you aren't using it. It's pretty hard to
test those firmwares, and remove all the bugs from them. The
firmware has to be "correct by design", because lab testing
simply won't uncover all the bugs. (This is something I learned
from my computer design days, is that lab testing, gets the
error rate in design down to a certain level. But if your
design techniques suck, it shows. And that's what modern
SSDs look like to me - inadequate designs, rushed out the door.)

I thought there was some SMART stat, which kept track of write life.
Maybe people should be eyeballing that, once in a while. Or perhaps,
simply recording the SMART stats every day. Then, when the device
fails, go back and look at the stats, and see if there is any reason
to suspect it was actually media.

http://en.wikipedia.org/wiki/S.M.A.R.T.

"233 0xE9 Media Wearout Indicator

Intel SSD reports a normalized value of 100 (when the SSD
is new) and declines to a minimum value of 1. It decreases
while the NAND erase cycles increase from 0 to the
maximum-rated cycles."

So there is a way to track it. Too bad there isn't much adherence
to standards out there. You can't really rely on all drives,
doing SMART exactly the same way. And that was true, even with
hard drives. The important parameters may be there, but many of
the others, differ from design to design.

You really need an article about SMART, that compares what the
various manufacturers and controller designs are doing, before
deciding indicators like that actually mean something.

Paul