Contribute
Register

Cannot boot from new cloned SSD (Snow Leopard) / Help appreciated

Status
Not open for further replies.
Joined
Apr 12, 2013
Messages
16
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
Hi everyone


I've got a problem which I tried to solve all last night but no avail and I hope someone here can give me some ideas as to a fix.


Years ago, 2010 to be exact, I built a great hackintosh using ------- running Snow Leopard on a GA-EP45-UD3LR with 9800GT GPU. This machine was flawless for years and it was a real joy to use. I'm fixed on 10.6.8 and have no need to go any further, I'm finding Apple software (iphoto, itunes, mail, imovie) to be getting worse and I've got everything I want where I am.


However, the main drive went down a couple of months ago (after 9000 hours use) so I'd thought I'd replace it with a SSD. Ended up going with a 480Gb Crucial M500. I cloned the backup drive onto the SSD using CCC, reinstated the bootloader (Im still using something called Asere 1.1.9 that Going Bald gave me years ago, essentially Chameleon v2) and ran it up, amazed with the speed. However when I tried to rearrange my drive boot order in BIOS to put the SSD first I get either stuck in the POST screen or caught in a loop that goes (Splash, POST, Splash, POST, ad infinitum). I once built a Hackintosh for someone with a 2Tb and encountered the boot0 problem and changed the boot1h file and got through it. Searching for clues I thought that was what I was experiencing so did that fix. The machine went from hanging at POST to the reboot cycle as described.


I've now tried updating Chameleon, fiddling about with different boot1h's but to no avail. I'm pretty good at Hackintosh's but this boot loader stuff I don't really fully understand. So is this a 4k SSD problem or is it something else? The machine I use just by booting of the backup drive and then jumping over to the SSD so it's not life or death but I really want a machine that boots without needing 2 drives. Any one got any advice? Thanks.
 
Hi everyone


I've got a problem which I tried to solve all last night but no avail and I hope someone here can give me some ideas as to a fix.


Years ago, 2010 to be exact, I built a great hackintosh using ------- running Snow Leopard on a GA-EP45-UD3LR with 9800GT GPU. This machine was flawless for years and it was a real joy to use. I'm fixed on 10.6.8 and have no need to go any further, I'm finding Apple software (iphoto, itunes, mail, imovie) to be getting worse and I've got everything I want where I am.


However, the main drive went down a couple of months ago (after 9000 hours use) so I'd thought I'd replace it with a SSD. Ended up going with a 480Gb Crucial M500. I cloned the backup drive onto the SSD using CCC, reinstated the bootloader (Im still using something called Asere 1.1.9 that Going Bald gave me years ago, essentially Chameleon v2) and ran it up, amazed with the speed. However when I tried to rearrange my drive boot order in BIOS to put the SSD first I get either stuck in the POST screen or caught in a loop that goes (Splash, POST, Splash, POST, ad infinitum).
Any one got any advice? Thanks.
That Asere boot loader has been outdated for years.
I am currently booting my 10.6.8 with the Chimera boot loader from the latest MultiBeast for Snow Leopard. Try that one and see if it works for you. Just run the MultiBeast app and select only the Chimera loader under boot loaders and install it.
 
Hey Going Bald, thanks for the response

Just tried as you said, installing Chimera from MB 3.10.1. Changed the boot order and exactly the same situation. Splash, POST, reset, POST, etc etc.

Strange huh? Any other ideas about this?

Thanks

PS I've got a trim enabler installed - relevant?
 
Hey Going Bald, thanks for the response

Just tried as you said, installing Chimera from MB 3.10.1. Changed the boot order and exactly the same situation. Splash, POST, reset, POST, etc etc.

Strange huh? Any other ideas about this?

Thanks

PS I've got a trim enabler installed - relevant?
I doubt TRIM has anything to do with it.
How about you follow the rules and put your board/cpu/gpu, etc in your profile and or create a sig?
Can't diagnose problems without knowing hardware.

BTW, mrjanek booted me and banned me from his site - I complained too much about his inattention and allowing spammers to take it over, I guess. Not sure if PunkNugget ever goes back there either.
 
Ah sorry about that, have fixed a sig. I did put the mobo and GPU in the first post though.

Can't believe mrjanek did that to you - you were the best there! How ridiculous. Shame that ------ faded out.

Anyway, now you can see the whole spec do you have any ideas? You booting ok on SSD then?
 
Ah sorry about that, have fixed a sig. I did put the mobo and GPU in the first post though.

Can't believe mrjanek did that to you - you were the best there! How ridiculous. Shame that ------ faded out.

Anyway, now you can see the whole spec do you have any ideas? You booting ok on SSD then?

The EP45-UD3P works just fine with a SSD.

Let's narrow the problem down to just the SSD and Chimera if we can.
Take a blank USB drive and format it GUID/Mac OS.
Copy your DSDT to the desktop and run MultiBeast, selecting Quick start->User DSDT
click on build and in the box on the right select the USB drive and click install.
Disconnect everything but the SSD clone and boot with the USB.
Report results.
 
OK using a new 16GB stick I did the build using MB 3.10 (SL version) and using my DSDT. Installation went fine and looks normal.

Disconnected all the drives bar the SSD clone (the one that can boot the system) and installed USB stick.

System cannot move past splash screen and doesn't even start USB system! Keyboard unresponsive and mouse light not coming on.

Reconnected and everything back to usual to type this message. I'm surprised by this. What do you think?

{Just checking with CW and the version installed on my USB stick is Chimera 1.7 r1394}

Also just tried a different stick, exactly the same behaviour.
 
OK using a new 16GB stick I did the build using MB 3.10 (SL version) and using my DSDT. Installation went fine and looks normal.

Disconnected all the drives bar the SSD clone (the one that can boot the system) and installed USB stick.

System cannot move past splash screen and doesn't even start USB system! Keyboard unresponsive and mouse light not coming on.

Reconnected and everything back to usual to type this message. I'm surprised by this. What do you think?

{Just checking with CW and the version installed on my USB stick is Chimera 1.7 r1394}

Also just tried a different stick, exactly the same behaviour.

In BIOS under Integrated Peripherals make sure Legacy USB Storage Detect is enabled so the system sees USB drives during POST. Use the function hot key to select the USB as the boot device.

Also, somewhere there in the BIOS there is a switch to disable the Full Screen slpash and allow you to see the POST - you might want to do that so you can see what is going on behind the splash screen during POST.
 
BIOS already set to 'enable legacy support of USB memory storage"

Can't use the boot function key as the moment the drive goes on the USB system seems to lock and nothing works anymore. For a test I booted without the USB stick, went into the boot menu, selected USB-HDD and then attached the stick. As soon as the stick went on the keyboard became unresponsive. How is that even possible?

Many thanks for you help. :thumbup:

IMG_0609.jpg


Thought I had an idea for minute but it didn't work. I put the SSD on port0 and turned native mode on (SATA port 0-3 native mode). Didn't make any difference. It had always been disabled so I did wonder.
 
BIOS already set to 'enable legacy support of USB memory storage"

Can't use the boot function key as the moment the drive goes on the USB system seems to lock and nothing works anymore. For a test I booted without the USB stick, went into the boot menu, selected USB-HDD and then attached the stick. As soon as the stick went on the keyboard became unresponsive. How is that even possible?

Many thanks for you help. :thumbup:

View attachment 124966


Thought I had an idea for minute but it didn't work. I put the SSD on port0 and turned native mode on (SATA port 0-3 native mode). Didn't make any difference. It had always been disabled so I did wonder.
Do you have an old 512MB or 1GB flash drive somewhere? Possible problem is the flash is too large for the USB port controller to be able to handle. Get the smallest one you can find and try that. Gotta remember that hardware this old can't always use modern stuff. I have an old PNY 1 GB USB 1.0 flash drive I use for this purpose. It was top of the line best/biggest you could get in 2009! We've come a looooonnnnnggg way since then:mrgreen::lol:.

Native SATA mode is for IDE settings - enable it if you have IDE drives connected. Allows mix of SATA and IDE drives from the same controller.
 
Status
Not open for further replies.
Back
Top