running bootcamp and now created 3rd disk and Windows 7 wont boot
I have Bootcamp on Macbook Pro and have been running with two partitions with Mac on one and Windows on another.
Now I decided to create a third disk to keep my data on. All worked fine and I can store files etc on this new partition. I can also see the Windows 7 partition.
When I reboot the Mac I get a black screen and a message indicate that non-boot disk found. Rebooting and holding the ALT key down gives the ability to boot into Mac again.
I found the following articles that suggest that I need to edit the Boot.ini file and change the partition number to be able to boot into Windows.
However, I Windows 7 no longer has a Boot.ini.
http://davidseah.com/wikilab/Creating-2-Windows-Partitions-with-Boot-Camp/
Has anyone got experience on this?
How can I fix this replacement for boot.ini from MacOS?
This article suggested installing rEFIt (http://refit.sourceforge.net/) to fix the issue.
http://forums.macrumors.com/showthread.php?t=264754
Anyone have experience on using rEFIt on bootcamp with three partitions on the Mac?
Thanks
Now I decided to create a third disk to keep my data on. All worked fine and I can store files etc on this new partition. I can also see the Windows 7 partition.
When I reboot the Mac I get a black screen and a message indicate that non-boot disk found. Rebooting and holding the ALT key down gives the ability to boot into Mac again.
I found the following articles that suggest that I need to edit the Boot.ini file and change the partition number to be able to boot into Windows.
However, I Windows 7 no longer has a Boot.ini.
http://davidseah.com/wikilab/Creating-2-Windows-Partitions-with-Boot-Camp/
Has anyone got experience on this?
How can I fix this replacement for boot.ini from MacOS?
This article suggested installing rEFIt (http://refit.sourceforge.net/) to fix the issue.
http://forums.macrumors.com/showthread.php?t=264754
Anyone have experience on using rEFIt on bootcamp with three partitions on the Mac?
Thanks
ASKER
I installed rEFIt but on reboot it tried to boot WIndows (my default selection from Bootcamp) and gave me "No bootable device -- Insert boot disk and press any key".
I rebooted and held ALT key down which gave me the choice of Mac or the restore disk.
This suggests to me that rEFIt hasn't been installed correctly. I couldn't see anything on the web site for configuring, everything to me suggested it installs and works.
I'lll try and re-install, while I hope you can provide me with further guidance.
Thanks
I rebooted and held ALT key down which gave me the choice of Mac or the restore disk.
This suggests to me that rEFIt hasn't been installed correctly. I couldn't see anything on the web site for configuring, everything to me suggested it installs and works.
I'lll try and re-install, while I hope you can provide me with further guidance.
Thanks
ASKER
I did ran the Partition Inspector. Maybe this has some clues. Let me know if any further information is required.
*** Report for internal hard disk ***
Current GPT partition table:
# Start LBA End LBA Type
1 40 409639 EFI System (FAT)
2 409640 488008255 Mac OS X HFS+
3 488008256 489277799 Mac OS X Boot
4 489279488 585664511 Basic Data
5 585664512 976773119 Basic Data
Current MBR partition table:
# A Start LBA End LBA Type
1 1 409639 ee EFI Protective
2 409640 488008255 af Mac OS X HFS+
3 488008256 489277799 ab Mac OS X Boot
4 489279488 585664511 07 NTFS/HPFS
MBR contents:
Boot Code: Unknown, but bootable
Partition at LBA 40:
Boot Code: None (Non-system disk message)
File System: FAT32
Listed in GPT as partition 1, type EFI System (FAT)
Partition at LBA 409640:
Boot Code: None
File System: HFS Extended (HFS+)
Listed in GPT as partition 2, type Mac OS X HFS+
Listed in MBR as partition 2, type af Mac OS X HFS+
Partition at LBA 488008256:
Boot Code: None
File System: HFS Extended (HFS+)
Listed in GPT as partition 3, type Mac OS X Boot
Listed in MBR as partition 3, type ab Mac OS X Boot
Partition at LBA 489279488:
Boot Code: Windows NTLDR
File System: NTFS
Listed in GPT as partition 4, type Basic Data
Listed in MBR as partition 4, type 07 NTFS/HPFS
Partition at LBA 585664512:
Boot Code: Windows BOOTMGR (Vista)
File System: NTFS
Listed in GPT as partition 5, type Basic Data
*** Report for internal hard disk ***
Current GPT partition table:
# Start LBA End LBA Type
1 40 409639 EFI System (FAT)
2 409640 488008255 Mac OS X HFS+
3 488008256 489277799 Mac OS X Boot
4 489279488 585664511 Basic Data
5 585664512 976773119 Basic Data
Current MBR partition table:
# A Start LBA End LBA Type
1 1 409639 ee EFI Protective
2 409640 488008255 af Mac OS X HFS+
3 488008256 489277799 ab Mac OS X Boot
4 489279488 585664511 07 NTFS/HPFS
MBR contents:
Boot Code: Unknown, but bootable
Partition at LBA 40:
Boot Code: None (Non-system disk message)
File System: FAT32
Listed in GPT as partition 1, type EFI System (FAT)
Partition at LBA 409640:
Boot Code: None
File System: HFS Extended (HFS+)
Listed in GPT as partition 2, type Mac OS X HFS+
Listed in MBR as partition 2, type af Mac OS X HFS+
Partition at LBA 488008256:
Boot Code: None
File System: HFS Extended (HFS+)
Listed in GPT as partition 3, type Mac OS X Boot
Listed in MBR as partition 3, type ab Mac OS X Boot
Partition at LBA 489279488:
Boot Code: Windows NTLDR
File System: NTFS
Listed in GPT as partition 4, type Basic Data
Listed in MBR as partition 4, type 07 NTFS/HPFS
Partition at LBA 585664512:
Boot Code: Windows BOOTMGR (Vista)
File System: NTFS
Listed in GPT as partition 5, type Basic Data
ASKER
I re-installed rEFIt and did a reboot. Prior to the re-install I went to the bootcamp Startup Disk and choose Apple. Did the re-install and rEFIt re-installed successfully. But the reboot just booted into MacOS.
I tried to look in the application and utilities folders but cannot find rEFIt.
I tried to look in the application and utilities folders but cannot find rEFIt.
You should get an alternate boot menu. Refit is at /efi - the root of hard drive, access via Terminal.
Below from the docs:
Here are the steps for a manual install:
Download the “Mac disk image” or any of the other two binary distributions from the home page. Double-click to mount or unpack them.
Copy the “efi” folder from the rEFIt distribution to the root level of your Mac OS X volume.
Open Terminal and enter the following commands:
cd /efi/refit
./enable.sh
When prompted, enter the password for your user account.
If everything went well, you’ll see the rEFIt boot menu on the next restart.
Below from the docs:
Here are the steps for a manual install:
Download the “Mac disk image” or any of the other two binary distributions from the home page. Double-click to mount or unpack them.
Copy the “efi” folder from the rEFIt distribution to the root level of your Mac OS X volume.
Open Terminal and enter the following commands:
cd /efi/refit
./enable.sh
When prompted, enter the password for your user account.
If everything went well, you’ll see the rEFIt boot menu on the next restart.
ASKER
After posting the last update, I shut down the system and went away for an hour or so. On my return I started the system and was welcomed with the rEFIt menu.
I choose MacOs, it booted okay. Then tried each of the Windows icons. The first one gave a black screen with the cursor blinking in the top left corner. The second Windows icon gave a black screen with "No bootable device -- Insert boot disk and press any key".
I guess the Windows icon associated to the message "No bootable device" should be the Windows 7 bootable drive.
How do I resolve this to get rEFIt to boot?
Thanks
I choose MacOs, it booted okay. Then tried each of the Windows icons. The first one gave a black screen with the cursor blinking in the top left corner. The second Windows icon gave a black screen with "No bootable device -- Insert boot disk and press any key".
I guess the Windows icon associated to the message "No bootable device" should be the Windows 7 bootable drive.
How do I resolve this to get rEFIt to boot?
Thanks
ASKER
Hi roylong,
Just saw your comments. I didn't need to do your proposal as it did finally boot up with the rEFIt menu.
Any help on getting Windows 7 now to actually boot would be greatful.
Thanks
Just saw your comments. I didn't need to do your proposal as it did finally boot up with the rEFIt menu.
Any help on getting Windows 7 now to actually boot would be greatful.
Thanks
ASKER
I wanted to have the bootcamp partition available in a virtual machine. So, I decided to download vmWare Fusion to get the bootcamp into Fusion to allow me to continue using Windows while I sort out the issue of booting into Windows from bootcamp.
On starting up Fusion the option to create a virtual machine from Bootcamp tells me that no bootcamp partitions found.
This suggests that creating the third disk from the MacOS has destroyed some pointers or something.
Hope this gives more details on what the problem might be and how I can fix the booting of Windows 7 from bootcamp partition, either by rEFIt or the Apple tool of bootcamp.
On starting up Fusion the option to create a virtual machine from Bootcamp tells me that no bootcamp partitions found.
This suggests that creating the third disk from the MacOS has destroyed some pointers or something.
Hope this gives more details on what the problem might be and how I can fix the booting of Windows 7 from bootcamp partition, either by rEFIt or the Apple tool of bootcamp.
That does sound like something got screwed up when you created the data disk - how did you create the disk? Did you use the macintosh command line tools; if you did it from Windows then this may well have caused an issue.
I would recommend booting from a Windows repair disk - you can do this through rEFIt - and see what this can find on your system.
I would recommend booting from a Windows repair disk - you can do this through rEFIt - and see what this can find on your system.
ASKER
Tried the Windows repair disk and no joy,
Went to the command line and executed "bootrec /fixmbr", also other commands for bootrec, like /FixBoot, & /RebuildBcd
Also tried GPARTED to look at the HDD. A friend tried different commands to get to the boot block, without any success.
Noted that only 4 partitions appear when listed, when there should be 5. The fifth partition is the Windows 7 (bootable partition). The 4th partition that is listed in my earlier comments is the 50gig partition I created to store documents.
He mentioned that the MBR is compressed and if it wasn't it should then be visible.
The partition is showing as compressed in OSX in GPT table. But not showing up in the MBR table.
What I've been told, that if it is possible to mark the partition as uncompressed then it should be possible to create the MBR entry.
Doing a "diskutil info /dev/disk0s5" gives the following information
Device Identifier: disk0s5
Device Node: /dev/disk0s5
Part of Whole: disk0
Device / Media Name: BOOTCAMP
Volume Name: Windows7
Escaped with Unicode: Windows7
Mounted: Yes
Mount Point: /Volumes/Windows7
Escaped with Unicode: /Volumes/Windows7
File System Personality: UFSD_NTFS_COMPR
Type (Bundle): ufsd_NTFS
Name (User Visible): Windows NT Filesystem (compressed)
Partition Type: Microsoft Basic Data
OS Can Be Installed: No
Media Type: Generic
Protocol: SATA
SMART Status: Verified
Volume UUID: 0B9476C0-2076-4908-85F5-46
Total Size: 200.2 GB (200247607296 Bytes) (exactly 391108608 512-Byte-Blocks)
Volume Free Space: 113.7 GB (113670348800 Bytes) (exactly 222012400 512-Byte-Blocks)
Device Block Size: 512 Bytes
Read-Only Media: No
Read-Only Volume: No
Ejectable: No
Whole: No
Internal: Yes
Solid State: No
Let me know if there are any other commands I can run on the system that may give further information on how I can fix the MBR and to be able to boot from Windows 7.
Went to the command line and executed "bootrec /fixmbr", also other commands for bootrec, like /FixBoot, & /RebuildBcd
Also tried GPARTED to look at the HDD. A friend tried different commands to get to the boot block, without any success.
Noted that only 4 partitions appear when listed, when there should be 5. The fifth partition is the Windows 7 (bootable partition). The 4th partition that is listed in my earlier comments is the 50gig partition I created to store documents.
He mentioned that the MBR is compressed and if it wasn't it should then be visible.
The partition is showing as compressed in OSX in GPT table. But not showing up in the MBR table.
What I've been told, that if it is possible to mark the partition as uncompressed then it should be possible to create the MBR entry.
Doing a "diskutil info /dev/disk0s5" gives the following information
Device Identifier: disk0s5
Device Node: /dev/disk0s5
Part of Whole: disk0
Device / Media Name: BOOTCAMP
Volume Name: Windows7
Escaped with Unicode: Windows7
Mounted: Yes
Mount Point: /Volumes/Windows7
Escaped with Unicode: /Volumes/Windows7
File System Personality: UFSD_NTFS_COMPR
Type (Bundle): ufsd_NTFS
Name (User Visible): Windows NT Filesystem (compressed)
Partition Type: Microsoft Basic Data
OS Can Be Installed: No
Media Type: Generic
Protocol: SATA
SMART Status: Verified
Volume UUID: 0B9476C0-2076-4908-85F5-46
Total Size: 200.2 GB (200247607296 Bytes) (exactly 391108608 512-Byte-Blocks)
Volume Free Space: 113.7 GB (113670348800 Bytes) (exactly 222012400 512-Byte-Blocks)
Device Block Size: 512 Bytes
Read-Only Media: No
Read-Only Volume: No
Ejectable: No
Whole: No
Internal: Yes
Solid State: No
Let me know if there are any other commands I can run on the system that may give further information on how I can fix the MBR and to be able to boot from Windows 7.
ASKER
Oh, just re-read Roylong other questions.
I created the data partition using the graphical user interface of "Disk Utility.app" I've attached a pdf showing the partition screen for the HDD and highlighted the data partition I created using the app, by choosing partition layout to be 3 partitions.
partition.pdf
I created the data partition using the graphical user interface of "Disk Utility.app" I've attached a pdf showing the partition screen for the HDD and highlighted the data partition I created using the app, by choosing partition layout to be 3 partitions.
partition.pdf
ASKER
I still haven't been able to find a solution.
Basically, if no one can provide a recovery method then I only have the option of destroying my Bootcamp partition and recreating.
I'm still hoping for a solution before going for this option. I return home this Friday/Saturday, so will be looking to remove the partition and starting a new bootcamp this weekend.
Basically, if no one can provide a recovery method then I only have the option of destroying my Bootcamp partition and recreating.
I'm still hoping for a solution before going for this option. I return home this Friday/Saturday, so will be looking to remove the partition and starting a new bootcamp this weekend.
You killed it by using the disk utility, which no concept of windows partitions. Bootcamp sets it up correctly, disk utility destroys the windows info from the disk.
The way I did this for triple boot was to allocate my mac partition and 'other' partition using bootcamp and then hive off part of the 'windows' partition for Linux - or for data in your case.
Make sure your mac partition is as big/small as you want it to be during the bootcamp setup process.
The way I did this for triple boot was to allocate my mac partition and 'other' partition using bootcamp and then hive off part of the 'windows' partition for Linux - or for data in your case.
Make sure your mac partition is as big/small as you want it to be during the bootcamp setup process.
ASKER
Each time I ran Bootcamp Assistant it only gave two options either create the bootcamp partition or merge into one Mac partition.
If I understand from your comment you created the bootcamp partition using Bootcamp Assistant. Then once Windows was installed used Windows disk management utilitiy to hive off a portion of the bootcamp partition as your linux partition.
It is unfortunate that you didn't see my other message, as I had asked how best to create a third partition for my data. The advice then was that Disk Utility was okay to use.
I tried running Bootcamp Assistant and it now tells me that the the startup disk cannot be restored to a single partition or partitioned.
I guess I need to now remove the partitions with Disk Utility and start again?
If I understand from your comment you created the bootcamp partition using Bootcamp Assistant. Then once Windows was installed used Windows disk management utilitiy to hive off a portion of the bootcamp partition as your linux partition.
It is unfortunate that you didn't see my other message, as I had asked how best to create a third partition for my data. The advice then was that Disk Utility was okay to use.
I tried running Bootcamp Assistant and it now tells me that the the startup disk cannot be restored to a single partition or partitioned.
I guess I need to now remove the partitions with Disk Utility and start again?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the information.
Had a brief look and will look more closely and start the process.
Will post if I need any further clarifications.
Thanks
Had a brief look and will look more closely and start the process.
Will post if I need any further clarifications.
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi, My question seems to have fallen off the radar. Anyone have any thoughts on how I can merge the data partition back into OSX partition?
See above for details.
Thanks
See above for details.
Thanks
Missed this in all the other emails - I thought you had got the answer to the original question.
Is there anything on the data partition?
Have you tried using the command line tools diskutil?
Is there anything on the data partition?
Have you tried using the command line tools diskutil?
ASKER
Thanks for replying.
No, I hadn't placed any data as yet on the data partition. I hadn't thought or thought that the GUI version does everything the command line version does. I'll have a look at the command line and search around to see if it can help.
No, I hadn't placed any data as yet on the data partition. I hadn't thought or thought that the GUI version does everything the command line version does. I'll have a look at the command line and search around to see if it can help.
ASKER
Hi Roylong
I had a look at the command line application and cannot see a command to use to merge the partition.
I have had further thoughts on your comment that you felt the question had been answered. I guess you can see it two ways. Firstly, I'm not completely back to square one, that is there is still the outstanding 50gigs not available. However, my Windows system is back up and running. So, from that point the assistance provided did get me to get the Windows running again.
So, I'll close this question and open another with the other issue I have. I hope you will be able to come to my new question and assist.
I had a look at the command line application and cannot see a command to use to merge the partition.
I have had further thoughts on your comment that you felt the question had been answered. I guess you can see it two ways. Firstly, I'm not completely back to square one, that is there is still the outstanding 50gigs not available. However, my Windows system is back up and running. So, from that point the assistance provided did get me to get the Windows running again.
So, I'll close this question and open another with the other issue I have. I hope you will be able to come to my new question and assist.
ASKER
I marked the solution as A, as Roylong provided detailed help and assistance to my issue. However, it didn't directly resolve the issue. I would not have resolved the issue if had not been the different tips and suggestions made by Roylong.
For anyone coming to this question having the same issue as I did, I have marked my comment which actually did fix the problem of getting Bootcamp to recognise again the Windows partition.
For anyone coming to this question having the same issue as I did, I have marked my comment which actually did fix the problem of getting Bootcamp to recognise again the Windows partition.
That should sort out your issue for sure.