PC will boot, but can't get into BIOS

Ur_Boiii_Yahmez

Commendable
Jan 10, 2017
9
0
1,510
Hey guys, recently I've been having some issues regarding my Boot priority since data migration to my SSD didn't entirely work like it was supposed to. So, I tried to do a fresh install of windows 10, however it won't let me because my SSD has an MBR partition table. And windows can only be installed to GPT disks. However, when I try to get into Bios to configure my settings, I get a black screen. Do I need to bite the bullet and just format my SSD?
 
Solution
It's probably your responses to 4. & 5. above that are causing the problems you've experienced.

Consider giving the disk-cloning (data-migration) operation another go with the SDM program. But this time IMMEDIATELY following the d-c operation after shutting down the PC, disconnect or uninstall the HDD "source" drive from the system and boot ONLY with the cloned SSD connected. Assuming the SSD boots & functions without problems, work with it a few days before re:connecting the HDD as a secondary drive in the system. Then do what you want with the HDD.

Ur_Boiii_Yahmez

Commendable
Jan 10, 2017
9
0
1,510


I don't remember if I could or not, however wouldn't that be irrelevant because I need to configure my SSD and I can't do that since I can't add it in after bios
 
Just a few preliminary questions at the outset...

1. The PC you're using to communicate on this "forum". Is this the PC in question?

2. Assuming it is, presumably the boot drive is your original boot drive - probably a HDD?

3. And if that is so, can we assume it boots without problems and functions just fine?

4. And if so, it contains the Win 10 OS?

5. What's the make/model of the SSD you're working with?

6. You mentioned "data migration to my SSD didn't entirely work like it was supposed to". What's that mean? The cloning operation failed in that the SSD (which I assume was the recipient drive) didn't boot or function properly? What disk-cloning program did you use?
 

Ur_Boiii_Yahmez

Commendable
Jan 10, 2017
9
0
1,510


1. I posted this on my phone
2. Yes
3. Yes except my desktop is blank minus the recycle bin and Data migration program(previously had non- default wallpaper, programs etc)
4. Yes
5. Samsung Evo 850 250gb
6. It means it originally copied my OS onto my SSD, making it the boot drive, and now my OS is no longer on my SSD, for when I try to boot from it, I get the "Inaccessible boot device" error
 
1. Re your response to 3. above...You are referring here to the HDD which is now your current boot drive since the SSD is NOT a bootable drive at this point, right?

2. So are you indicating that following the apparent failed data-migration operation, your source drive, i.e., the HDD was somehow changed as a result of the failed disk-cloning attempt?

3. I assume you used the Samsung Data Migration program for the disk-cloning operation, right? If not, which program?

4. After the disk-cloning operation did you disconnect or uninstall the source HDD from the system and boot ONLY with the SSD connected?

5. When you now boot to the HDD with the SSD connected as a secondary drive and you access Disk Management...is the System Reserved partition (about a 500 MB partition) only on the HDD and NOT on the SSD? Or does the SSD also contain the SR partition?
 

Ur_Boiii_Yahmez

Commendable
Jan 10, 2017
9
0
1,510



1.) Yes when I'm not trying to do my fresh install of Windows 10 on my SSD
2.) Perhaps, the only thing that seems to be changed though is the location of the operating system.
3.) Yup, that's the one
4.) No I don't think so, I should have checked though I will do that next time, thanks.
5.) The SR partition is only on the HDD and not on the SSD
 
It's probably your responses to 4. & 5. above that are causing the problems you've experienced.

Consider giving the disk-cloning (data-migration) operation another go with the SDM program. But this time IMMEDIATELY following the d-c operation after shutting down the PC, disconnect or uninstall the HDD "source" drive from the system and boot ONLY with the cloned SSD connected. Assuming the SSD boots & functions without problems, work with it a few days before re:connecting the HDD as a secondary drive in the system. Then do what you want with the HDD.
 
Solution