I had a semi-successful OSX86 install with iDeneb 1.3, though it was buggy and took 7 minutes to boot or shut down, but at least it worked. Then to try and fix problems, I installed the voodoo kernel, and that didn't help. So then I tried installing iPC's 10.5.6, and now I no longer have a booking OSX: it dies at 'boot1: error'. I have tried:
- Using EasyBCD to "repair" the hfs+ file system.
- Re-installing using the DVD, and then installing the chamelion boot loader.
- Booting into -s mode with the DVD, and using fdisk to flag the partition.
- Several attempts at erasing the partition and installing other distributions, including iPC 10.5.6 and LawlessPC (Zephyroth) 10.5.4, using both bare-minimum selections and using the packages I think I'd need for my system.
After every one of these, I get the same result: trying to boot to OSX using the Vista bootloader entry dies with boot1: error. So it seems like more of a boot loader problem than a distribution selection issue, but I'm not sure. What else can I try?
Same problem Here
I have exactly the same problem after the Ideneb 1.3 installation.
I have seen that the ddisk ID (in the utilitydisk) have changed after the installation:
Primary HDD 80GB SATA was disk0s1 (1part, guid)
secondary HDD 500 GB was disk0s2 (FAT32 - common-win-osx)
Now, the drive ID is inverssed(?)!!
1st drive with Osx is disk0s2 !!! and Osx try to boot on disk0s1
I need to change the bootloader, but, why the drive have changed ?? I noticed that osx boot with the idenebdvd inserted on the boot.
Maybe, i got to put sata80GB on SATA2connector and try...i will let know what...if you find a solution, please, contact me !
sorry for my poor english, i'm french guy :-)
I have maybe found the solution about the disk0:error !!
When you create a GUID partition, Osx set a new small partition (200mb-efibios) This partition become real after the installation, and ask to be set on disk0s1 ! Then, the previously disk0s1 is incremented..disk0s2..cqfd
Then, to resolve the problem, i got try this:
netkas.org About GUID
But now, there is a efi V9 then, i'm busy to find a update of this tutorial...
Hope that can help you,
To clarify my problem (boot1, not boot0): the Vista boot loader still works, and I can still use it to boot into both Vista and XP partitions on the same disk as the OSX partition (SATA disk 1). However, selecting the OSX option in the same boot loader fails with this "boot1" error.
In addition, ever since OSX was installed, a grub loader on another disk (IDE disk 0) for a Linux installation no longer works and complains that there's no OS installed.
Is this still a GUID issue?
yesterday, i have try to change the cootsector without result.
Always same problem...
I have found a new procedure to try:
Open up a terminal.
//Change directory to the bootloaders section, so I don't have to type out as much.
diskutil umount /dev/disk#s#
//Unmount all active partitions, so dd will work.
dd if=boot0 of=/dev/disk# bs=400 count=1
//Writes the MBR loader to search for the boot1h
dd if=boot1h of=/dev/disk#s#
//Writes the boot handler for HFS partitions.
startupfiletool -v /dev/disk#s# bootefi9
//Writes the EFIv9 bootloader to Leopard's partition.
bless -v /dev/disk#s#
Reboot and I am not liable. This was done using iAtkos, startupfiletool's arguments may vary.
This worked, but I did it after I had installed Leopard, so these are just the steps to fix your bootloader. G'luck!
Voila, (i think that we need to copy the boot1h file into on the hdu )before.
Thanks cber; I'll give this a try. I think I have tried just about everything else: I even re-partitioned my IDE drive 0 last night and re-installed a fresh copy of OSX there, but the error never changed. I then re-installed Linux on a second partition on that drive, and added the OSX partition to its grub boot loader, but loading it from there resulted in another error (not bootable, or something to that effect). I am starting to think I'm running out of options, but it's hard to believe that only a few people have run into this problem, and that nobody knows for sure how to fix it ...
About your terminal procedure: will I be able to run this if I can't boot into the installation? If I run one of the OSX86 install discs and open a terminal from there, should I be able to run these commands (I assume un-mount won't be a problem, but the others)?
I think (but I'm not sure) that 'bless' makes the selected partition active, meaning it can be booted.
Wasn't sure which partition to perform this procedure on: EFI or HFS? I gave it a try anyway... according to 'diskutil list':
The partition on disk2 was my original installation; s1 is XP and s2 is Vista. disk0 had both OSX and Linux installed.
s1 EFI 200M
s2 AppleHFS 40G
s3 AppleHFS 40.1G
I tried your procedure on both disk0s1 and disk0s2:
startupfiletool -v /dev/disk0s[1|2] bootefi9
- I didn't have 'startupfiletool' in my installation or distribution; I had to get it from elsewhere, copy it, and +x it
- On s1, I got "Unrecognized filesystem", and on s2 I got "No such file or directory" (on bootefi9, I assume). I couldn't write to the /usr/standalone/i386 directory to touch/create a new file.
The only other thing of note was that when I tried 'bless -v' on anything, it returned "Dummy bless executed!"
- Booting from the Vista boot loader returns "boot1: error", as before.
- Booting from disk0, which used to be Linux's grub loader, now returns garbage lines and then a boot error.
Any thoughts on what I did wrong? Any pointers to an online tutorial or resource I could read in order to find answers? Please help?
No, unfortunately, still stuck as explained above in #7.
Originally Posted by icchansan