![]() |
|
#1
|
|||
|
|||
|
Intel SSD Dead after firmware update
Beware the new firmware update. I'm not saying it's what killed my Intel SSD, but my Intell SSD definitely died an hour after I installed it.
I installed the firmware (in IDE mode, not RAID), it ran fine for a while, then windows crashed and I get an error on one of my drives. It may be something else, but you may want to wait a while before installing to make sure this isn't a common issue. I haven't called Intel yet, I'll post again when I do.
|
|
#2
|
|||
|
|||
|
Yup! Looks like my SSD has died and won't boot anymore after firmware update. Wonder what happened. Oh well, I guess my computer will be down for a few weeks now and I'll have to reinstall everything again. Thanks Intel for messing up my new computer with the new Windows 7 OS.
I just read in the following thread 'looks like TRIM-enabled firmware for X25-M is out today' on page two that another person has decided to join the party and lost his SSD.
|
|
#3
|
|||
|
|||
|
Djkilla, did yours run fine for awhile before dying also? I'm starting to get spooked.
IT COULD HAPPEN ANY TIME!
|
|
#4
|
|||
|
|||
|
What error are you getting?
|
|
#5
|
|||
|
|||
|
It was booting into windows then it was detected and a message said to reboot. After 2-3 reboots with the same results, It now doesn't boot into windows and says 'Disk boot failure, insert system disk and press enter'.
|
|
#6
|
|||
|
|||
|
Mine boots to the Intel RAID controller, tells me one of the disks is okay, the other has an error (0), and after that they fail to boot.
|
|
#7
|
|||
|
|||
|
The same thing happened to me and I found this thread on Intel's forums: http://communities.intel.com/message/71383#71383
The drive was working perfect, I updated the firmware, booted into Windows, it made some updates and told me to reboot, then black screen. I disabled my raid setup in the bios and then I get an error message when trying to boot Windows. I can't even re-install because Windows 7 just hangs when trying to repair or re-install. I booted with a Linux Disc and it can't initialize the drive. So my guess is that its borked and Intel is about to have to issue a few thousand RMAs to everyone who did this.
|
|
#8
|
|||
|
|||
|
Poor Intel...
And Poor me... I want one of these drives so badly, but not until they reliably hit the <200$ mark. This can't be good for revenues = This can't be good for consumer pricing ![]()
|
|
#9
|
|||
|
|||
|
When I flashed mine, strange thing happened. I set SATA to IDE-Compatibility mode, and at the prompt where it asks if you want to update the firmware, after pressing y and enter, it just hung there for 30min with a blinking cursor. Thinking something was wrong, I reset the machine, but windows came back and the matrix storage manager reported that the firmware was updated. So far no crashes, but I'm running Vista atm, not Windows 7.
|
|
#10
|
|||
|
|||
|
I"m not at home right now, so I can't try this, but has anyone tried installing an older firmware? I have a second drive that isn't dead, and I"d like to keep it that way, but supposedly you can't install the new firmware twice.
|
|
#11
|
|||
|
|||
|
darn, was about to install my brand-spanking new Win7 Ultimate and this happens... when will Intel learn to test the firmware before releasing it?
|
|
#12
|
|||
|
|||
|
sucks to be a early adopter >_>
i feel for you guys
|
|
#13
|
|||
|
|||
|
Crap, crap, spoke too soon, disk i/o error. Getting some bad stuttering, and the diagnostic tool is showing the drive failing the write test. Looks like I'm on the RMA boat now.
|
|
#14
|
|||
|
|||
|
Are the drives bricked, or just all your data/partition(s) hosed?
|
|
#15
|
|||
|
|||
|
They are bricked. I would have happily re-installed Windows 7 since my data was on other drives, but the drive was inaccessible. I have my drive boxed up and ready to mail tomorrow morning unless Intel is able to wave a magic wand and tell me how to fix it. I've scared myself off of SSDs for a few years and would probably never touch an Intel SSD again. I'll gladly take a 5% real world performance hit for a drive that doesn't have a history of bricking itself when a firmware update is applied.
|
|
#16
|
|||
|
|||
|
I individually updated two drives in my Sugo build and the one that went into the classified got hosed on the second boot. It kept trying to boot the 100mb recovery partition which still seems readable. The rest of the disk however appeared as a raw partition and has issues.
![]() The write fails on this one because its the 100mb recovery partition. ![]() The Sugo's drive has been rebooted a few times and seems ok.
|
|
#17
|
|||
|
|||
|
Wow, I think this should be a sticky until Intel fixes this.. I have 2 Intel 80GB G2's that I have yet to install as I am waiting upon my i7 stuff to come in.. I am glad I have waited, and glad I found this thread. Let us know of any further issues or updates..
|
|
#18
|
|||
|
|||
|
fffffffffffffffffffffffffffffffffffffffuuuuuuu
i just updated the firmware and saw the message prompting me to reboot. then I log on here to say "flash successful" to find this awesome thread. LOL.... feels great knowing my hd will die at any moment or when I reboot. I feel like keanu in speed or some shit.
|
|
#19
|
|||
|
|||
|
Quote:
|
|
#20
|
|||
|
|||
|
I'm backing up my files just in case.
![]()
|
![]() |
| Thread Tools | Search this Thread |
|
|