Question Second M.2 Drive not detected on cold boot. Restart fixes problem.

[GUnit_Gaming]

Problem started after I moved what was the main 1tb drive from slot one down to slot two. I added a new 4tb m.2 drive into slot one and partitioned it in half. The 1tb was left whole. Full wipe and reinstall of everything, Win10. I've found similar posts on other sources but the steps listed don't help. The second drive is more of just a bulk games drive but having to restart just to get it showing is kinda annoying. Any ideas would be great. Thank you.

M.2 Slot 1 (Gen 4): WD Black SN850X 4TB Gen4.
M.2 Slot 2 (Gen 3): WD Black SN850 1TB Gen4.
Sata 1,2: Seagate 1TB HDDs (x2)
Sata 3,4,5,6: Empty

Edit;
Asus ROG STRIX B550-F Gaming (Wifi).
AMD Ryzen 7 3700x.
G.Skill TridentZ RB Series 16GB DDR4 3600mhz.
EVGA GeForce GTX 1660 SC.
WD Black SN850X 4TB Gen4 (G4 Slot). WD Black SN850 1TB Gen4 (G3 Slot). Seagate 1TB HDD (x2).
Corsair RMx 650w 80+ Gold PSU.

 

[Lutfij]

Sig space spaces can and will change over time. When that happens this thread and their suggestions can be rendered moot to the end user in the same boat as you're in now. It's why we ask users to pass on their specs in the thread's body. I've shoehorned your specs into the thread's body.

Asus ROG STRIX B550-F Gaming (Wifi).
What BIOS version are you on for your motherboard?

You state doing a full wipe, were both drives connected when you were reinstalling Windows 10?

 

[GUnit_Gaming]

Sig space spaces can and will change over time. When that happens this thread and their suggestions can be rendered moot to the end user in the same boat as you're in now. It's why we ask users to pass on their specs in the thread's body. I've shoehorned your specs into the thread's body.

Asus ROG STRIX B550-F Gaming (Wifi).
What BIOS version are you on for your motherboard?

You state doing a full wipe, were both drives connected when you were reinstalling Windows 10?

Yes both drives were installed during the OS install. I thought maybe an outdated BIOS would be it so I updated it today to the newest (3607), along with the drivers. I did a cold start and the problem still happens.

 

[Moonstick2]

Did you find this thread? SN850 on a variety of boards

https://community.wd.com/t/wd-black...ios-on-bootup-from-power-off/259168/80?page=6

There are a few things in there you could try if you haven't already, otherwise it looks like you're best off returning the 4 TB as faulty and getting a different brand.

I had a 1 TB WD NVMe as my games drive for years without issue. Recently I got a 2 TB WD NVMe as the games drive and moved my OS/data to the 1 TB. Now, very occasionally, that 1 TB isn't found in BIOS so the PC won't boot, but it works fine when I try and boot it again. Go figure.

It doesn't happen enough to me to make me consider replacing the drive (yet), but in your case if it's happening a lot with a new drive it's not worth putting up with it.

 

[GUnit_Gaming]

Did you find this thread? SN850 on a variety of boards

https://community.wd.com/t/wd-black...ios-on-bootup-from-power-off/259168/80?page=6

There are a few things in there you could try if you haven't already, otherwise it looks like you're best off returning the 4 TB as faulty and getting a different brand.

I had a 1 TB WD NVMe as my games drive for years without issue. Recently I got a 2 TB WD NVMe as the games drive and moved my OS/data to the 1 TB. Now, very occasionally, that 1 TB isn't found in BIOS so the PC won't boot, but it works fine when I try and boot it again. Go figure.

It doesn't happen enough to me to make me consider replacing the drive (yet), but in your case if it's happening a lot with a new drive it's not worth putting up with it.

On a cold boot, both M.2s are detected in the BIOS. When I let windows boot, the 2nd M.2 drive (the 1TB) is not detected by windows. The new 4TB which is partitioned in half, works perfectly fine. Only when I restart windows will it then detect the 2nd M.2 drive. Sorry for not responding. Life happened.

 

[Moonstick2]

Right, so it's not the new drive that's a problem, but it's a 2nd M.2 drive issue. It always shows in BIOS, but not in Windows until you reboot. This is all consistent and repeatable, and you're on the latest BIOS.

Ugh.

I suspect some kind of Windows bug. Maybe something weird, like it boots so fast it somehow misses the second drive from cold. When you reboot from cold, have you looked in Disk Management to see if Windows sees the drive in any way at all?

I suspect your options might be (a) live with it, or (b) try a different brand of 1 TB M.2 (or a 1 TB SSD) to see if that works, and if it does sell the WD on.