So, I have a strange issue. I installed a 128GB SSD into my PC, along with a 3TB HDD. I installed Windows onto the SSD (drive C), and I use the HDD for most everything else. I noticed that the HDD had a decent chunk of unallocated space, but thought nothing of it at the time.
The other day, however, I wanted to install Ubuntu for dual-boot for something to play around with, and because my grandfather has put it on his PC (for the sake of less virus issues, etc) and I want to be able to help him out as he usually comes to me with PC issues.
Well, the reason the HDD was missing a large portion of space was because I had, unknowingly, set it as MBR instead of GUID (not something that occurred to me at the time) so I located a utility to convert the disk over to GUID without data loss. The issue was that, while Windows installed onto my SSD just fine, the boot record was put on the HDD as the motherboard does not appear to recognize the SSD as a viable boot device (it does not show up in a list of hard drives in the BIOS or as a boot device).
On a side note, Ubuntu steadfastly refused to do anything with the unallocated space, giving me an error stating that the range was too high.
While I would *like* to not have to blow everything away and reinstall my OS, I'm not completely against the idea. That seems moot, however, as my motherboard does not seem to like the idea of my SSD being the boot device. So I basically have a strange scenario where the BIOS does NOT see the hard drive (my SSD), but Windows does. As you can guess, most searches only bring up the reverse of my situation.
Hardware:
MOBO: ASUS Sabertooth X58
SSD: SanDisk SDSSDP-128G-G25
HDD: Seagate ST3000DM001
PROC: Intel i7-960
OS:
Windows 7 Ultimate SP1 (Could be Pro - not at my place to check)
The other day, however, I wanted to install Ubuntu for dual-boot for something to play around with, and because my grandfather has put it on his PC (for the sake of less virus issues, etc) and I want to be able to help him out as he usually comes to me with PC issues.
Well, the reason the HDD was missing a large portion of space was because I had, unknowingly, set it as MBR instead of GUID (not something that occurred to me at the time) so I located a utility to convert the disk over to GUID without data loss. The issue was that, while Windows installed onto my SSD just fine, the boot record was put on the HDD as the motherboard does not appear to recognize the SSD as a viable boot device (it does not show up in a list of hard drives in the BIOS or as a boot device).
On a side note, Ubuntu steadfastly refused to do anything with the unallocated space, giving me an error stating that the range was too high.
While I would *like* to not have to blow everything away and reinstall my OS, I'm not completely against the idea. That seems moot, however, as my motherboard does not seem to like the idea of my SSD being the boot device. So I basically have a strange scenario where the BIOS does NOT see the hard drive (my SSD), but Windows does. As you can guess, most searches only bring up the reverse of my situation.
Hardware:
MOBO: ASUS Sabertooth X58
SSD: SanDisk SDSSDP-128G-G25
HDD: Seagate ST3000DM001
PROC: Intel i7-960
OS:
Windows 7 Ultimate SP1 (Could be Pro - not at my place to check)
Facebook
Twitter
Instagram