This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
When will Intel release new firmware to fix "Bad Context 13x Error" for Intel X25-M G2?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2011 09:15 PM
As I know Intel X25-M G2 also has a drive capacity of 8MB issue, when will Intel release a new firmware to fix "Bad Context 13x Error" for Intel X25-M G2?
9 REPLIES 9
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2011 01:23 PM
You're right Relic. I'm just passing along the info that was provided in the release.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2011 08:51 PM
Never, I think.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2011 02:39 AM
I can confirm: I have a 160 GB X25-M G2 Postville (installed last fall) with similar issues. It ran as system/OS disc with Win 7 64 bit.
After I woke up the PC from the automatic "save energy" mode the system reported some errors (I can't recall what exactly). Hence I rebooted the system. It reports first an AHCI failure on port 2 (where the SSD sits). Additional investigations and tests (Parted Magic et al.) revealed the cause: 8MB and BAD_CTX!
Ironically this all happened a few days after Intel finally released the firmware update for the well documented 8 MB bug on the 320 series (If you read thru the release notes you will realize that for the Postville there is no updated FW; the last update goes back to Jan 2011). What a coincidence....
Since then I spend countless hours, not to say days, and tried to reactivate the SSD with all the hints and advices found in the 8 MB bug threads. Unsuccessful (in more detail: I was able to do a secure erase but I'm unable to format the SSD. The format process takes forever and after 100% completion it says formatting unsuccessful) It looks like this will be another RMA case. Great!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2011 06:34 AM
Because the firmware is nothing to do with hardware failure. Who told you that tis issue is similar? I think bad_ctx is some common error that can be caused by different failures.
For you I suggest to RMA the drive, if you can not or want to try fix it, then completely erase (twice or more) the drive in Victoria http://hdd-911.com/index.php?option=com_docman&task=docclick&Itemid=31&bid=79&limitstart=0&limit=15 http://hdd-911.com/index.php?option=com_docman&task=docclick&Itemid=31&bid=79&limitstart=0&limit=15 , but you need to get the capacity back to normal before (the known method is secure erase with parted magic and... you must use it twaice and with backdoor desribed in wiki article about sleep function - https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase ).
Good luck.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2011 11:58 AM
Thanks for the feedback and the additonal hints.
I think I will choose the RMA path; I already spent too many hours in trying to fix the problem. For example I used Parted Magic/Secure erase several times in a sequence. Everything seemed to be OK (Disk Health reported positive/correct values) but I was unable to successfully format the disc.
Let's hope the replacement process will not take forever...
