Bootcamp "no bootable disk" after new partition made
Hi All
I'm not a tech head and I've seen a bunch of confusing things on this issue but here goes nothing to get an answer
I am running OSX Mavericks on a Imac 2011. I've run Bootcamp Windows 7 for ages. But I decided to make a share drive so i siphoned off some data and made another FAT partition in Disk Utility and I think I have stuffed the MBR. Now I get the 'No Bootable Disk' when I try to get into Bootcamp
I tried repairing it with Refit - didn't work
Tried repairing the main drive - didn't work
Trired this solution but didn't have permission in Terminal to change the fdisk - not that I fully understood what that was doing so I was kind of glad
Tried to follow this but got nowhere as it was over my head and using Windows tools
Please help
This is my Partition Inspector record - I do I an external drive plugging in but I've tried booting without that too - no dice:
*** Report for internal hard disk ***
Current GPT partition table:
# Start LBA End LBA Type
1 40 409639 EFI System (FAT)
2 409640 1346786831 Mac OS X HFS+
3 1346786832 1348056367 Mac OS X Boot
4 1348057088 1543368703 Basic Data
5 1543370752 1953523711 Basic Data
Current MBR partition table:
# A Start LBA End LBA Type
1 1 409639 ee EFI Protective
2 409640 1346786831 af Mac OS X HFS+
3 1346786832 1348056367 ab Mac OS X Boot
4 * 1348057088 1543368703 0c FAT32 (LBA)
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 1346786832:
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 1348057088:
Boot Code: None (Non-system disk message)
File System: FAT32
Listed in GPT as partition 4, type Basic Data
Listed in MBR as partition 4, type 0c FAT32 (LBA), active
Partition at LBA 1543370752:
Boot Code: Windows BOOTMGR (Vista)
File System: NTFS
Listed in GPT as partition 5, type Basic Data
Clean both the OSX and Bootcamp - that sounds very painful.
The bootcamp excercise will be painful enough.
I followed the command line prompts from Christopher Murphy and I'm posting the info here:
sudo gpt -r -vv show disk0
gpt show: disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
gpt show: disk0: Suspicious MBR at sector 0
gpt show: disk0: Pri GPT at sector 1
gpt show: disk0: Sec GPT at sector 1953525167
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 1346377192 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
1346786832 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
1348056368 720
1348057088 195311616 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
1543368704 2048
1543370752 410152960 5 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
1953523712 1423
1953525135 32 Sec GPT table
1953525167 1 Sec GPT header
sudo fdisk /dev/disk0
Disk: /dev/disk0
geometry: 121601/255/63 [1953525168 sectors]
Signature: 0xAA55
Starting
Ending
#: id cyl hd sec - cyl hd sec [
start -
size]
1: EE 1023 254 63 - 1023 254 63 [
1 -
409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [
409640 - 1346377192] HFS+
3: AB 1023 254 63 - 1023 254 63 [1346786832 -
1269536] Darwin Boot
*4: 0C 1023 254 63 - 1023 254 63 [1348057088 - 195311616] Win95 FAT32L
Hoping this somehow lets me repair the damage with some walk through code steps by someone out there - that would be awesome!!!
Similar Messages
-
No bootable disk after installing Windows
I tried to install Windows 7 with Boot Camp on my Intel Single Core Mac Mini, and after having an error message I couldn't boot anymore. All I was getting was a black screen with the cursor flashing. I took the opportunity to upgrade to a bigger hard drive. I got the older hard drive out, deleted the windows partition, and cloned the original mac partition onto the new hard drive. All I get now is instead a "no bootable disk - insert bootable disk and press any key" error message. I have tried to boot from the original Install DVD, but no key combination works on start up. I tried C, Option key, Command-Option-Shift-Del, but it still goes to the black screen. The mouse is still working, as I can get the DVD out if I click the left button on start up but no keyboard seems to work (I tried to original Apple ones). I have got the new hard drive out, put it in an enclosure, formatted it with my laptop, and tried to install OSX from the disk but still can't boot from disk and still get error message. Any help?
While we all have MacBooks in this forum not all of us use BootCamp. There's a BootCamp Support Community where everybody uses BootCamp. You should also post this question there to increase your chances of getting an answer.
https://discussions.apple.com/community/windows_software/boot_camp -
Bootcamp-No Bootable Disk Error
I have a Windows 7 on my Bootcamp. It worked flawlessly until when I tried to import my Bootcamp to Parallel. On the Parallel, it said No Bootable Disk so I quited Parallels Desktop and tried booting my Windows 7 on my Bootcamp. And it is giving the same error.
Thanks Bob! My problem was that I was following advice from elsewhere on the internet that said I should burn a DVD in UDF format when in fact just burning it using disk utility in ISO made it work. Thank you so much!
-
Boot Camp "No Bootable Device" after OSX Partition Resize
I have a MacBook Mid/Late 2007. I started out with a 500GB drive that I partitioned 100GB for Windows 8 in Boot Camp (yes, I know only 7 is officially supported, not the point as it worked fine.) I wanted to try Mavericks so I resized my OSX partition down 100GB to make a new 100GB Mavericks partition. After I installed it and played around, I noticed when I booted with the option key, my Boot Camp partition was missing. I thought i was becaus eI had too many partitions, so I deleted Mavericks and resized my main OSX back to where it was when I started. The Boot Camp partition still won't show up when I hold option on boot, but when I run Boot Camp manager on OSX it wants to remove it, so it knows it's there. It also shows up in the startup disks pane, but if I select it and reboot, I get a "No Bootable Device -- insert boot disk and press any key" message. If there a way to bring back Windows?
Here's the kicker: My optical drive DOES NOT work. I installed Windows 7 off DVD long ago before it quit working and the only way I got Windows 8 on was through a downloaded upgrade. I know I should get it fixed, but I don't have the money (and I never use it, and this is 2 that have died on me in this laptop.) My system can't boot anything other than OSX off flash drives or external DVD drives (I tried, and I tried reEFIt, neither worked.) So I need a solution that doens't require a boot CD if at all possible.Nhammake wrote:
I can get to and boot OSX (it's what I'm using now as this is my only laptop), I just can't boot Windows. All my files show up fine on both partitions.
You can't add/remove or alter the partitions if Boot Camp is installed, Windows will cease to boot.
To fix it, erase all paritions except OSX. Start over, 2 partitions only (OSX and Boot Camp) -
Bootcamp no longer works after adding partition via Windows 7
I needed a D: drive in Windows and shrunk the system (C:) partition and added another partition intended to be a secondary drive in Windows. After rebooting Windows throws a BSOD and I can't even select OS X as a bootable option. Is anyone able to point me in the right direction on how to fix? Thank you!
I learned the FAQ the hard way
diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_parition_scheme *251.0 GB disk0
1: Windows_LDM 77.0GB disk0s1
2: Windows_LDM 94.5GB disk0s2
3: Windows_LDM 79.5GB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *1.3 GB disk1
1: Apple_partition_map *30.7 KB disk1s1
2: Apple__HFS OS X Base System *1.3 GB disk1s2
From there it does /dev/disk2, /dev/disk3, until /dev/disk12 usually like:
#: TYPE NAME SIZE IDENTIFIER
0: untitled *524.3 KB disk2
diskutil cs list
No CoreStorage logical volume groups found
gpt -vv -r show /dev/disk0
gpt show: /dev/disk0: mediasize=251000193024; sectorsize=512; blocks=490234752
gpt show: /dev/disk0: MBR at sector 0
gpt show: /dev/disk0: Malformed MBR at sector 0
gpt show: /dev/disk0: Bad CRC in GPT table at sector 2
start size index contents
0 1 MBR
1 150392831 1 MBR part 66
150392832 184604672 2 MBR part 66
334997504 155235200 3 MBR part 66
490232704 2048
fdisk /dev/disk0
DIsk: /dev/disk0 geometry: 30515/255/63 [490234752 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
1: 42 0 0 2 - 1023 254 63 [ 1 - 150392831] LinuxSwap DR
2: 42 1023 254 63 - 1023 254 63 [150392832 - 184604672] LinuxSwap DR
3: 42 1023 254 63 - 1023 254 63 [334997504 - 155235200] LinuxSwap DR
*4: 07 0 0 0 - 0 0 0 [ 0 - 0] HPFS/QNX/AUX -
Use securefile for new partitions made by interval partitioning
I am using Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production.
I have a range partitioned table having lobs as basicfile. Due to storage issue and other business constraints , it is determined not to change existing lobs to securefile.
However ,we want new lobs to be in securefile and alter table to have interval partition+.
While researching, I found sql to change lob in range partition to securefile by using
alter table t1 add partition t1_p2 value less than (10000) lob (col3) store as securefile (tablespace tbs_sf1)Please advise me to do similar in case of interval partition.
Many thanks for assistance.>
Can we modify default attribute of lob to store as securefile for partition table.
>
Yes - that is what I meant in my reply. But it seems I may have been wrong since after further testing I was able to find syntax that would appear to work for you. Please test this and post the results.
The line
LOB(CLOB_DATA) store as securefileshould store intervals as securefile. But it accepted syntax to store the predefined partitions as basicfile
PARTITION P0 VALUES LESS THAN
(TO_DATE(' 2008-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
LOB(CLOB_DATA) store as basicfile,I don't have time to test with data until next week. But if this works you could predefine all of your partitions that you want to use basicfile for and then use interval partitions for the ones you want securefile for. That sounded like what you were trying to do.
DROP TABLE INTERVAL_SALES1 CASCADE CONSTRAINTS;
CREATE TABLE INTERVAL_SALES1
PROD_ID NUMBER(6),
CUST_ID NUMBER,
TIME_ID DATE,
CHANNEL_ID CHAR(1 BYTE),
PROMO_ID NUMBER(6),
QUANTITY_SOLD NUMBER(3),
AMOUNT_SOLD NUMBER(10,2),
CLOB_DATA CLOB
LOB(CLOB_DATA) store as securefile
PARTITION BY RANGE (TIME_ID)
INTERVAL( NUMTOYMINTERVAL(1,'MONTH'))
PARTITION P0 VALUES LESS THAN
(TO_DATE(' 2008-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
LOB(CLOB_DATA) store as basicfile,
PARTITION P1 VALUES LESS THAN (TO_DATE(' 2009-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')),
PARTITION P2 VALUES LESS THAN (TO_DATE(' 2009-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')),
PARTITION P3 VALUES LESS THAN (TO_DATE(' 2010-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
)Post the results of any testing you do. -
New-Partition assignes driver letter to mount point after reboot.
Trying to create a series of mount points using powershell on Server 2012 R2. When I have used diskpart in the past I could initialize the disk, create a partition, format a volume and assign a mount point without assigning a driver letter to the drive.
When I try to do the same thing in Powershell on Server 2012 R2, everything looks great until I reboot. Every partition I created and assigned as a mount mount gets a driver letter added to it... I am using mount points to avoid drive letters. Is there a way
to prevent this behavior. The following is an example:
Get-Disk 3 | Initialize-Disk -PartitionStyle GPT
Get-Disk 3 | new-Partition -UseMaximumSize -AssignDriveLetter:$False | Format-volume -confirm:$False
Add-Partitionaccesspath -DiskNumber 3 -Partition 2 -AccessPath c:\someFolder
Everything looks good at this point with no driver letter assigned. Rebooting adds a driver letter to the volume with no impact on the mount point... Is there a way to suppress the driver letter assignment?Figured it out... It appears that this part works fine:
Get-Disk 3 | Initialize-Disk -PartitionStyle GPT
$Part = Get-Disk 3 | new-Partition -UseMaximumSize -AssignDriveLetter:$False
$Part | set-partition -NoDefaultDriveLetter:$True
$Part | Format-volume -confirm:$False
If you look at the output of Get-Partition the NoDefaultDriveLetter value is TRUE. After running Add-PartitionAccessPath it changes to FALSE. You can set it back with the Set-Partition command:
Get-Partition -DiskNumber 3 -Partition 2 | add-PartitionAccessPath c:\SomePath -passthru | set-Partition -NoDefaultDriveLetter:$True
I had a bunch of them to do so I used the following:
Function Config-Disk {
[cmdletbinding()]
Param(
[INT]$Disk,
[INT]$Partition = 2,
[String]$Label,
[String]$MountPoint
Get-Disk $Disk | Initialize-Disk -Partitionstyle GPT
Get-Disk $Disk | New-Partition -UseMaximumSize |
Format-Volume -FileSystem NTFS -NewFileSystemLabel $Label -Confirm:$False
Add-PartitionAccessPath -DiskNumber $Disk -PartitionNumber $Partition -AccessPath $MountPoint -Passthru |
set-Partition -NoDefaultDriveLetter:$True
MD "c:\SomeLocation1"
MD "c:\SomeLocation2"
Config-Disk -Disk 3 -Label "SomeLabel1" -MountPoint "c:\SomeLocation1"
Config-Disk -Disk 4 -Label "SomeLabel2" -MountPoint "c:\SomeLocation2" -
Hello.
I have a problem. I want to install WinXP via BootCamp and can't create new partition for it.
BootCamp Assistant crashes during partitioning (kernel panic), and when I use Leopard installation disk and try to create new partition in Disk Utility on DVD, it returns an error "No space left on device".
I repaired my hard disk many times (all errors were repaired) and still no improvement.
I don't want to format my disk to zero, because I don't use Time Machine and it would be really difficult to restore all the data.
Thank you in advance.Use Disk Utility Restore to copy your internal drive to an external USB/FW drive. Then reformat.
-
After i had created new partition, bootcamp partition was disappear in the boot screen
I was created a new partition for mac os x yosemite after that day I cant see bootcamp partition on boot screen (press alt while startup) but bootcamp partition can see in desktop and system preferences>startup disk. When I was startup windows from preferences>startup disk, I see this writing "no bootable device".
So how can I fix my windows partition? Please help!!!
Christopher Murphy can you help me? You look like expert of this area.
Are these help for the solution?
Merts-MacBook-Pro-2:~ Mert$ sudo gpt -r -vv show disk0
Password:
gpt show: disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
gpt show: disk0: Suspicious MBR at sector 0
gpt show: disk0: Pri GPT at sector 1
gpt show: disk0: Sec GPT at sector 1953525167
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 1243298208 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
1243707848 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
1244977384 5422872
1250400256 703123456 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
1953523712 1423
1953525135 32 Sec GPT table
1953525167 1 Sec GPT header
Merts-MacBook-Pro-2:~ Mert$ sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 121601/255/63 [1953525168 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 1243298208] HFS+
3: AB 1023 254 63 - 1023 254 63 [1243707848 - 1269536] Darwin Boot
4: 0C 1023 254 63 - 1023 254 63 [1250400256 - 703123456] Win95 FAT32LYou can not create another partition on a drive containing a Boot Camp partition. You now need to erase then format your drive. Reinstall OSX then reuse Boot Camp Assistant to create a new Boot Camp partition. Reinstall Windows. Ensure you copy off all your data before erasing and formatting the drive.
-
Repairing bootcamp after creating new partition
Like others who have posted here, I had two partitions, MacOS and Bootcamp that worked just fine. I then added a new partition because I need a "D" drive in Windows configuration to be able to install a particular set of programs that rely on such a configuration (long story and perhaps there was a better way). Once I added the new NTFS partition and rebooted, I no longer see the Windows drive as a a boot option. I don't know if the command line "sugo" utility and syntax that I've seen in postings here applies to all such situations but if anyone can guide me through it I would be very grateful. Thanks
No worries. Here you go. I'm glad you can interpret this stuff.
sudo gpt -vv -r show /dev/disk0
gpt show: /dev/disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 1953525167
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 1664355600 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
1664765240 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
1666034776 936
1666035712 44627968 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
1710663680 242860032 5 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
1953523712 1423
1953525135 32 Sec GPT table
1953525167 1 Sec GPT header
sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 121601/255/63 [1953525168 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 1664355600] HFS+
3: AB 1023 254 63 - 1023 254 63 [1664765240 - 1269536] Darwin Boot
4: 07 1023 254 63 - 1023 254 63 [1666035712 - 44627968] HPFS/QNX/AUX
sudo dd if=/dev/rdisk0s5 count=1 2>/dev/null | hexdump -C
00000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS .....|
00000010 00 00 00 00 00 f8 00 00 3f 00 ff 00 00 a8 f6 65 |........?......e|
00000020 00 00 00 00 80 00 80 00 ff bf 79 0e 00 00 00 00 |..........y.....|
00000030 00 00 0c 00 00 00 00 00 02 00 00 00 00 00 00 00 |................|
00000040 f6 00 00 00 01 00 00 00 9a b9 e6 6e d8 e6 6e 0c |...........n..n.|
00000050 00 00 00 00 fa 33 c0 8e d0 bc 00 7c fb 68 c0 07 |.....3.....|.h..|
00000060 1f 1e 68 66 00 cb 88 16 0e 00 66 81 3e 03 00 4e |..hf......f.>..N|
00000070 54 46 53 75 15 b4 41 bb aa 55 cd 13 72 0c 81 fb |TFSu..A..U..r...|
00000080 55 aa 75 06 f7 c1 01 00 75 03 e9 dd 00 1e 83 ec |U.u.....u.......|
00000090 18 68 1a 00 b4 48 8a 16 0e 00 8b f4 16 1f cd 13 |.h...H..........|
000000a0 9f 83 c4 18 9e 58 1f 72 e1 3b 06 0b 00 75 db a3 |.....X.r.;...u..|
000000b0 0f 00 c1 2e 0f 00 04 1e 5a 33 db b9 00 20 2b c8 |........Z3... +.|
000000c0 66 ff 06 11 00 03 16 0f 00 8e c2 ff 06 16 00 e8 |f...............|
000000d0 4b 00 2b c8 77 ef b8 00 bb cd 1a 66 23 c0 75 2d |K.+.w......f#.u-|
000000e0 66 81 fb 54 43 50 41 75 24 81 f9 02 01 72 1e 16 |f..TCPAu$....r..|
000000f0 68 07 bb 16 68 70 0e 16 68 09 00 66 53 66 53 66 |h...hp..h..fSfSf|
00000100 55 16 16 16 68 b8 01 66 61 0e 07 cd 1a 33 c0 bf |U...h..fa....3..|
00000110 28 10 b9 d8 0f fc f3 aa e9 5f 01 90 90 66 60 1e |(........_...f`.|
00000120 06 66 a1 11 00 66 03 06 1c 00 1e 66 68 00 00 00 |.f...f.....fh...|
00000130 00 66 50 06 53 68 01 00 68 10 00 b4 42 8a 16 0e |.fP.Sh..h...B...|
00000140 00 16 1f 8b f4 cd 13 66 59 5b 5a 66 59 66 59 1f |.......fY[ZfYfY.|
00000150 0f 82 16 00 66 ff 06 11 00 03 16 0f 00 8e c2 ff |....f...........|
00000160 0e 16 00 75 bc 07 1f 66 61 c3 a0 f8 01 e8 09 00 |...u...fa.......|
00000170 a0 fb 01 e8 03 00 f4 eb fd b4 01 8b f0 ac 3c 00 |..............<.|
00000180 74 09 b4 0e bb 07 00 cd 10 eb f2 c3 0d 0a 41 20 |t.............A |
00000190 64 69 73 6b 20 72 65 61 64 20 65 72 72 6f 72 20 |disk read error |
000001a0 6f 63 63 75 72 72 65 64 00 0d 0a 42 4f 4f 54 4d |occurred...BOOTM|
000001b0 47 52 20 69 73 20 6d 69 73 73 69 6e 67 00 0d 0a |GR is missing...|
000001c0 42 4f 4f 54 4d 47 52 20 69 73 20 63 6f 6d 70 72 |BOOTMGR is compr|
000001d0 65 73 73 65 64 00 0d 0a 50 72 65 73 73 20 43 74 |essed...Press Ct|
000001e0 72 6c 2b 41 6c 74 2b 44 65 6c 20 74 6f 20 72 65 |rl+Alt+Del to re|
000001f0 73 74 61 72 74 0d 0a 00 8c a9 be d6 00 00 55 aa |start.........U.|
00000200 -
No boot disk after creating a USB bootable device with Bootcamp Assistant.
Hi people, i was trying to install windows on my Mac Pro 4,1. I had to modify the Info.plist in Bootcamp Assistant to be able to make a bootable usb, after choosing and creating the bootable usb my mac rebooted and after i got into a black screen saying "no bootable device"...i tried Win7 and Win8.1 on 2 different USB sticks without any luck. Any ideas? Thank you!
Disregard this message. I give up.
-
Bootcamp - No bootable device -- insert boot disk and press any key help plz
Hello there!
I recently upgraded my imac mid 2010 system with a SSD hard-drive. The old "main" drive went to the place of super-drive and after reinstalling OS X into the new drive and wiping the old drive a very interesting problem happened. I started trying to install windows 7 via bootcamp. I did everything what the bootcamp assistant says and after the imac restarts itself it just says No bootable device -- insert boot disk and press any key. Firstly I thought that maybe something is wrong with the installation disk (i have an external super-drive connected to the imac). After restarting the imac once again i held down the option button and arrived to the screen, where it shows the avlaible boot options (different disks). Now, what I saw, was funny. The bootcamp assistant had'nt created the bootcamp drive at all. Atleast it did not show it. After doing this two-three times the result was the same. My next idea was that maybe, there is an issue with the concrete SSD model I am using. So I went back to OS X and opened the bootcamp assistant and restored the state of the OS X SSD drive. Next I did an bootcamp partition onto the old drive I have installed. But the result is still the same. Now my head is empty of ideas.
Has anybody had a similar problem and can you please give me tutorial what I did wrong or what to try next?
Thanks.
Indrek.Hi Michael!
Yep, I did get this running. Not in a normal way (meaning the easy way). What I did, is that I just created the BOOTCAMP partition in OS X. Just let it format and create the partition where you would install BOOTCAMP.
After that I discovered that via a ISO program (WinClone) you can directly restore a previously created OS X boot image to your current computer. So, I installed a blank Windows 7 to my macbook pro, didint install any drivers and just let it work up then. Then I went back to os X (in macbook pro) and made a bootimage for the BOOTCAMP partition. After that I saved it to my external harddrive and wired it to my iMac. In iMac I just downloaded the same boot-image program and restored the bootimage that I made in Macbook Pro to iMac. After that I made an restart and the bootcamp section with windows worked well with my iMac. Install the bootcamp soft and you can do everything and everything works. FYI, you get the windows working via those steps, BUT if you either delete or do anything to make your bootcamp partition unworkable then you will have to repeat those steps again. But it´s fast non-the-less, so it shouldn´t be a problem for you.
If you didin´t understand anything or something doesen´t add up, send me a letter or a notification.
Hope this helps.
Indrek. -
Made a new partition on Macintosh HD, Boot Camp will no longer boot.
Specs:
MacBook Air 2013
8GB RAM
i7
512GB SSD
Hello all, looking for some assistance.
My HD is formatted to 400GB of OSX and 80GB of Boot Camp. I stupidly made the mistake of adding a new partition out of the large amount of free space I have on the OSX partition, to format the new partition for Windows. This made Boot Camp no longer boot. On the Disk select screen after holding Option on boot, my Boot Camp partition is not visible. I can see everything on the partition on OSX, however.
To try and fix this, I deleted the new partition and tried to reduce the hard drive back to the original two partitions. However, I cannot extend the OSX partition to fill in the new free space. So now I have a Boot Camp partition, my OSX partition, and 20GB of unused, free space that I cannot use or put back into the original partition.
I asked AppleCare live chat for any assistance, they suggested that I use "Erase free space" in Disk Utility to use the space again. However, the option is greyed out on both the drive and the Macintosh HD partition.
After a bit of googling I saw a suggestion of making a USB Recovery drive to get the space back through Disk Utility that way. This still did not work; the results were the same, unable to add the space back to the original partition, and "Erase free space" is still greyed out.
Using BootChamp (notice the H, this is an app that allows you to restart and boot directly into Boot Camp through OSX), I get a DOS screen saying "No bootable device – insert boot disk and press any key". I cannot get this screen any other way.
I have repaired and verified the disk and its permissions, to no avail.
I cannot think of anything else to do short of formatting the entire drive but this is obviously less than preferable. I additionally do not have a backup of the BootCamp partition (as it is not accessible), even though everything is visible on the partition through OSX.
So, in summary, I added a new partition to my HD and now Boot Camp will not boot. Any ideas?"rEFIt is an alternative bootloader for your Mac that's a lot more forgiving. If you don't think investing in iPartition is worth it, I'd give this a shot:
In rEFIt, do not boot: go to the EFI shell, and type "gptsync". This will tell you that the partition table is out of sync, and will offer to sync it for you. Say "yes", naturally. Now reboot and all systems should be go!"
This worked. -
Bootcamp - The disk cannot be partitioned because some files cannot be moved.
I know what you're thinking; this question has been posed before. But my circumstances are different.
Sooo I bought a brand new Macbook Pro 15" Retina, late-2014 model on Monday. After some initial setup (moving my music, downloading programs etc.) I moved onto the last thing I needed to do - set up bootcamp (primarily for gaming I admit).
Specs: 2.8GHz Quad-core Intel Core i7, Turbo Boost up to 4.0GHz
16GB 1600MHz DDR3L SDRAM
1TB PCIe-based Flash Storage - In total the files I moved onto it left me with about 890GB free on the HD.
At this point I had made sure everything was updated as far as I was aware.
I received the error message "The disk cannot be partitioned because some files cannot be moved." I was trying to make a 151GB partition but also tried going down to 40GB and received the same message. I tried several solutions I found online including booting in cmd+s and typing in some codes, I checked the disk with disk utility and it was fine.
Nothing much for it and I was feeling lazy, I backed up with Carbon Copy Cloner (I much prefer this program to time machine) and reformatted. Clean install of OSX Yosemite and the Macbook looked like it had just come out of the box. Before I even attempted to restore using CCC I started up bootcamp again: same error. With essentially a brand new Macbook Pro right out of the box, near to 1TB HD space free.
I've taken it to the local Apple store but they "Don't have any support for bootcamp in-store" and I'm out of the house for 12 hours a day with work (I'm actually at work now). Plus you know, I require food and such, so I don't get much time to get in touch with Apple support directly.
The guy at the Apple store recommended Parallels or Visualbox; note that I want to use bootcamp. I like the extra power and I have a copy of Windows 8.1 from a previous Macbook Pro that worked wonderfully through bootcamp. This should work as far as I am concerned and I don't want to accept anything less to be honest.
Any ideas?Hi Loner T,
Thanks for your suggestion, however I did a step wrong and I am facing another bigger problem.
Step 1 was to use time machine to backup OSX, looks like I failed to do that, and only backed up the data instead. Because after I erase my internal disk, I cant restore from TM.
So now the situation is that I can't access my HD, can't reinstall Mac to that hard disk (it is not detected), Cant use DU to repartition the hard disk as well, option not selectable.
What can I do now? -
'No bootable disk' error message when installing Windows7 with Bootcamp
Hey,
It seems so many people have had this problem which I am having now, I've tried searching for a solution that works but to no avail. So I'll give as much detail to this problem in the hope that someone knows the answer!
When running bootcamp assistant in order to install Windows 7 on my MacBook Pro (running Lion), I am able to go through all the steps - create USB installer, download software and partition hard drive. However, when the computer restarts I am faced with the black screen displaying "No bootable device - insert disk and press any key to continue". Nothing seems to work!
I've tried using a DVD instead of a usb to install Windows, using a burned copy of the ISO disk image (in UDF format) of Windows and I've tried using a sony and a san disk USB. I've tried holding down the option key on start up to see if I can select the disk manually but nothing appears (just my hard drive and the recovery mode).
Any help would be really appreciated! I'm in need of windows in order to run some programs to carry out data analysis on endangered species for research.Thanks Bob! My problem was that I was following advice from elsewhere on the internet that said I should burn a DVD in UDF format when in fact just burning it using disk utility in ISO made it work. Thank you so much!
Maybe you are looking for
-
Brought my new iPad it's battery & heating prob
The battery drains a lot even I am using in 3G mode & watching hd movies,the major problem is the heating one,it's heat's a lot itself & my palm too,heating means vigorous heating. Plz help me out wid som tips.
-
First two lines of each page... - Format Issue
I have a manual I am currently updating. I am unaware of how it was formatted initially but it is currently pushing the first two lines of each page all the way to the left margin. I have checked everything I know to check for the format setting an
-
ITunes updating crashing windows?
This is third time I'm typing due to some unknown error apple website is showing me. It's hard to type whole thing again and again. I happen to follow the lates iTunes update notification for windows and installed. It asked me to restart and after re
-
Itunes won't work on Windows xp
I installed itunes on my computer, i have windows xp family edition, and when i try to open the application, it says i need windows 2000 or higher to use this application, same goes for quicktime, any idea what wrong?
-
Color Correction -- render does NOT match preview
Something seems very odd about Color Correction. I select a clip that is too dark. I adjust the slider to lighten it up while previewing. It looks perfect. Now I APPLY and the rendered video is very different. Typically now way too light. So I adjust