Just a warning, folks, that it seems that the current firmware (01MG) shipped with new Crucial M4 mSATA drives (at least the 256Gb) is seriously buggy, causing frequent "2101 Detection Error" warnings for the drive on boot up, with subsequent failure to boot until a full (20minute - 1hour) power cycle is completed.
I bought one of these a week ago to do a clean install of Windows 8 with my W520. I formatted it as GPT, and everything went fine for a couple of days until about five reboots down the line I got a 2101 Detection Error on boot up. This had me very scared, as I'd moved over a lot of data from a different drive in order to make room on the second drive for regular image-based backups (ironically enough). Stupid I know. Fortunately I still had Windows 7 on the other drive, which I could boot in order to research the problem. Came up with a few mentions, and decided to try power off with battery out. Sure enough, after an hour off with no battery, the system booted up again from the mSATA drive. Phew. I immediately backed up all "crucial" (ha ha) data. Warning, folks, never, ever, trust in a new drive until it is well tested, and even then make sure you've not only backed up your data, but you have a second backup in case the first backup fails.
Right, a couple more days of fast, responsive operation and then one night on reboot, WHAM "2101 Detection Error on HDD2 (mSATA)". Great. It was bedtime anyway, so I leave the system off with the battery out all night, but in the morning the error persists and the system won't boot. As it happens, I had been fiddling with BIOS settings, so I wondered whether I’d mucked something up. I went into the BIOS, pressed F9 to load defaults, F10 to save and reboot. Pressed F12 during reboot so I could select the mSATA drive, and hey presto, up it boots. WTF?
Think no more about it till last nght, exactly the same problem. “Right, I know how to fix this,” I thought. Went straight into BIOS, reset it. Restarted. “2101 Detection Error”. So off, battery out, wait 10 minutes (I’m impatient), back into BIOS, reload defaults again, this time decide to spend some time in the BIOS putting it back to my usual settings. Spent about 10 minutes doing that. Restarted, and the drive boots again as if nothing had happened.
So this morning I went to the Crucial forums (why didn’t I look there before? – I’d been looking on Lenovo sites, thinking the problem was the Lenovo firmware), and I’ve found lots and lots of reports of the exact same issue on a number of different systems, not just Lenovo, mostly with the 2.5” M4, which has firmware 010G, and some specifically with the mSATA 01MG. The firmware is basically the same. It seems the previous firmware for the 2.5” M4 was fine, but when people upgraded to 010G (which offered performance improvements) they started getting this error, although Mac users had the error on earlier firmware too. Some people have returned their drives, and others have tried to downgrade with mixed success. Others are waiting for a promised fix from Crucial. My drive was *shipped* with 01MG already on it -- I haven't flashed it.
Crucial have a post where they recommend letting the machine idle in the BIOS setup for 20 mins, then repeating this twice over, for a full hour, to fix the issue temporarily!!!!!!!! I can’t believe they’re seriously recommending such a procedure for a serious product. Clearly it’s a workaround – apparently the drive does some sort of internal self check during this time, and needs to be powered on with no attempt at data access.
I haven’t yet decided whether to return mine as unfit for purpose (a real pain, due to all the time I’ve put into setting up Win8 the way I want it), or to wait for a firmware update. But I thought I should warn you guys of the issue.