Crucial MX200 not recognised in UEFI boot

Toggle sidebar Toggle sidebar
4

4ellboy

Commendable
Jan 10, 2017
8
0
1,520
Hello. I have a frustrating problem: Windows 10 does not recognise my SATA HDD when I boot in UEFI mode, although it works OK in Legacy mode.

I have a new DELL Inspiron 15 7560 which shipped with an mSATA 256GB HDD and a caddy for a 2.5" drive. [After 3 weeks trying to find the correct part, I finally bought an interpose cable (the second drive connects using a small HDD connector on the motherboard, not direct in the SATA.]

I put in my 12 month old Crucial MX200 1TB SSD drive, intending to use it as a data area for photos, retaining the mSATA for boot/OS and software. The Crucial drive has a Win10 OS/boot partition at present, which I am intending to overwrite.
SO: when I boot the machine with its standard UEFI settings, it simply doesn't see the Crucial drive. It is visible in BIOS diagnostics but nowhere else once Windows starts. I have the latest WIN10 updates, the latest firmware for the Crucial drive (M04) and the latest device drivers.
Curiously, when I change the BIOS to boot in legacy (not UEFI mode), then it 1) fails to boot from the mSATA drive, 2) it then boots successfully from the Crucial drive and 3) it shows both the Crucial drive (as c:\ and a separate partition g:\) and the mSATA drive (as d:\). BUT it isn't quite what I want: I want to use the mSATA as the boot drive, leaving the whole 1TB second drive for data. Also the version of Windows which is presently on the Crucial drive has the wrong licence key (from another laptop which I've sold) and is therefore unauthorised.
Is there a way of getting the Crucial drive to be recognised as a second disk when I boot in UEFI mode? Sorry for the shaggy dog story but I know how important it is to put the details in. Thanks in anticipation!
 
Solution
4
Success, and thanks to all for your helpful comments.  I now have a working laptop: booting (in UEFI mode) from the 256GB mSATA with my 1TB MX200 as a second drive, with a single partition containing my photo archives.
I fixed the problem by borrowing back the old DELL in which I previously used the MX200.  It recognised the MX200 as an external drive, and I was able to completely reformat it into NTFS mode.  There was one oddity: in the process I concluded that the SATA caddy that I had been using was not functioning correctly; when I tried his SATA caddy it worked fine.  Thus, I was dealing with two problems: a drive that was not recognised by my new laptop and also a faulty SATA caddy.  Once again thanks for all of your patience and...
Sort by date Sort by votes
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
Well, as a workaround since you apparently plan to utilize the Crucial as a secondary drive in your system and have no intention of utilizing the OS installed on that drive, couldn't you install the drive as a USB external device and delete the OS on that drive after booting to the system via your mSATA drive? Or even format the Crucial drive assuming there's no data currently on that drive that you want?
 
Upvote 0 Downvote
4

4ellboy

Commendable
Jan 10, 2017
8
0
1,520


 
Upvote 0 Downvote
4

4ellboy

Commendable
Jan 10, 2017
8
0
1,520


Hello; thanks for taking an interest. I replied earlier but somehow it lost my text. In answer to your suggestion; it won't recognise the drive either connected internally or externally (by USB) if I boot in UEFI mode. If I boot in legacy mode then it won't boot from the mSATA, and uses the first partition on the MX200 as the boot drive. I don't think I can format the boot drive in Windows. I've had a suggestion that I should disable the mSATA and then do a clean install on the MX200 (build using UEFI); then re-enable and boot to the mSATA and then format the MX200. I still have questions but that sounds like a plan.
 
Upvote 0 Downvote
4

4ellboy

Commendable
Jan 10, 2017
8
0
1,520


Thanks for your interest. The laptop was usable with the small mSATA drive, but I need to install the larger drive to fit my photo archive. I hunted for 3 weeks to find an interpose cable to allow me to physically connect the MX200 drive. I had already discovered that it would not connect via external USB either.

I believe that the problem is due to the MX200 being built in legacy (MBR?) mode, which the laptop cannot access when booted in UEFI.

 
Upvote 0 Downvote
4

4ellboy

Commendable
Jan 10, 2017
8
0
1,520
Success, and thanks to all for your helpful comments.  I now have a working laptop: booting (in UEFI mode) from the 256GB mSATA with my 1TB MX200 as a second drive, with a single partition containing my photo archives.
I fixed the problem by borrowing back the old DELL in which I previously used the MX200.  It recognised the MX200 as an external drive, and I was able to completely reformat it into NTFS mode.  There was one oddity: in the process I concluded that the SATA caddy that I had been using was not functioning correctly; when I tried his SATA caddy it worked fine.  Thus, I was dealing with two problems: a drive that was not recognised by my new laptop and also a faulty SATA caddy.  Once again thanks for all of your patience and support.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom