DON'T Buy Intel 320 SSDs

First you say it is one in a million. I provide links showing that it is obviously much more common than 1 in a million. Oh, you say, I did not really mean one in a million

i explained there, and here again, that is an expression not meant to infer actual statistical analysis. you are trying to muddy the waters again here...this is your tried and true tactic of picking at "or details that are largely irrelevant in an attempt to shut out the conflicting idea. The core of the post will be left alone since it isn't easy to contradict what the person is actually saying."

the meaning was simply: it is a corner case, a rare hard to reproduce error. I have repeated that numerous times, how tiring.

I do not propose to say how this issue is happening. I am just saying that in all of the internet there are 7 individuals who have experienced this issue with the 320 SSD. out of a very vast number that have been sold. the rate of this is obscenely low, not nearly enough to merit any type of panic, or hypocritical statements of "dont buy intel 320"

you are again trying to avoid the real issue here. you keep stating "all these people" these "diverse hardware and usage cases" "whatever is making it so common"
there arent all these people
there arent diverse hardware and usage cases, 7 cases does not qualify as this.
it is not common. not by any means. this is so uncommon it is ridiculous.

I notice that you are sidestepping everything that is asked of you, so again, would you care to tell us:
what qualification do you have, or experience in this arena to make these statements?

you are avoiding the question. i asked you directly.
 
Last edited:
I do not propose to say how this issue is happening. I am just saying that in all of the internet there are 7 individuals who have experienced this issue with the 320 SSD.

Wrong again.

And I already told you what you need to do if you want me to answer your questions. You said you had no questions for me. Can you ever say something correct and not change again a few minutes later? Changing one's mind when presented with new data is one thing, but you seem to randomly bounce around from one position to another, wishy-washy, never meaning what you wrote a few minutes ago.
 
you are dodging the question. you are in a corner, and you cant get out. you are simply trying to answer every single post with another trolling flamebait post.
answer the question, but like the saying goes
"Better to keep your mouth closed and be thought a fool than to open it and remove all doubt"
John

EDIT:i have not changed my position once this entire thread. I started saying its inconsequential, ane we all know now it is. On every forum out there these threads about this all end with the same thing, people saying "some idiots are making a moountain out of a molehill."
'im sure you will respond with another flamebait. have fun with that John. Your refusal to say how in the world you are so smart and knowledgeable and what qualifications you have, says it all.
 
Last edited:
You ridicule me, call me a hypocrite, twice, then accuse me of making personal attacks, and then expect me to respond to your personal questions? Seriously?

I made a number of clear, technical points in this thread, clearly explained. When a question of terminology came up, I provided a link to wikipedia which gave a page long discussion of the term.

You started in with scoffing, then saying one thing, then making personal attacks, then saying another thing, then changing again, then saying that you don't want me to answer your questions, then demanding that I answer your questions. When the issue of terminology came up, you provided a link to a two sentence definition that did not even match your usage of the term.

Even if we ignore the personal attacks, your side of the debate looks extremely thin and unpersuasive.

The evidence is preponderantly on the side of the 8MB bug being a design flaw in the Intel 320 SSD, and Intel has only issued a vague statement that they are aware that some users have reported experiencing the 8MB bug. Intel gave no indication when, or if, this bug may be fixed, or even if they are working on a fix. Also, no suggestions on how to avoid this problem or minimize the chance of it happening. For an SSD whose only real selling point is its reliability, this is NOT GOOD. Intel needs to do much better if I am to buy any 320 series SSDs in the future.
 
You have no response. that is why you aren't answering.
Well, you have a response, but it shows your unqualified.

Im not going to be a pompous ass here and try to throw around my own qualifications. no fun in epeen swinging.
 
Last edited:
I have two 320 128GB (one in a laptop and one in a desk computer) for about three months and no problems so far
 
Well, you have a response, but it shows your unqualified.

That could be it. Or it could be that I just don't want to answer personal questions to someone who has repeatedly insulted me.

But feel free to think of me as a 16 year old high school dropout if it helps your ego. Just don't PM me with any more questions like what is the difference between TB and TiB.
 
Just don't PM me with any more questions like what is the difference between TB and TiB.
Reply With Quote
.
The only reason i asked was i was bored . If you recall correctly, there was a very respected forum member that had been reporting values incorrectly all along.
my question was IN JEST.
I figured you were going to say something cutting, or smart alec.

how in the hell did you not get that? one of the smartest guys was reporting it wrong over and over for days, so i said:

hey give me a quick primer here on TiB v TB?? i thought it really isnt that much of a difference!

its a joke you nincompoop! the only thing i forgot to add was DUH!!! at the end.
when you replied with the actual technical definition i thought: well. he didn't get it.

see your cutting sarcasm can be funny at times, when you do not let your ego get in the way. in this case i just wanted to hear you say something funny.

man thats it? LOL

you not answering is not because you are offended. that is bullshit and you and everyone who is actually bothering to read this drivel (and believe me john, no one is watching anymore, so quit putting up a front, this is a dead thread) knows it. You have no technological expertise.

one last thing:
JARGON
1. Nonsensical, incoherent, or meaningless talk.
2. A hybrid language or dialect; a pidgin.
3. The specialized or technical language of a trade, profession, or similar group.
how can you purport to know what is said in the technical language of a trade, if you are in no way connected to it?
you have no connection to the industry at all, yet you purport to know the inner workings and jargon of us that DO ACTUALLY have respected, sought after opinions from people in the industry.
 
Last edited:
Here is the thing Red, he is insulting and rude. I have pointed out several instances in this very thread where he has intentionally laid flamebait for other members, and flat out insulted them.
unprovoked.
Take me out of the equation, then go look at his insulting and inflammatory posts, here, and at other forums. I could set here and link a multitude of posts from this very thread, and others, where he has insulted and attacked other members of this forum. Im not even involved in these discussions. So you can remove me from the equation.
Bullying those that do not have as much knowledge as you, and using every "trick" in the forum book to do so, is wrong. He is merely shouting out all opposition.
Now, i have the balls to stand up and call him on it. I have the knowledge to do so, too.
Its easy to pick on the "little guy" with little to no knowledge in a setting like this, and i see it all the time.
I am active on tons of forums, and i have literally tens of thousands of posts on a multitude of storage forums. For years.
I have never had the issues on any of them that i have here. I have never been attacked and insulted in the manner that happens here.
The thing is, it isnt the good members here that do it. There is a precious few. And one especially.
Now, heres the deal. I attempted to make "peace" after that and be cool. But seriously, your not going to set here and attack others in an insulting manner unprovoked, then attack me as well.
I will stand up and say something. You say you learned to STFU right? in your post thats your own words. Thats your prerogative. Not mine.
I will not acquiesce to someone merely because they attempt to shout over me. I may come off as aggressive in this thread, but that is because of previous experiences with this individual.
one or both of you get banned or worse because of a simple disagreement.

ive never been in any trouble here. Or anywhere else for that matter. if there is an issue a mod will talk to me im sure.
me and john will learn to coexist, as we do elsewhere.
 
Last edited:
A joke, huh?

Computurd said:
hey give me a quick primer here on TiB v TB?? i thought it really isnt that much of a difference!

johnw said:
About a 10% difference.

T=(1000)^4
Ti=(1024)^4

Ti / T = 1.0995

Computurd said:
thx, that is a much bigger difference than i thought, i was thinking 4 percent!

No doubt this was a joke, too:

Computurd said:
hey i like your way of measuring the latency from the iops. one thing though, could you give me the formula for figuring iops into latency?

johnw said:
Well, to do it completely accurately is a little tedious, since to be completely accurate

IOPS = 1 / (latency + block_transfer_time)

but we cannot observe latency and block_transfer_time separately -- we can only measure IOPS. But if we measure IOPS for a range of block sizes, say from 4KB, 8KB, 16KB ... up to 1MB, then make a plot with 1/IOPS on the y-axis, and block size on the x-axis, then if you fit a line to the data, the y-intercept will give you the latency, since the latency is basically the time to complete the operation when the block size is zero.

That would be the completely accurate way to do it.

But if you just want a quick and dirty estimate, you can assume that 4KB block is close enough to a block size of zero, and then just take 1/IOPS for 4KB block:

latency = 1 / IOPS

That is assuming QD=1. If QD > 1, then the approximate formula is

latency = QD / IOPS

Computurd said:
dude that is awesome. i appreciate it, and that is now written in a text file LOL sometimes im a little slow
Thanks!

As for insults and trolling, this thread seemed to be fine until posts like these:

Computurd said:
this statement is all the proof that we need that you have absolutely no idea what you are talking about.

Computurd said:
yes i know...dont feed the trolls....just irritates me that there are people who post rubbish for whatever reason (usually they are just idiots, with little to no real knowledge) then it is read by people who are just researching products/buys and come across this junk. to not comment and "light the way" showing the truth, well, its almost criminal, isnt it?

and Skakruk, cmon dude. you didnt post this as some "grand design" i dont buy that. seriously dude, your not that smart.
certainly if you were, you wouldnt outline for us how you are intentionally trolling.

you are whining, like 90 percent of the internet.
thing is, this bug hasnt even affected you.
you are simply being a drama queen.

Computurd said:
ROFLMAO!!

i notice that you aren't concerned enough to take your data off of your very own device.

that is a bit hypocritical, eh?

EDIT: really john, what are you buying these days? you say dont buy OCZ, or anything SandForce, or now intels? seriously? every time someone says "dont buy this" you are the first in the thread screaming.
what SSD is up to your standards?


As I told you before, if it helps your ego, feel free to pretend that I am a 16 year-old high-school dropout who does not even know 1/10 of what you do. And feel free to insult me and defame me all you want. Just don't expect me to answer your PM'ed questions about TiB and IOPS any more.
 
Last edited:
John, in reference to the TB v TiB: I was being polite. It was apparent you didnt get it. At the moment i was actually on a call with a Rep, and just shot off a quick response.

Again, you are trying to derail the main thrust of the argument. This is merely a distraction so that you do not have to address the real issue.
you constantly try to snipe small details, and now you are bringing PM's from another storage site into this discussion LOL

Here is the thing that you are avoiding.

This bug with the Intel 320 is rare. a corner case. extremely hard to reproduce.

It is so rare in fact, that no new cases have came about. The cases are confined to that thread at Intel.

This does not merit a vendor bashing thread where people are told "dont buy Intels"
that is the case in point. period.

you are attempting to derail because you do not want to address the issue. And the issue is showing that there is no call for panic.

funny that earlier you advised another user to buy the G2 instead of the 320. If you stop and think about it, that is ridiculous. They use the same freaking controller!!!
------------------------------------------------------------------------------------------------------------------------------------------------------------
EDIT: i see that you have edited your post above mine. I did ask you for the formula that you were using to figure the IOPS. It seemed that you were using a different formula. Simple as that. and in the posts that we were discussing, you were. when i was checking it, my results came up different.

*John
Well, to do it completely accurately is a little tedious, since to be completely accurate

first you say this, and explain what i already know.

*John
But if you just want a quick and dirty estimate, you can assume that 4KB block is close enough to a block size of zero, and then just take 1/IOPS for 4KB block:l

here you explain that you are using a different method. When i was checking using the actual correct manner, your results were different/wrong.

I didnt call you out and say "HEY! your wrong on that!" in the thread. I was curious as to why your numbers were different. if i were to pattern someone else i know i could have asked them why it was off in public and been rude and condescending.
Simple as that.
its called "colloboration" John, and apparently your ego again makes you think that you were being asked an obviously simple question because of lack of knowledge. you do not understand decency and asking for things in a nice manner, as opposed to being rude and aggressive.
 
Last edited:
Here is the thing that you are avoiding.

This bug with the Intel 320 is rare. a corner case. extremely hard to reproduce.

It is so rare in fact, that no new cases have came about. The cases are confined to that thread at Intel.

This does not merit a vendor bashing thread where people are told "dont buy Intels"
that is the case in point. period.

you are attempting to derail because you do not want to address the issue. And the issue is showing that there is no call for panic.

funny that earlier you advised another user to buy the G2 instead of the 320. If you stop and think about it, that is ridiculous. They use the same freaking controller!!!
 
There may be a troll in this thread, but it certainly is not the OP.

Is it really so difficult to read about the issue you are commenting on, then think about it a little bit before posting? When you don't do this, you look like an idiot and decrease the SNR. I just don't see how someone could possibly be commenting in this thread multiple times without realizing that the issue under discussion is related to POWER CYCLING the SSD.

And the troll still has not bothered to read about the issue under discussion and think about it and address the issue in a comment.

No, certainly not you. You have clearly read all about the issue and thought about it before making any ridiculous comments.

Don't feed the troll.

So all the posts of people who simply turned on their computer, or rebooted it, and had the 8MB bug are falsified? It must be strange being so much smarter and more honest than everyone else on the Internet, huh?



these are just your insulting posts john in this thread. the last one was an unprovoked comment to another member. I dont have time to start linking all the other stuff you post in other threads that i DO read.
 
let's all just hold hands and skip through the fields full of fluffy bunnies.
I'm thinkin' a poppy field would help all these intelligent guys chill out. :)

I have respect for all involved in this thread and am sure that cooler heads will prevail.
 
Sorry Blindedbyscience, I didn't think that I had insulted anyone. *chill pill taken* :)
/off topic

As for the SSD, I think that when Intel releases a firmware update, it will alleviate all of these problems.
It would be nice to see some official documentation though from Intel.

EDIT:

Hopefully that helps.
 
Last edited:
well what could have been a useful thread became quite the drama with two posters that should have left this thread long ago and taken thier battle elsewhere. it kind of sucks when your just interesting in reading about a potential issue for a product your thinking about buying. I dont care who thinks they are right or wrong, how about be adults and move it along, it makes both seem childish and hell bent on winning the 'debate' and showing how much better they are lol


As far as the topic itself, when I first heard about this, I was definitely interested in hearing more. It may not be a big deal right now, but Im willing to wait before deciding which ssd to buy for a little while and see if Intel comes up with a fix or there is some explanation for a cause. When Im going to be dropping alot of money for an ssd, Im going to wait until im confident in what im going to buy.
 
well what could have been a useful thread became quite the drama with two posters that should have left this thread long ago and taken thier battle elsewhere. it kind of sucks when your just interesting in reading about a potential issue for a product your thinking about buying. I dont care who thinks they are right or wrong, how about be adults and move it along, it makes both seem childish and hell bent on winning the 'debate' and showing how much better they are lol

So, you just thought you would resurrect the thread, which had died down on its own, just so you could get in your little dig, huh? Well done!
 
As far as the topic itself, when I first heard about this, I was definitely interested in hearing more. It may not be a big deal right now, but Im willing to wait before deciding which ssd to buy for a little while and see if Intel comes up with a fix or there is some explanation for a cause. When Im going to be dropping alot of money for an ssd, Im going to wait until im confident in what im going to buy.

We've all exhausted our opinions in it and until Intel releases some PR or documentation on this issue (directly, not random websites) or releases a firmware update, it needs to just sit.
 
Back
Top