So after I built my self a nice gaming computer, I finally decided to plug in my Android phone to access the SD card as mass storage. Took me a minute to figure out because I had to dig through the settings so it would act like that, instead of the default being ran through a content manager but when I finally did so, chaos broke through.
My E drive, a separate HDD I use purely for installing programs had disappeared on me. At first I had no Idea what went wrong so I thought I'd give it a reboot. Then the boot manager went missing! I had to fiddle with the bios to eventually get the right order, which oddly, had to be the programs only HDD, not the SSD which holds the operating system.
After all that the drive was still missing so I went to the disk manager and found it was still there untouched. I spent a couple of minutes trying to solve why it couldn't be found, then I noticed the drive had not been assigned a letter!
How does something like that happen? Is it possible that on my phone the SD card was also E drive and the computer instead of naming it H drive it kicked my HHD off E? I am afraid now if I plug my phone back in I will have this problem again(using as a mass storage device).
Has anyone else seen this issue before?
My E drive, a separate HDD I use purely for installing programs had disappeared on me. At first I had no Idea what went wrong so I thought I'd give it a reboot. Then the boot manager went missing! I had to fiddle with the bios to eventually get the right order, which oddly, had to be the programs only HDD, not the SSD which holds the operating system.
After all that the drive was still missing so I went to the disk manager and found it was still there untouched. I spent a couple of minutes trying to solve why it couldn't be found, then I noticed the drive had not been assigned a letter!
How does something like that happen? Is it possible that on my phone the SD card was also E drive and the computer instead of naming it H drive it kicked my HHD off E? I am afraid now if I plug my phone back in I will have this problem again(using as a mass storage device).
Has anyone else seen this issue before?