Fixing boot1 error? 10.8.2

[coolblue8]

Just completed the boot0 rdisk fix from this guide: http://www.mymac4music.com/2011/10/boot0-error/

HOWEVER, now when I boot from HDD, I get a boot1 error! It says boot0: done on the line before, but now its trying to boot off of disk1, which is not where the mac os is installed.

 

[RehabMan]

Just completed the boot0 rdisk fix from this guide: http://www.mymac4music.com/2011/10/boot0-error/

HOWEVER, now when I boot from HDD, I get a boot1 error! It says boot0: done on the line before, but now its trying to boot off of disk1, which is not where the mac os is installed.

Need to know more info about your disk layout, where you installed Chimera, etc.
Start with output from 'diskutil list' in Terminal...

 

[coolblue8]

Need to know more info about your disk layout, where you installed Chimera, etc.
Start with output from 'diskutil list' in Terminal...

I had to make two partitions because of my 1TB HDD-500GB storage, and Macintosh OS (thats where the OS is installed)

Here is the diskutil (my boot0 fix was on disk0s3):

/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS 500GB Storage 500.1 GB disk0s2
3: Apple_HFS Macintosh OS 499.6 GB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *16.4 GB disk1
1: Apple_HFS PNYUSB 16.4 GB disk1s1

disk1 seems to be my UniBeast USB, which I keep plugged in, in order to boot

BTW, Chimera has not worked for me yet

 

[RehabMan]

I had to make two partitions because of my 1TB HDD-500GB storage, and Macintosh OS (thats where the OS is installed)

Here is the diskutil (my boot0 fix was on disk0s3):

/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS 500GB Storage 500.1 GB disk0s2
3: Apple_HFS Macintosh OS 499.6 GB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *16.4 GB disk1
1: Apple_HFS PNYUSB 16.4 GB disk1s1

disk1 seems to be my UniBeast USB, which I keep plugged in, in order to boot

BTW, Chimera has not worked for me yet

I wonder if perhaps your /dev/disk0s2 partition has a boot record on it, but no /boot file.
If while you were mucking about, you wrote the boot1h to /dev/disk0s2 instead of /dev/disk0s3?

To check:

# read boot record (1024 bytes) from disk0 part2, write to /tmp/br
sudo dd if=/dev/rdisk0s2 bs=512 count=2 of=/tmp/br
# look at the end of that boot record
xxd </tmp/br| tail

If the last word of the output is 55aa, then you've got the boot record on there, but likely do not have the rest of Chimera there because it is more than likely on /dev/disk0s3.

 

[coolblue8]

I wonder if perhaps your /dev/disk0s2 partition has a boot record on it, but no /boot file.
If while you were mucking about, you wrote the boot1h to /dev/disk0s2 instead of /dev/disk0s3?

To check:

# read boot record (1024 bytes) from disk0 part2, write to /tmp/br
sudo dd if=/dev/rdisk0s2 bs=512 count=2 of=/tmp/br
# look at the end of that boot record
xxd </tmp/x | tail

If the last word of the output is 55aa, then you've got the boot record on there, but likely do not have the rest of Chimera there because it is more than likely on /dev/disk0s3.

Here is what came up:
2+0 records in
2+0 records out
1024 bytes transferred in 0.000245 secs (4177984 bytes/sec)
Battistos-Mac-Pro:~ battistomac$ # look at the end of that boot record
Battistos-Mac-Pro:~ battistomac$ xxd </tmp/x | tail

Is the "xxd" the last word?

Thank you for your patience

 

[RehabMan]

Here is what came up:
2+0 records in
2+0 records out
1024 bytes transferred in 0.000245 secs (4177984 bytes/sec)
Battistos-Mac-Pro:~ battistomac$ # look at the end of that boot record
Battistos-Mac-Pro:~ battistomac$ xxd </tmp/x | tail

Is the "xxd" the last word?

Thank you for your patience

Oh, I see my mistake. Last command should be:

xxd </tmp/br | tail

BTW, you don't have to type the comments (comments start with #)

 

[coolblue8]

Oh, I see my mistake. Last command should be:

xxd </tmp/br | tail

BTW, you don't have to type the comments (comments start with #)

OK heres what came up now:

2+0 records in
2+0 records out
1024 bytes transferred in 0.000256 secs (3999038 bytes/sec)
Battistos-Mac-Pro:UNIBEAST battistomac$ xxd </tmp/br | tail
0000360: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000370: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000380: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000390: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
Battistos-Mac-Pro:UNIBEAST battistomac$

 

[RehabMan]

OK heres what came up now:

2+0 records in
2+0 records out
1024 bytes transferred in 0.000256 secs (3999038 bytes/sec)
Battistos-Mac-Pro:UNIBEAST battistomac$ xxd </tmp/br | tail
0000360: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000370: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000380: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000390: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
Battistos-Mac-Pro:UNIBEAST battistomac$

Well, it wasn't that because that is clean (no boot record there). Maybe you should do the same thing with /dev/rdisk0s3 to verify that there *is* a boot record there. And then look at your root to verify you have a /boot.

That's all I can think of for now...

 

[coolblue8]

Well, it wasn't that because that is clean (no boot record there). Maybe you should do the same thing with /dev/rdisk0s3 to verify that there *is* a boot record there. And then look at your root to verify you have a /boot.

That's all I can think of for now...

Do you think it might have to do with the hard drive itself? I was thinking of buying a separate 32gb SSD and loading the bootloader onto that one.

 

[coolblue8]

You won't believe what the actual problem was.

I COMPLETELY FORGOT TO RE-MOUNT THE HDD AFTER THE TERMINAL FIX!


Anyway, thank you for your help! I will use it if I have a REAL problem next time!