06-26-2017 04:34 AM
I had the same issue. I went back to BIOS 1.29. It recognizes both drives again.
For that I had to disable "Secure RollBack Prevention". I did the update with the ISO (USB or CD).
Hope it works for you too.
06-26-2017 05:44 AM - edited 06-26-2017 05:57 AM
Its great to know. Here is the link:
06-29-2017 08:49 PM
The 1.30 update also killed my Adata drive, and was also forced to step back to 1.29. However I've heard from at least one person with a MyDigitalSSD device that theirs is working.
So it seems to be either specific brands, or possibly specific models within brands. Which means it's probably some sort of untested, unverified, and almost certainly unnecessary whitelist / blacklist.
I've opened a support ticket here in the U.K., which the rep said was being escalated. Of course the last time they said it was being escalated when I called back a week later it hadn't been. And then several days later that second escalation hadn't been escalated, and I eventually had to publicly post on Twitter and YouTube to get a meaningful response.
So, if I don't have any response today, I'll make another video showing the problem and tweet them again.
07-04-2017 02:18 AM
in order to duplicate the symptom and find the solution by development team, Lenovo would like to gather M.2 SSD 2242 model(or brand) name that you are experiencing the symptom on Transcend, ADATA or Teamgroup.
Thank you for your help.
07-04-2017 02:22 AM
=== START OF INFORMATION SECTION ===
Device Model: TEAM M4P SSD 256GB
Serial Number: E201702160020021
Firmware Version: O0724B
User Capacity: 256.060.514.304 bytes [256 GB]
Sector Size: 512 bytes logical/physical
Works fine with 1.29 and not at all with 1.3.