Installed M.2 SSD in laptop. Disk Mgmt shows it as HD1, not HD0

[Skyzoomer]

I bought an Acer Spin3, i7 laptop that came with a 1TB HDD and Win10. Bought a Crucial 275GB M.2 SSD and cloned the entire 1TB drive to it. Used Diskpart to clean the 1TB HDD so it is now entirely unallocated.

I can boot into Win10 on the SSD fine. Problem is that Disk Management shows:
.... Disk 0: 931.51 GB Unallocated
.... Disk 1: 256.16 GB in 4 partitions, one of which is the Acer (C: ) 255.03 GB NTFS, Healthy (Boot, Page File, Crash Dump, Primary)

How can I assign the SSD to Disk 0 so it displays on top as normal?

----------
THE PERTINENT BIOS SETTINGS ARE:

BIOS Information screen shows:
… HDD0 Model Name: Crucial_C1275MX300SSD4
… HDD1 Model Name: ST1000LM035-1RK172
… SATA Mode: AHCI

Boot screen shows:
Boot Mode: UEFI
Secure Boot: Enabled
Boot priority order:
… 1. Windows boot manager
… 2. HDD0: Crucial_C1275MX300SSD4
… 3. HDD1: ST1000LM035-1RK172
… 4. USB FDD:
… 5. etc.

There is no other boot option on the Boot screen or anywhere else.

BIOS Main screen shows:
... Network Boot: Disabled
... F12 Boot Menu: Enabled
----------

As the "BIOS settings show, the SSD is assigned to HDD0". So I can't figure out why Win10 (or the Windows Boot Manager) is assigning the unallocated 1TB drive as Drive-0 and the SSD as Drive-1.

 

[VirtualLarry]

This is not a technical problem, this is "computer OCD".

Seriously, don't worry about it.

Edit: Just a note, the order that drives are shown, in Disk Management, may or may not have anything to do with their physical connections or positions.

 

[OlyAR15]

In order to get Disk 0 to be the SSD, you would simply do a fresh install of Win 10 after reformatting the SSD. Keep the other drive unallocated.

Or, you can just ignore a completely irrelevant issue, like VL said, and worry about more important things in life.

 

[Skyzoomer]

This is not a technical problem, this is "computer OCD".
Seriously, don't worry about it.
Edit: Just a note, the order that drives are shown, in Disk Management, may or may not have anything to do with their physical connections or positions.

After much Googling, I came to that conclusion, ie: Don't worry about it.
Thanks.

 

[Skyzoomer]

In order to get Disk 0 to be the SSD, you would simply do a fresh install of Win 10 after reformatting the SSD. Keep the other drive unallocated.

I was wondering if doing a fresh install of Win10 would get it to be Disk-0 in Disk Management. But it is baffling why the BIOS sees the SSD as HDD-0 but Disk Management sees the unallocated 1TB HDD as Drive-0. Thanks.

Or, you can just ignore a completely irrelevant issue, like VL said, and worry about more important things in life.

 

[corkyg]

Disk Management simply saw the HDD first. When you installed the SSD, the HDD must have been there, and it has "date of rank," IOW words, it is senior to the SSD. That's very normal.

 

[JeffMD]

Hd0 and hd1 are their technical location in the sata controller and cannot be changed.

 

[Valantar]

If everything is working as it should, why are you even worrying about this? BIOS and OSes may or may not label things differently. Leave well enough alone. This is all fine.

 

[Skyzoomer]

Disk Management simply saw the HDD first. When you installed the SSD, the HDD must have been there, and it has "date of rank," IOW words, it is senior to the SSD. That's very normal.

So the "rank" is saved in Windows and "cloning" the 1TB HDD to the SSD preserved that rank. That would explain my results. That also means that "cloning" will always do that. Thanks.

 

[Skyzoomer]

Hd0 and hd1 are their technical location in the sata controller and cannot be changed.

My BIOS shows the SSD as HD0 but Win10's Disk Managment shows the unallocated HDD as Drive0. That appears to have "changed" it, which is what I didn't understand when composing my original post. Thanks.

 

[Skyzoomer]

If everything is working as it should, why are you even worrying about this? BIOS and OSes may or may not label things differently. Leave well enough alone. This is all fine.

Inquiring minds want to know .

 

[Valantar]

Inquiring minds want to know .

The tone of this thread isn't enquiring, it's assuming something is a problem when it isn't showing any sign of being a problem in any way, shape or form. A couple of key quotes that pretty much sums it up IMO:

I can boot into Win10 on the SSD fine. Problem is that Disk Management shows:
.... Disk 0: 931.51 GB Unallocated
.... Disk 1: 256.16 GB in 4 partitions (...)

This is not a technical problem, this is "computer OCD".

Seriously, don't worry about it.

 

[Skyzoomer]

The tone of this thread isn't enquiring, it's assuming something is a problem when it isn't showing any sign of being a problem in any way, shape or form. A couple of key quotes that pretty much sums it up IMO:

Knit picking!

 

[Valantar]

Knit picking!

Nitpicking. But so is correcting other people's spelling, I suppose. Oh well. Enough OT for now.

 

[corkyg]

So the "rank" is saved in Windows and "cloning" the 1TB HDD to the SSD preserved that rank. That would explain my results. That also means that "cloning" will always do that. Thanks.

No, if on completion of cloning, you remove the HDD before reboot, the new SSD should then be recorded as Drive 0.

As regards, spelling . . . The idiomatic expression in English is nit picking. Nits are the tiny egg sacs of lice.

https://www.google.com/search?sourc...0l2j0i10l3.0.0.0.5313...........0.t9voJjh99bU

 

[Chiropteran]

The idiomatic expression in English is nit picking. Nits are the tiny egg sacs of lice.

I did not expect to learn that from this thread.

 

[Skyzoomer]

Disk Management simply saw the HDD first. When you installed the SSD, the HDD must have been there, and it has "date of rank," IOW words, it is senior to the SSD. That's very normal.

So the "rank" is saved in Windows and "cloning" the 1TB HDD to the SSD preserved that rank. That would explain my results. That also means that "cloning" will always do that. Thanks.

No, if on completion of cloning, you remove the HDD before reboot, the new SSD should then be recorded as Drive 0.

True since I removed the HDD on completion of cloning (since the HDD still had the bootable Win10 system on it), booted from the SSD and disk management showed the SSD as Disk-0. But when I reinstalled the HDD (but booted from the SSD), disk management showed the HDD as Disk-0 and the SSD as Disk-1.

 

[corkyg]

That's because you still had a copy of the OS on the HDD. Had you reformatted the HDD, it would have been different. This is just normal Windows protocol and nothing to worry about.

 

[Skyzoomer]

That's because you still had a copy of the OS on the HDD. Had you reformatted the HDD, it would have been different. This is just normal Windows protocol and nothing to worry about.

That's what I initially thought so that's why I had cleaned the HDD using Diskpart so it was completely unallocated, as stated in my original post. Then I booted from the M.2 SSD but the HDD still was/is Disk-0 in Disk Management. Since the BIOS lists the SSD as HD-0, couldn't understand why the HDD is Disk-0 in Disk Management. Just explaining the sequence of events so no need to go over the same things again.

Thanks much for helping out,
Skyzoomer