-
1. Re: Update on "Bad Context 13x Error"
Lloyd Powell Jul 24, 2011 3:36 PM (in response to afrosty)
This is exactly what everybody was asking for, thank you. I look forward to the schedule being posted.
-
2. Re: Update on "Bad Context 13x Error"
john4200 Jul 24, 2011 5:31 PM (in response to Lloyd Powell )Agreed. Finally Intel has responded with an informative post about the 8MB bug. Better late than never, I suppose.
-
3. Re: Update on "Bad Context 13x Error"
smr Jul 24, 2011 6:03 PM (in response to john4200)
"Better late than never"?
Are you serious? Intel has reproduced a rare issue that affects a minority of users, has debugged it and isolated a problem, generated a fix, and is in the process of testing it. Not too shabby for a few weeks.
My thanks, at least, go to the Intel engineers for handling this efficiently.
-
4. Re: Update on "Bad Context 13x Error"
john4200 Jul 24, 2011 6:28 PM (in response to smr )The first report of the bug was more than 2 months ago, as you can see if you follow the link in the "Is 320 firmware buggy?" thread. And it is easy to reproduce. Just power cycle the drive many times. Which would have been an obvious thing to test internally on a new product that just had power-fail protection capacitors added to it, and has a datasheet that says it is rated for 50,000 power cycles.
Yes, I am serious.
-
5. Re: Update on "Bad Context 13x Error"
Goose Jul 24, 2011 6:35 PM (in response to afrosty)Thank you, intel engineers. It's relieving to hear that I may put my worries to rest.
-
6. Re: Update on "Bad Context 13x Error"
carsten Jul 24, 2011 7:56 PM (in response to afrosty)
Alan,
Thank you very much.
Will it be possible to apply the upcoming firmware fix to drives that are already suffering from this issue (thus restoring their capacity), or was it designed only to prevent it from happening in the first place (in which case all currently affected drives would have to be exchanged through RMA)?
-
7. Re: Update on "Bad Context 13x Error"
w00thisButtonDo Jul 25, 2011 12:52 AM (in response to afrosty)1. Are the "old" generations of the Intel SSD affected too (I have seen some reports for G1 and G2 about "8MB bug") or it's related to the other hardware problem?
2. New upcoming firmware will fix SSD with data loss or will restore capacity with user data on it?
-
8. Re: Update on "Bad Context 13x Error"
Jiri Jul 25, 2011 12:56 AM (in response to afrosty)
Hello,
I recovered my SSD by formatting it via secure erase tool.
However SMART attribute B8 is reporting an error now and I get a warning now everytime I startup my laptop: 1720 smart hard drive detects imminent failure failing attribute id b8.
Will this firmware update also fix this issue or should I rather RMA the SDD?
-
9. Re: Update on "Bad Context 13x Error"
Leonardo Jul 25, 2011 1:54 AM (in response to afrosty)
Just received my Intel 320 series 80GB SSD.
Packing Date: 24 May 2011
Batch #: CNCV15010B
Version #: G24397-601
S/N: CVPR1180028K080BGN
I will wait 2-3 weeks for the new firmware, before installing and using it.
Thank's foor all the forum info.
.
-
10. Re: Update on "Bad Context 13x Error"
James Jul 25, 2011 8:32 AM (in response to afrosty)
Do you know if I will be able to get my data back on a drive that has this issue with the firmware fix?
-
11. Re: Update on "Bad Context 13x Error"
Mathias Jul 25, 2011 10:10 AM (in response to afrosty)
Great.
I have the same problem with the Intel X25-M G1 160GB model that had the same error. Do you plan to issue a firmware for these devices so I can revive the device again?
-
12. Re: Update on "Bad Context 13x Error"
Marcis Jul 25, 2011 11:21 AM (in response to afrosty)
Phew. I am relieved.
Though my 120GB 320Series model is fine so far (knock on a tree) it is nice to know fix is coming
-
13. Re: Update on "Bad Context 13x Error"
John Jul 25, 2011 1:39 PM (in response to smr )
Well said. My thoughts exactly.
-
14. Re: Update on "Bad Context 13x Error"
w00thisButtonDo Jul 25, 2011 2:20 PM (in response to smr )It would be good not to produce this issue at all. Issue must be "isolated" on the developing stage of the product, not when it manufactured and sold out. This time it can be fixed with new firmware, not so crazy like for the P67 users, who used RMA to get the new motherboard/chipset revisons. Yes it's all free of charge, but WTF?