1 2 3 4 8 Previous Next 113 Replies Latest reply: Jun 29, 2012 9:21 PM by Rhyando Go to original post RSS
  • 15. Re: Update on "Bad Context 13x Error"
    koitsu Community Member
    Currently Being Moderated

    Guest wrote:

     

    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?

     

    Your drive has other problems.  Attribute 0xB8 is End-to-End Error, which indicates the drive internally has a problem with data transition between the on-board cache and the actual NAND cells.  If the overall SMART health is failing, that indicates the normalised value (VALUE) has exceeded the alerting threshold (THRESH).  Secure Erase did not cause this problem; there's nothing you can do about it other than get a replacement drive.  Please file an RMA.

  • 16. Re: Update on "Bad Context 13x Error"
    Currently Being Moderated

    Is there information on which batches/serial #s are affected by the bug?

     

    I'm receiving shipment on a 160GB 320 and would obviuosly rather wait for the new firmware before installing an OS.

  • 17. Re: Update on "Bad Context 13x Error"
    who Community Member
    Currently Being Moderated

    Hi everyone,

     

    I bought an Intel 320 120Gb less than a week ago.

    Ran the firmware update tool and was told it had the latest version of firmware.

     

    I wasn't aware of the "BIOS Password Issue" (http://www.intel.com/support/ssdc/hpssd/sb/CS-030724.htm) but read about the power issue elsewhere.

     

    I enabled password on the drive, rebooted a couple of times (asking me for password each time) and proceed to install Windows 7 onto it.

     

    Halfway through the installation (~20+%), i decided i should perform a secure erase on the drive first (to replace the hardware based encryption key),

    hence i powered off the notebook.

     

    ---

    Each Intel SSD 320 Series has a unique key when it

    leaves the factory. The user can simply start using the
    SSD and data is encrypted with that unique key.
    However, if the user prefers a new key, one can be
    generated by executing a Secure Erase or Enhanced
    Secure Erase on the SSD.

     

    Source: http://download.intel.com/design/flash/nand/325201.pdf

    ---

     

     

    I put the drive into an external USB3.0 enclosure (using VIA VL700 chipset)

    (http://www.hornettek.com/pcaccessory/index.php/25q-hdd-enclosure/usb-30/panther)

    and connected it to another Windows 7 machine so that i could run Intel's SSD Toolkit on it.

    It could not detect the drive and then i realized it was password protected.

    Disconnected the USB enclosure, took the drive out from the enclosure.

     

    Put the drive back onto the machine (which i enabled the password on, and was installing Windows 7).

    Powered it up, asked for password, keyed it in...it didn't recognize my password anymore!

    I've attempted this many times and it doesn't work on either notebooks i had.

     

    Connected the drive to a PC, ran SSD Toolkit, drive is detected but unable to perform a Secure Erase (as drive was password locked).

    Full LBA was detected.

    I exported the SMART attributes and i could put it up somewhere if anyone wants to take a look.

     

    So, my conclusion at this time, ATA password on the 320 Series 120Gb drive was corrupted due to sudden power-loss.

    I didn't thought it would be this serious as Intel has enchanced protection against it (http://download.intel.com/design/flash/nand/325207.pdf)

     

    Now i'm stuck with the drive bought just a few days back.

    Hope Intel will look into this issue too and let all of us know if the new firmware will fix this or would i need to RMA the drive?

  • 18. Re: Update on "Bad Context 13x Error"
    Currently Being Moderated

    The firmware update process ought to be interesting.   From the "BIOS password issue" document:

    If you have not enabled a BIOS drive password, do not be enable the BIOS drive password.

     

      I'm not sure exactly what that means.   But the firmware update procedure that I reviewed directs that the drive password be turned off:

     

     

    DRIVE PASSWORD
    The Firmware Update Tool will not run correctly if your 
    Drive Password is set. Make sure that your Drive Password 
    is turned off (in your BIOS Settings) before beginning the 
    firmware update process. After the firmware update has completed 
    successfully, turn the drive password on again.

     

    The BIOS password issue document recommends:

     

    If a BIOS drive password has been enabled, do not change or remove it and contact Intel® Customer Support for more information.

     

    So since I already have a BIOS password, the firmware update will be a special procedure at minimum.

  • 19. Re: Update on "Bad Context 13x Error"
    Currently Being Moderated

    Took a while we have already thrown away disks...

  • 20. Re: Update on "Bad Context 13x Error"
    magr01ino Community Member
    Currently Being Moderated

    Any updates on this topic? Still eagerly awaiting the firmware update before I want to put the new RMA drive into my macbook..

  • 21. Re: Update on "Bad Context 13x Error"
    vegan Community Member
    Currently Being Moderated

    I have seen comments in the media over this issue for quite a while now.

     

    Hopefully Intel can figure out what the firmware needs to do be less sensitive to power failures etc.

     

    Given the sensitivity I suggest using a backup power supply.

  • 22. Re: Update on "Bad Context 13x Error"
    w00thisButtonDo Community Member
    Currently Being Moderated

    It's not a power failure. Don't believe every word said in first message. Many of users have installed their SSDs into laptops, so backup power supply is already built-in and looks like this does not help at all.

  • 23. Re: Update on "Bad Context 13x Error"
    vegan Community Member
    Currently Being Moderated

    I mostly see SSD in large data centers not so much in a personal machine

  • 24. Re: Update on "Bad Context 13x Error"
    sarreq Community Member
    Currently Being Moderated

    so...  any update on a release date?  I just bought an 80GB 320 to replace my system drive, without knowing about this problem beforehand.  I'd like to have a fix handy before I install it.

  • 25. Re: Update on "Bad Context 13x Error"
    w00thisButtonDo Community Member
    Currently Being Moderated

    Desktop oriented SSD  series in datacenters? That's fun

  • 26. Re: Update on "Bad Context 13x Error"
    vegan Community Member
    Currently Being Moderated

    Some shops I have read about have used them in servers and RAID arrays to perk up performance. I cannot imaging a server that busy as even facebook is interested in faster network speed over server woes.

  • 27. Re: Update on "Bad Context 13x Error"
    w00thisButtonDo Community Member
    Currently Being Moderated

    Practically every manufacturer of SSDs have minimum two classes of production. Desktop and enterprise (MLC flash is used for the desktop mostly and SLC flash for enterprise). Why would facebook use an desktop oriented SSDs, instead enterprise? May be just for the lower price? But the reliability, acccess/reading speeds  are lower too (teoretically).

    Even if facebook, hypothetically, is greedy and using cheaper MLC SSDs in their datacenter, I don't think they are using Intel SSD, as it is not cheap enough in conclusion with other similar class and speeds.

  • 28. Re: Update on "Bad Context 13x Error"
    Desiderius Community Member
    Currently Being Moderated

    Intel says that the 320er Serie is also for server. Only the 510er Serie have no passing for server. Intel always are proud to say thats the forefather X25-M is so good in server. Here an translation from an german articel:

     

    Intel is particularly proud that in the servers of a unnamed OEM  customers used X25-m is still significantly less than expected: only 0.46  percent of the more than 100,000 storage were returned (annual return rate, ARR)  and only 0.26 percent were actually broken.

    http://www.heise.de/ct/meldung/Intel-SSD-320-Nachfolger-der-Baureihe-X25-M-1216456.html

     

    We have over 150 Intel X25-M Generation 1 and Generation 2 SSDs for customers in hardcore database servers. Such customers need the speed advantage over SAS and know the risk of the new technologie SSD. But the speed plus is impressive. Also i can say that we have a really low failure rate on the X25-M SSDs over the 2 years. We also testing Intel X25-E Series but the customers is the Price/Gigabyte to expensive.

     

    From 64 Intel 320er 160GB SSD are 17 broken after 3-5 days of stress testing with the 8MB bug. Now we stop all tests and hope for the firmware update.

  • 29. Re: Update on "Bad Context 13x Error"
    w00thisButtonDo Community Member
    Currently Being Moderated

    Nothing to say. Thats why 8mb bug exists may be

    Intel tries to boost sales of x25-e SLC series.

    And your data-center don't use backup power supplies also, because it's too expensive for customers? :/

1 2 3 4 8 Previous Next

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points