• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

SSD won't detect after TRIM enabled

WhenKittensATK

WhenKittensATK

Limp Gawd
Joined
Oct 6, 2009
Messages
320
I currently have a RAID 0 setup for my OS drive (2 regular HDDs). I recently bought a SSD to be my new OS drive. I read online that you can use TRIM when your Sata Controller is set to RAID as long as the SSD isn't in an array, which it wasn't.

So I enabled TRIM and a few minutes later, my computer froze and gave a BSOD (disappeared too fast to read). Now the SSD won't detect at all. I tried unplugging all devices and installing it on my laptop. Also tried swapping the ports on the PC, didn't work.

The SSD did come with the latest Firmware installed, Crucial 128 GB CT128M226 (TRIM support added).

Specs:
Intel C2Q Q6600 @ 3.4 GHz
Biostar Tpower I45
4 GB RAM
Nvidia 9800GTX+ 512 MB
Win 7 64 Bit
 
Last edited:
disconnect all other drives but the SSD from the system, and go into BIOS. Do you see the SSD there?
 
Curious, how did you 'enable TRIM'?

Sounds to me like you got a bad unit that just happened to fail right then. I can't think of anything you could have done to it that would cause it to not be detected anymore especially even when you move it to another machine.

I have heard about some issues with certain models of Crucial drives pulling a vanishing act like that, only cure I know of is an RMA.
 
Blue Falcon said:
Curious, how did you 'enable TRIM'?

Sounds to me like you got a bad unit that just happened to fail right then. I can't think of anything you could have done to it that would cause it to not be detected anymore especially even when you move it to another machine.

I have heard about some issues with certain models of Crucial drives pulling a vanishing act like that, only cure I know of is an RMA.
Click to expand...

Opened up Command Line and typed " fsutil behavior set DisableDeleteNotify 0 ″
It give me a response of " DisableDeleteNotify = 0 "
 
killagorilla187 said:
Who's idea was it for you to enable TRIM anyways? Certainly they are to blame....
Click to expand...
It was the same guy who told me to install Synergy so we could co-op HL2 and then having it end up destroying my Nvidia 8800 GTS (bad video memory, a bunch of red lines). That's 2 confirmed kills for the slayer of hardware.
 
if you dont see it in BIOS then the drive flash likely went to shit. see if there's a firmware recovery tool or reflash procedure on the drive. if not, it's RMA time.
 
That's an M225, right? If you can, I'd return it for cash or credit, and get a C300 instead. They are about the same price, but the C300 is better. The M225 is Indilinx, which is older technology.
 
LOUSYGREATWALLGM said:
Why did you have to enter the command "fsutil..."?

If the SSD supports TRIM feature, Windows 7 will do it.
Click to expand...
People said to enable TRIM, so I looked online to find out how to do it and found Corsair's guide and did it.

Does Win 7 do it automatically or something? If so no one ever told me. Nor did I find anything that said it did.
 
Contacted Crucial Tech Support and they said they sold all the stock they had they can only offer in-store credit, no exchanges.

So I really need some more input here.

EDIT: They do have the C300 64 GB SSD for $20 more. I may get that or just wait out the 12 months I have with in-store credit for the prices to lower a bit. My mobo only has Sata 3 GB/s, so not even sure if buying a Sata 6 GB/s addon card would even be worth the investment.
 
Last edited:
Krazyxazn said:
People said to enable TRIM, so I looked online to find out how to do it and found Corsair's guide and did it.

Does Win 7 do it automatically or something? If so no one ever told me. Nor did I find anything that said it did.
Click to expand...

If your drive has TRIM capable firmware and you're using Windows 7 with the proper AHCI driver(such as Microsoft's) then TRIM in enabled my default. There is nothing to turn on. The only thing a user has control over is a software implementation such as Intel's Toolbox or Wiper.exe for Indlinx drives
 
Krazyxazn said:
Contacted Crucial Tech Support and they said they sold all the stock they had they can only offer in-store credit, no exchanges.

So I really need some more input here.
Click to expand...

Don't know what input you're looking for... if the drive isn't detected in the BIOS by any machine you put it in, it's toast.

As was said earlier Windows 7 automatically sends TRIM commands so there shouldn't have been any need to manually enable it. Furthermore most people would have checked to see if it was enabled before actually manually toggling DisableDeleteNotify.

However with that being said there is absolutely no way that toggling the DisableDeleteNotify value could have caused your SSD to just die. This command has no direct interaction with the SSD itself, all it does is tell Windows 7 to begin notifying the SSD whenever blocks are deleted. It does this via the ATA "TRIM" command so that the SSD can erase them at it's leisure (thereby making them faster to write to later).

About the only suggestion I can make would be to see if there is a firmware update for the SSD. Perhaps flashing the firmware will bring it back to life. (Even if it's not seen in the machine's BIOS many firmware update utilities access the drive directly and bypass the system BIOS.)

Also try either changing all the BIOS ATA options to 'Legacy' and 'SATA' (instead of Native, AHCI, and/or RAID) and see if the drive is detected in the BIOS then. As a last resort try completely clearing the BIOS of the machine (CMOS clear jumper or button on the motherboard). Although honestly since the drive isn't detected in another machine this is really last ditch and probably futile.



And on a side note, I can't believe people actually bought these refurb SSDs. That kind of shit scares the hell out of me....
 
I was looking for a definitive post and yours was it. I'll be throwing it in the mail shoot and either waiting or picking up that C300 64 GB.

The SSD didn't show up in firmware updater so, all hope is lost. I like to at least try every possible solution, before giving up. What's strange is why enabling Trim manually would cause it to die. I mean if its already turned on by default, why would enabling what is already on cause it to crash. The only answer I probably get from that was because it was a Refurb drive, which doesn't answer it :p
 
Last edited:
Krazyxazn said:
I was looking for a definitive post and yours was it. I'll be throwing it in the mail shoot and either waiting or picking up that C300 64 GB.

The SSD didn't show up in firmware updater so, all hope is lost. I like to at least try every possible solution, before giving up. What's strange is why enabling Trim manually would cause it to die. I mean if its already turned on by default, why would enabling what is already on cause it to crash. The only answer I probably get from that was because it was a Refurb drive, which doesn't answer it :p
Click to expand...

The answer is abundantly clear. Enabling TRIM cannot and did not cause your SSD to go bad. The fact that it died shortly after you issued a completely harmless (and redundant) command to the operating system is mere coincidence.

Chalk it up to bad luck, or it being a refurb, or both. I personally wouldn't buy a refurb'ed SSD without knowing exactly how they are 'refurbished', tested, and determined to be good. I've seen too many manufacturers of various products that do very little in the way of actually refurbishing a defective product other than to send it right out the door again for some other poor soul to get stuck with.
 
Someone posted this on SlickDeals. I'll give it a try.

[This is how I fixed the disappeared drive]

The drive got disappeared and I'm not sure if it's because some MBR tools or SATA-ACHI laptop setting. Anyway the drive was no longer recognized.

I opened up the drive and found a couple pin-holes, one set of them is "factoryset", I shorted it with a paper-clip (or a staple) and now the drive can be recognized as "YATAPDONG BAREFOOT-ROM ....080". This seems to set the drive to the factory reset mode.

Now the drive can re-flashed by the 1571 destructive firmware (meaning all data is lost). 1571 firmware tool only runs in Windows (XP). Then I removed the "factoryset" jumper and upgrade the firmware to 1916 in DOS mode (I made s USB DOS boot drive).

I tried three different computers and only the Thinkpad laptop (Intel chipset, the others are VIA chipset) and in SATA-IDE mode works with the 1571 flasher.

Now the drive is revived but unfortunately I'll have to backup daily because the fix will destroy all data and no one knows when this will happen again. This is obviously a design flaw that the firmware is easily corrupted. The 1916 firmware is not safe otherwise we won't hear so many disappearing drives here.

This took me 2 days to figure it out after reading many many posts in the OCZ and Crucial forums. The Indilix controller is terrible for so many firmware corruptions.
Click to expand...

Hmm I'm getting this message when I try to flash it:
Error: bank configuration error (must be FFFF)
error at ..\..\host\host_mass_production.c 957

Controller is set to SATA-IDE and doing this under Windows PE, since my XP partition is on my Raid 0 drive. This is too demoralizing, I thought I had something going with this method.

EDIT 2:

It's alive.... with 1819 Firmware for now. Going to keep trying to get 1916 Firmware to work.
http://img641.imageshack.us/img641/2600/73229708.png
http://img842.imageshack.us/img842/3356/26223708.png

EDIT 3:

I put the SSD case back on and now its undetectable :p I'm just going to go through with the RMA. This is becoming too much of a hassle
 
Last edited:
You must log in or register to reply here.
Back
Top