Second Disk doesn't automount at boot

[nickgw]

Hey Guys, I'm wondering if anybody has run across the issue I'm having in W10.

 

I've got the W10TP installed on an SSD (C: drive) and a second HD that stores my data/some of my userfolders. Whenever I reboot my system, the HD that is normally D: does not ???automount, and I have to log in, immediately open Disk Management and assign a drive letter to the HD, afterwhich everything works as expected. I've attached a picture of Disk Management, pre-drive letter assigning.

 

I'm hoping someone has run into this and found a fix, or that I'm doing something wrong and it's glaringly obvious in the Disk Management screenshot.

 

Thanks!

[Som]

have you tried a different letter?

[nickgw]

Yes, and the CD-Rom is explicitly set to E:, so there is never a conflict for the D: letter assignment.

[Jackaluichi]

Hey Guys, I'm wondering if anybody has run across the issue I'm having in W10.

I've got the W10TP installed on an SSD (C: drive) and a second HD that stores my data/some of my userfolders. Whenever I reboot my system, the HD that is normally D: does not ???automount, and I have to log in, immediately open Disk Management and assign a drive letter to the HD, afterwhich everything works as expected. I've attached a picture of Disk Management, pre-drive letter assigning.

I'm hoping someone has run into this and found a fix, or that I'm doing something wrong and it's glaringly obvious in the Disk Management screenshot.

Thanks!

I have a similar scenario myself and I haven't had this problem. I went through a clean installation. Did you upgrade from a previous Windows version?

[nickgw]

I have a similar scenario myself and I haven't had this problem. I went through a clean installation. Did you upgrade from a previous Windows version?

 

Nope, same issue on the W10 build pre-TP and the TP. Both were clean installs.

[Jackaluichi]

Nope, same issue on the W10 build pre-TP and the TP. Both were clean installs.

Then I suggest letting MS guys know on their official forums http://answers.microsoft.com/en-us/insider/forum/insider_wintp?tab=Threads

 

Regards.

[Eric Veteran]

Try this from an elevated command prompt:

mountvol /n
mountvol /e

 

I'm assuming the drive actually is a removable drive?

[hagjohn]

I have the same issue with all 10 builds so far. I had to turn off fast boot in the bios.

[nickgw]

Try this from an elevated command prompt:

mountvol /n
mountvol /e

I'm assuming the drive actually is a removable drive?

 

I'll try this, but the drive is actually a RAID0 stripe.

 

Is the partition marked as active?

in an elevated command prompt

diskpart

select disk 0

list volume

select volume (volume number as appears from above command)

active

assign

exit

exit

 

Tried marking the drive as active, but it would no longer boot. Bootloader partition needs to be marked as active, which is also on the RAID0 Stripe.

 

Also strange how the system partition is on a different disk. I suspect the HDD is on the intel chipset SATA port while the SSD on a 3rd party controller

I would make sure the SSD becomes Disk 0 by moving SATA ports and then reinstalling everything.

I considered this. All three drives (RAID0Stripe and SSD) are on the Intel RAID SATA ports.

 

 

I have the same issue with all 10 builds so far. I had to turn off fast boot in the bios.

I'll try this. Glad to hear I'm not alone.

 

 

Thanks for all the tips. I'm going to try them and if none work, submit to MSFT.