Jump to content
24 posts in this topic

Recommended Posts

In order to keep my 10.4.3 partition as a backup, I installed 10.4.4 to my smaller SATA drive. Once I determined 10.4.4 was up and running with no problems, I went ahead and wiped 10.4.3. I then used Disk Utility to restore my 10.4.4 from the smaller drive to the larger drive. I can not seem to get it to boot from that larger drive. Once I change my boot drive in BIOS and it begins booting from the larger drive, it immediatly goes to a screen with a blinking cursor in the left hand corner. I never even see the starting darwin message. Anyone have any ideas?

Link to comment
https://www.insanelymac.com/forum/topic/9401-moving-os-x-1044/
Share on other sites

I made a thread about this in the OSX86 Installation Section, which I pasted below. Anyway, in diskutil, did you check the box to erase the partition? When you check that box, I believe you lose the MBR. You may be able to use use this command in single user mode to make your drive bootable:

sudo bless -mount /Volumes/macosx-10.4.4 -setBoot

 

Or maybe the steps below might help.

 

If you only have room for two operating systems on your PC (i.e. WinXP and OS X) this may be of use to you.

 

Assume 10.4.3 is already installed (i.e on partition #1 of disk0). Assume 10.4.4 is installed on a different partition (i.e. partition 1 of your external usb drive). And assume you want to transfer the 10.4.4 installation to the 10.4.3 partition, thereby replacing 10.4.3 with 10.4.4. This may help you:

 

1. Boot into the existing 10.4.4 installation and make sure it works the way you want it.

 

2. Backup your 10.4.3 extensions folder if you think you may need them in the future.

 

3. Using terminal app, manually delete all files and folders from the 10.4.3 partition that you do not want to keep. The command is "rm -R <file or directory>" without quotes. You want to delete the kernels, hidden files, system files. You can leave the files "Desktop DB" and "Desktop DF" alone. Note that at this step you are destroying the 10.4.3 installation.

 

4. Next open Disk Utility. Go to the Restore tab. Make the source your 10.4.4 installation and the target your, now unbootable, 10.4.3 partition.

 

5. Uncheck the box "Erase Destination" so that 1) Your MBR stays intact, and 2) Any files you want saved on your 10.4.3 partition won't be erased by this process.

 

6. After the transfer is complete, don't reboot yet. First repair permissions on the new 10.4.4 partition.

 

7. Reboot into single user mode on the new 10.4.4 partition. Follow Maxxuss' 10.4.4 instructions regarding fixing the extensions in single user mode.

 

8. Reboot into the new 10.4.4 partition normally. Repair disk permissions again.

 

9. System should now be ready for use.

In order to keep my 10.4.3 partition as a backup, I installed 10.4.4 to my smaller SATA drive. Once I determined 10.4.4 was up and running with no problems, I went ahead and wiped 10.4.3. I then used Disk Utility to restore my 10.4.4 from the smaller drive to the larger drive. I can not seem to get it to boot from that larger drive. Once I change my boot drive in BIOS and it begins booting from the larger drive, it immediatly goes to a screen with a blinking cursor in the left hand corner. I never even see the starting darwin message. Anyone have any ideas?

maybe wiping off 10.4.3 is a bad idea since present solution (i think) needs it to boot 10.4.4 (or maybe i am wrong)... without 10.4.3 i think we need EFI bootlloader to boot 10.4.4 which is a headache now..

I used Kiko's method and it worked perfectly. Short run down on what I did.

 

Background:

I have two hard drives, a 160 Gb and a 120 Gb. My ORIGINAL 10.4.3 was on the 160, and that is where I wanted 10.4.4 to be when I was done.

 

I installed 10.4.4 using Maxxus' method to my 120 Gb. Once I verified everything was working, I restored using Disk Utility 10.4.4 to the 160 Gb drive. It would not boot off the 160.

 

Solution:

Used Kiko's method. Wiped out my 160 Gb drive (again) and this time did a barebones install of 10.4.3 back to it. Once 10.4.3 install was done I booted back into 10.4.4. I then removed (as in manually deleted NOT formatted) all data on the 10.4.3 drive. I then used disk utility to restore my working 10.4.4 install from the 120 to the 160. I made sure ERASE DESTINATION was turned OFF.

 

Final word:

It worked. Now up and running on 10.4.4 on my 160. Thanks Kiko. I know plan to repartition my 120, with two partitions. A 10 Gb partition to load another fresh barebones of 10.4.3 in case it is needed in the future and the rest will become video storage.

I used Kiko's method and it worked perfectly. Short run down on what I did.

 

Background:

I have two hard drives, a 160 Gb and a 120 Gb. My ORIGINAL 10.4.3 was on the 160, and that is where I wanted 10.4.4 to be when I was done.

 

I installed 10.4.4 using Maxxus' method to my 120 Gb. Once I verified everything was working, I restored using Disk Utility 10.4.4 to the 160 Gb drive. It would not boot off the 160.

 

Solution:

Used Kiko's method. Wiped out my 160 Gb drive (again) and this time did a barebones install of 10.4.3 back to it. Once 10.4.3 install was done I booted back into 10.4.4. I then removed (as in manually deleted NOT formatted) all data on the 10.4.3 drive. I then used disk utility to restore my working 10.4.4 install from the 120 to the 160. I made sure ERASE DESTINATION was turned OFF.

 

Final word:

It worked. Now up and running on 10.4.4 on my 160. Thanks Kiko. I know plan to repartition my 120, with two partitions. A 10 Gb partition to load another fresh barebones of 10.4.3 in case it is needed in the future and the rest will become video storage.

 

WOW!!! this proof i am wrong.... you got your intel audio card working native... we have the same MOBO.. can you share how you did it regarding the audio... thanks

WOW!!! this proof i am wrong.... you got your intel audio card working native... we have the same MOBO.. can you share how you did it regarding the audio... thanks

I don't have your board, but I did a bit of research. You need the AC'97 driver. You can find it here:

 

http://forum.osx86project.org/index.php?s=...indpost&p=29717

 

It works in 10.4.3 and 10.4.4. Unzip it and do the following in Terminal:

 

sudo -s
cp -R Desktop/AppleAC97Audio.kext /System/Library/Extensions/
cd /System/Library/Extensions/AppleAC97Audio.kext/Contents/PlugIns/
kextload AppleAC97AudioIntelICH.kext
rm /System/Library/Extensions.kextcache
kextcache -k /System/Library/Extensions

 

Reboot and there you go! Good luck!

I don't have your board, but I did a bit of research. You need the AC'97 driver. You can find it here:

 

http://forum.osx86project.org/index.php?s=...indpost&p=29717

 

It works in 10.4.3 and 10.4.4. Unzip it and do the following in Terminal:

 

sudo -s
cp -R Desktop/AppleAC97Audio.kext /System/Library/Extensions/
cd /System/Library/Extensions/AppleAC97Audio.kext/Contents/PlugIns/
kextload AppleAC97AudioIntelICH.kext
rm /System/Library/Extensions.kextcache
kextcache -k /System/Library/Extensions

 

Reboot and there you go! Good luck!

ill try this when ill arrived house.... your post number 5 has a signature of an intel 945GNT MOBO... same as mine... but this reply has another sig... thanks illl really really try this

 

edit: sorry ... its errantwolfe post... sorry

Please guys, we are getting off topic here. This thread is about reloacting your 10.4.4 install, not about getting sound working. i1Sam, you do not use the AC97 codec, you have a Sigmatel 9220 audio chip. Just so others do not continue to post off topic here, instructions for getting LAN and Audio working on a 945GNT board can be found at http://forum.osx86project.org/index.php?sh...042entry58042.

I made a thread about this in the OSX86 Installation Section, which I pasted below. Anyway, in diskutil, did you check the box to erase the partition? When you check that box, I believe you lose the MBR. You may be able to use use this command in single user mode to make your drive bootable:

sudo bless -mount /Volumes/macosx-10.4.4 -setBoot

 

Or maybe the steps below might help.

 

If you only have room for two operating systems on your PC (i.e. WinXP and OS X) this may be of use to you.

 

Assume 10.4.3 is already installed (i.e on partition #1 of disk0). Assume 10.4.4 is installed on a different partition (i.e. partition 1 of your external usb drive). And assume you want to transfer the 10.4.4 installation to the 10.4.3 partition, thereby replacing 10.4.3 with 10.4.4. This may help you:

 

1. Boot into the existing 10.4.4 installation and make sure it works the way you want it.

 

2. Backup your 10.4.3 extensions folder if you think you may need them in the future.

 

3. Using terminal app, manually delete all files and folders from the 10.4.3 partition that you do not want to keep. The command is "rm -R <file or directory>" without quotes. You want to delete the kernels, hidden files, system files. You can leave the files "Desktop DB" and "Desktop DF" alone. Note that at this step you are destroying the 10.4.3 installation.

 

4. Next open Disk Utility. Go to the Restore tab. Make the source your 10.4.4 installation and the target your, now unbootable, 10.4.3 partition.

 

5. Uncheck the box "Erase Destination" so that 1) Your MBR stays intact, and 2) Any files you want saved on your 10.4.3 partition won't be erased by this process.

 

6. After the transfer is complete, don't reboot yet. First repair permissions on the new 10.4.4 partition.

 

7. Reboot into single user mode on the new 10.4.4 partition. Follow Maxxuss' 10.4.4 instructions regarding fixing the extensions in single user mode.

 

8. Reboot into the new 10.4.4 partition normally. Repair disk permissions again.

 

9. System should now be ready for use.

 

will this solution can be applied in upgrading my laptop, i am planning to do this...

 

1. install a 8g1165 to a usb drive thru my existing 8f1111g on my laptop.

2. if it works and running fine on the usb drive..(and hope main lcd will work now w/o dummy external doggle)

3. boot on the 8g1165 usb..

4. manually delete the files under 8f1111g

5. restoring 8g1165 onto the internal hdd unbootable(now) 8f1111g

 

will this work?? i only have 40gig(2 partitions) on my lappy dual boot with mce 2005

 

ps... thanks for the direction errandwolfe(on my audio problem)

I definitely need help :)

 

I had 10.4.3 1111f running fine in dual-boot with Windows XP on my laptop.

 

The laptop has only 1 physical HDD: a 7200rpm Hitachi

 

As I only had 1 primary partition running XP months ago I decided to decrease the size of this partition using Acronis PartitionExpert: I created a second primary partition of 15Gb to install Os X 10.4.3 on. After changing the partition type to AF I could format the partition using Disk Utility while installing from DVD.

 

After this I added the Chain0 to the boot.ini of my Windows XP and I got a perfect multi boot system :)

 

Now, to be able to install 10.4.4 I followed Maxxuss guidelines: I again decreased the size of my Windows XP partition to be able to create a third primary partition using Acronis PartitionExpert: the one to contain Mac Os X 10.4.4

 

After a succesfull install of 10.4.4 and applying all the patches, copying the mach kernel, etc... I rebooted my system to try to launch 10.4.4 in Safe Mode (to get into the GUI as described by Maxxuss)

 

Well: I can't boot 10.4.4: chain error

I can't boot 10.4.3 anymore: HFS+ error

I needed to make the XP partition active again to be able to at least boot into Windows XP again

 

So, my question: anybody can help me to get one of my installed Mac Oses booted: the 10.4.3 or the 10.4.4 one?

 

Any help on this is really appreciated as I stored most of the patches, wiki pages, applications (Camino, etc...) on my 10.4.3 partition as I thought the installation of 10.4.4 would not corrupy my 10.4.3 partition or prevent me from booting :(

 

FYI: I also installed the osl2000 boot manager but even using this I cannot boot from either Mac Os X installation!

 

Anyone???

 

Thx!

 

Take care,

Tek_No

I have this problem too, and there is a way to repair partitions and make them bootable, but the exact procedure escapes me. Until I learn it do the following:

 

1) Leave a bootable Install DVD in your drive. I use the JaS patched 10.4.3 dtk userdvd.

 

2) Boot from this DVD.

 

3) Just sit and wait and don't type anything. After 8 seconds or so, it will actually find which OS X partition is "active" and boot that. I use a bootable floppy and CD with a fdisk-like program to change active partitions when I need to.

 

4) If you didn't set your partition active, the general syntax is to press F8 before you run out of time on the CD boot prompt, then type rd=disk0s2 - this example means partition 2 on your first drive (what would be considered C: by Windows, usually IDE primary master). Change the number after disk to 1 if you're booting a slave drive, 3 if it's the 2nd IDE chain master, and so forth. You have to know a bit about what drives appear in what order to your BIOS. The s2 means second partition, usually most people have Windows or a boot manager on the first partition, so s2..s4, anything beyond 4 would be an extended partition and these ARE NOT BOOTABLE. disk1s1 would work if you have OS X installed on a fresh slave drive.

It seems that the community has progressed towards a patched 10.4.4 Restore DVD that is "out there." This may be the thing people are looking for a user-friendly upgrade from 4.3 to 4.4.

 

See this thread for info about this disc

http://forum.osx86project.org/index.php?showtopic=9625&hl=

I followed the steps and successfully transferred my 10.4.4 to my new 250GB SATA drive. One question. I now get aliases to etc, tmp, var on my root. Didn't have these on my other drive, and when booted to other drive with 10.4.4 there are invisible.. I have tried everything that I could google to make these aliases invisible again with no luck. Any ideas? Has anyone else had this happen?

Disk Utility (Applications/Utilities folder) has a Repair Permissions function, just select the drive with the oddball behavior with it and click the Repair Permissions button... then reboot.

 

Other than that, look for "TinkerTool" which is a free program. It lets you tell the finder to hide or show otherwise invisible files and lots more.

I followed the steps and successfully transferred my 10.4.4 to my new 250GB SATA drive. One question. I now get aliases to etc, tmp, var on my root. Didn't have these on my other drive, and when booted to other drive with 10.4.4 there are invisible.. I have tried everything that I could google to make these aliases invisible again with no luck. Any ideas? Has anyone else had this happen?

 

 

Try what R. Bear Helms suggested. After I did the transfer on my computer, the proper directories were still invisible.

This seems to have worked perfectly (thanks!). One question though:

 

How can I now modify the boot process? After the 10.4.3 to 10.4.4 installation/upgrade, I was left with a 10 second "boot loader" that allows me to choose which version/HD/partition to load. Now that they are both 10.4.4, I'd like to get rid of the old option (or at the very least, switch them around, so that it auto boots to the new [which was old 10.4.3] drive, and then I can just modify the com.apple.Boot.plist to pause for only 1 second or something). Anyone know how I can do this?

 

Thanks

I have this problem too, and there is a way to repair partitions and make them bootable, but the exact procedure escapes me. Until I learn it do the following:

 

Okay. I've been able to fix my own problem (changing the partition which is booted automatically at start up), and I think this may help you guys (with the broken partitions) as well.

 

I totally screwed up my system trying to figure out how to make one partition boot over another. Naively I just deleted one, hoping a Disk Utility repair on the other would do all the work for me. Don't do this; it left me with an unbootable computer. Using your DVD method (with one difference, I had to mash F8 repeatedly RIGHT when the Darwin started loading. Some how this caused an error with the DVD's com.apple.Boot.plist that allowed me to choose the HD I wanted to boot from... Weird, but it worked). I was able to boot, which was some form of relief, but I'd like to be able to boot without a DVD in the drive. So what I did was boot off the DVD into single user mode (F8; -s), and then ran fdisk on my HD (/dev/rdisk0) and changed the partition that was bootable there. Here is how I did that:

 

fdisk -e /dev/rdisk0

// the -e is to edit the MBRs interactively; the disk chosen will obviously depend on your setup.

 

flag 1

// flag "flags" the given (in this case "1" which is /dev/disk0s1) partition as bootable. Again, whether it is 1 or not will depend on your hardware.

 

quit

// not exit, this gives you the option to save

 

and then confirm the changes. I rebooted without the DVD in the drive, and it worked. To say the least, I'm relieved. I hope this is of help to someone else.

Have repaired permissions atleast 5 times and those folders are still visible. Is there away I can repair permission from say single user mode? I even tried setfile terminal command with no luck.. Son of a... Oh well, I guess I can deal with this little annoyance.

 

Hey, if you still can't get it going (from the terminal), there is a little prgram called X-Ray that lets you do it. You just need to load the program, drag the folder/file you want to modify to it, unlock the file, and click on invisible. It may not become invisible until you reboot though.

 

Hope that helps

Hey, if you still can't get it going (from the terminal), there is a little prgram called X-Ray that lets you do it. You just need to load the program, drag the folder/file you want to modify to it, unlock the file, and click on invisible. It may not become invisible until you reboot though.

 

Hope that helps

 

 

Yep, I did that last night with XRay and it worked like a charm.. What an awesome program. I just don't understand why SetFile wouldn't make them invisible but Xray will.. Oh well, I am a happy camper now. Thanks.

  • 5 months later...

Booted from DVD, went into terminal screen.

 

fdisk -e /dev/rdisk0

flag 1

quit

 

MESSAGE OCCURS:

Writing current MBR to disk.

Device could not be accessed exclusively.

A reboot will be needed for changes to take effect. OK? (n)

 

I chose yes.

 

Still NG....

×
×
  • Create New...