Community
09-03-2011 05:53 PM - edited 09-03-2011 05:55 PM
Ok, Crucial's response was a series of questions and the follow procedure:
------------------
In most cases, your SSD can be returned to normal operating condition by completing a power cycle. The process will take approximately one hour.
We recommend you perform this procedure on a desktop computer because it allows you to only connect the SATA power connection, which improves the odds of the power cycle being successful. However, a USB enclosure with an external power source will also work. Apple and Windows desktop users follow the same steps.
1. Once you have the drive connected and sitting idle, simply power on the computer and wait for 20 minutes. We recommend that you don't use the computer during this process.
2. Power the computer down and disconnect the drive for 30 seconds.
3. Repeat steps 1 and 2 one more time.
4. Reconnect the drive normally, and boot the computer to your operating system.
5. If the latest firmware is has not been updated to your drive, do so. Go to http://www.crucial.com/support/firmware.aspx for our firmware updates.
A laptop computer will also work, but you’ll have connect the drive and navigate to the systems BIOS menu. (Please refer to your system manufacture’s documentation on how to access the BIOS.) Allowing the drive to sit in the BIOS will improve the odds that the power cycle will work. For laptops, we don’t recommended using a USB enclosure powered via USB. In addition, Apple laptop users must boot the system to the open firmware.
1. Laptop users will need to be in the BIOS menu, or open firmware as stated above. The computer will need to stay powered for 20 minutes. We recommend you don’t use the laptop during this process.
2. Power the computer down and disconnect the drive for 30 seconds.
3. Repeat steps 1 and 2 one more time.
4. Reconnect the drive normally, and boot the computer to your operating system.
5. If the latest firmware is has not been updated to your drive, do so. Go to http://www.crucial.com/support/firmware.aspx for our firmware updates.
------------
Maybe this will be of use to some of those having issues with the M4 suddenly being unrecognized by BIOS.
They did not provide an explanation why the drive would suddenly fail to be recognized by the BIOS nor explain why this procedure should help. It's interesting though. Some sort of internal reset mechanism?
Despite the notes from Crucial, unfortunately this did not work for me. I made two attempts at their procedure and across two differing systems. No joy. So I spend more time playing with paperweights while the saga continues...
12-10-2011 11:17 AM
Crucial has replaced this drive under warranty.
Originally, they sent me a 128GB replacement for a 256GB drive. In addtion, the drive was clearly refurbished (their policy) with some hand written notes on the label.
After a follow-up conversation about the error (and the fact that the drive was only a couple of weeks old), the drive was replaced with an as-new 256GB.
They paid for the shipping. With a bit aof work, I'm satisfied with Crucial's response. New drive is working fine to date.
Thanks Crucial. Thanks to those helpful souls on this forum.
05-31-2012 04:02 PM - edited 05-31-2012 04:12 PM
/resurrecting thread, as it resurrected by SSD
I can definitely confirm the power-cycle procedure posted above.
A) SSD Crucial M4 256GB, bricked itself for no apparant reason while waking up from sleep mode
B)
Power off, 30 seconds.
Power on, absolutely no data for 20min (used a USB phone charger, see add. info below)
Power off, 30 seconds
Power on, absolutely no data for 20min
Power off, 30 seconds,
C)
Boot into OS. SSD works
Sounds much like Voodoo, but it worked. ![]()
Situation:
SSD Model: Crucial M4 256GB SSD, Firmware version 0001 (compounding factor no.1: never updated FW).
Computer: Lenovo Thinkpad T500 and then carried over in successor, Thinkpad W520. Each time a fresh install of Windows 7-64 with all Windows, device driver and Lenovo components updated, in default system- and power saving configuration.
Operational background: regular home environment, used for 6 months with absolutely no F4 BSOD or other symptoms. New components, new laptop, never overclocked, no tweaking, plain vanilla configuration, used for office, browsing, casual gaming, light loads. Laptop was regularly suspended in sleep mode, all power saving features were used in factory default configuration, deeper sleep etc. were enabled, system was never hibernated to save on write cycles
(compounding factor no.2: deep sleep modes, laptop resting in suspend mode for many and long times)
Failure description: regular Windows use (Office, Browsing), system suspend. System wake up after 14h in sleep mode, resume succeeds, but no read or write access to drive. Windows fails with BSOD F4 error, reboots, SSD is not recognized anymore, drive LED constanly on. Retries and connects through USB enclosure did not work, drive appeared completely bricked.
Recovery: boot-up from spare HDD with old, but still bootable installation, read thread, perform Voodoo as stated above. Reconnect in USB enclosure, no drive letter appeared. Reconnect as SATA main HDD, SSD boots up fine, no error messages, appears completely working as if never failed at all.
Next steps: update firmware. Download and burn up-to-date Linux live CD for emergencies. Most importantly: Update and regularly and religiously perform backups.
Additional Information: a phone charger or other power-only USB outlet will work fine for the power cycle. (Advantages: a) only charging circuit present, so no data flow interrupting the process, b) computer can be used, e.g. with a Live CD, while power cycle is performed, c) power cycle can be performed much much easier) - USB phone chargers will output 5V USB with no data, so there is probably no potential for damage, but please be sure to test your USB phone charger with a cheap USB stick before plugging in the USB enclosure, just to be on the safe side.
Thanks again for this procedure.