I have a Late 2011 13" MacBook Pro running High Sierra 10.13.6,
Quick recap, I initially wanted to install Windows through Bootcamp but it for some reason failed once the laptop restarted to boot the Windows installer disc, the disc ejected and it only said "no bootable device, insert boot disk and press any key". Could be an issue with the installer CD disc as its not an OEM disc,
Because it failed, I did not bother going forward with installing Windows so I rebooted into macOS to revert it. I went into Disk Utility and saw the already partitioned "BOOTCAMP" volume from the failed installation and proceeded to remove that partition because it had nothing in it. However now I see that my Macintosh HD volume had not changed in size, it still shows 250GB (I had split equally 250GB each for macOS and Windows).
To add to the confusion, if I look into the "Storage" section in "About This Mac", it will show that "Macintosh HD" has the full 500GB capacity, but not in Disk Utility.
If anyone has any idea on fixing this please do chime in. I'd rather not do a clean macOS reinstall, but if I have to, then I will.
Cheers,
Quick recap, I initially wanted to install Windows through Bootcamp but it for some reason failed once the laptop restarted to boot the Windows installer disc, the disc ejected and it only said "no bootable device, insert boot disk and press any key". Could be an issue with the installer CD disc as its not an OEM disc,
Because it failed, I did not bother going forward with installing Windows so I rebooted into macOS to revert it. I went into Disk Utility and saw the already partitioned "BOOTCAMP" volume from the failed installation and proceeded to remove that partition because it had nothing in it. However now I see that my Macintosh HD volume had not changed in size, it still shows 250GB (I had split equally 250GB each for macOS and Windows).
To add to the confusion, if I look into the "Storage" section in "About This Mac", it will show that "Macintosh HD" has the full 500GB capacity, but not in Disk Utility.
If anyone has any idea on fixing this please do chime in. I'd rather not do a clean macOS reinstall, but if I have to, then I will.
Cheers,