Discuss 10v Will Not Boot. Please Help. at the Kernel / Kext (Driver) Support - Hackint0sh.org; I don't remember what guide I followed, but aroud this time last year, I made ...
10v Will Not Boot. Please Help.
I don't remember what guide I followed, but aroud this time last year, I made a dual-boot 10v hackintosh to run SL and W7. It worked great, and since it was a gift for my wife and she didn't actually want W7 (an oversight on my part) I never actually installed W7.
The book has worked pretty well for the last year-ish, occasionally encountering kernel panics up to twice a day, but usually no more often than every other day. No serious problems, and since it was working fine, no modifications were made to it. I disabled automatic updates because of the problems I kept hearing about support for the processor being removed by Apple in updates.
So yesterday, the computer was sitting on the dining table, as it had been all weekend while we were gone on a camping trip. It was turned off, which is how we left it.
When my wife went to turn it on, she encountered this screen:
I pulled the drive from the computer and plugged it into my 10.5 MBP with a USB-SATA adapter, and I find no mountable volumes...which I think is actually due to the way the partitioning was done for the W7/SL dual-boot configuration, but I really don't remember.
What can I do to fix this? Do I need to go buy or borrow an 8GB USB drive and make it a bootable 10.6 and use the disk utility to repair it, or what?
I'm not sure where to go from here, and my wife is quite depressed at the sudden and confusing loss of her portal to the WWW and document-forging.
I searched on Google and various forums and found a strange lack of any similar issues...could the hard drive be boned? Is this as bad as it could be, or is it better than I'm thinking it is? Yes that question was intentionally confusing.
Please advise me what steps to take next. I'm not sure what to do from this point.
Last edited by Dash_Merc; 08-11-2010 at 09:39 PM.
Try to boot with -x -v for verbose output.
See how far it goes, and if it's actually able to read your hdd/volume/content through the booting process.
I don't see any way to enter commandline arguments. How do I "boot with -x -v for verbose output?"
The only thing I get at all when pressing keys during boot is a grey menu similar to BootCamp's that allows me to select the Windows partition or the Macintosh HD partition. Is there some key combination I should be using to access a commandline before or during boot?
Wow, I just noticed that little CLI at the bottom of the BootCamp-esque screen. I did not see that before. So I just:
and it might fix everything?
Nevermind, I read the included instructions by typing "?"
And it spewed a whole bunch of black text on a grey screen, listing every .kext file on the computer, and then a black screen with white text showed up and kept going until:
mach_kernel -x -v "Graphics Mode"="1024x576x32"
...which means what, precisely? If it means waiting for the partition to boot...then maybe I'm boned...but maybe it's waiting for the USB root?
Apple PS2Trackpad: Using peak detection method
Still waiting for root device
Still waiting for root device
Still waiting for root device
Last edited by Dash_Merc; 08-11-2010 at 11:33 PM.
1. It seems your hard drive still ok (for the most part) as SL still able to read and process the booting sequences.
Originally Posted by Dash_Merc
2. Don't enter too many boot arguments/options as you don't know what kernel and video mode your SL was/is running. And if you're asking for what it does not have then thing isn't pretty.
3. Try option -x -v -f which means booting in safe mode, clearing all previous caches and giving verbose output.
4. Waiting for root... error means SL is having problem accessing your hdd due to corrupted/missing driver/kext for hdd/controller or operating mode change. Check your BIOS setting to see if you have option under SATA/IDE to AHCI/normal or whatever it was running just in case something has changed BIOS settings.
I checked the BIOS, and there is no option to modify the SATA settings.
I ran boot: mach_kernel -x -v -f, and received the same output as before.
I'm making a new SL USB boot drive, and I'm going to try a permissions repair, and if nothing else, I'll copy the relevant data off the drive and reinstall from scratch (and then immediately follow any relevant instructions for updating to the newest supported updates...and make it only one partition since my wife doesn't need Windows 7).
Do you know what .kext files might be missing, in particular? If I can find them on the original drive using the boot drive, then perhaps I can replace them via drag and drop?
Oh noes! I made the boot drive and used NetBookBootMaker on it, and it results in a kernel panic because of "unsupported CPU."
Looks like I get to re-make the boot drive and try again...and if that doesn't work, I'll just accept that I'm screwed and try to figure out what other options I have for recovering data off a partition that is invisible to any other computer I plug it into.
I tried rerunning NetBookBootMaker (an older version; the one I used for the original install), and it seems to be booting now. I'll update with my success or failure in a bit.
I'm using Disk Utility to repair the original boot disk and see what it can do. No ETA. I'll just let it run while I work on other things (I *am* at work, after all), and see where it takes me. If I completely bone this, I don't suppose it's a big deal, provided I can get the volume to be recognised by my mac so I can copy the relevant data and start anew.
Disk Utility cannot repair the disk. I'm making a blank disk image on another non-boot drive I will have plugged in, and I'll fill it with the data I need to backup. I hope this will work.
I can't write to the boot drive. I should have seen that coming. I'm creating an image from my wife's user folder on another hard drive I plugged in with another USB-SATA adapter. Let's see if it works. The Macintosh HD volume doesn't mount automatically under Disk Utility on the boot disk. I have to explicitly tell it to mount the partition. I wish I could just open up Finder and just straight copy files from the bad partition, but I guess creating ./dmg files from folders on the bad partition is acceptable. I'd rather have the data in a less than optimal format than not at all.
Last edited by Dash_Merc; 08-12-2010 at 08:11 PM.
1. Does it need mach_kernel to boot? It may use legacy, atom, or mach kernel depends on how it was named even it's the atom kernel.
Originally Posted by Dash_Merc
2. As for reinstalling, make 2 partitions (the second could be small) and install one extra OSX to it for backup/repair/update purpose, just in case thing goes south then you always have something to boot up and repair the main OSX volume.
3. Those kexts that involved with the error would be all the *ATA*, AHCI, Jmicron kexts for hdd/controller.
4. Good luck with your data recovery.
Last edited by ratvn; 08-12-2010 at 09:36 PM.
I'm dumb for not typing the arguments by themselves...I just didn't think it would accept them alone. And reading the help led me to believe that I needed to include at least one of the other parts of the command besides just the argument (for example, the kernel, and/or the partition).
Installing two OS X partitions is a good idea. That way I won't have to deal with plugging in thousands of umbilical support cables to get done what needs to be done.
I can't actually browse the contents of the SL partition, so I don't think I'll be able to copy anything to/from anywhere to fix the kext problem. It's unfortunate, because being able to browse the contents would save me a buttload of time.
Thanks for the good wishes. The procedure is going well, and I am creating disk images from my wife's user folder and Applications folder on a blank partition in another drive. It is *very* time-consuming. Luckily I'll have a couple hours to let it finish at home while I play games or something, since my wife will be out and about with friends.
I must say I certainly regret configuring this for dual-booting. Having an entire partition be completely invisible to any computer it's connected to, except when I'm using the 10.6 install disk is really really stupid. I can't emphasize how entirely frustrating it is that I can't just plug in the drive and copy files from it. I don't care if it's not bootable, it should still be visible under 10.5, considering it uses the exact same file table format. There must be something worse wrong with it than just corrupted files if I can't even find the volume in the terminal...
I got tired of waiting, and I also realised the partition I was copying things to was WAY too small (but for some reason it didn't warn me -- I was copying 40-ish GB of data to a 15 GB partition...I didn't realise she had that much data to begin with). I looked around the web and was reminded of MacDrive, a program I almost never use but did purchase and install on my BootCamp partition. So I install the trial of MacDrive 8 on my work computer in a VM, and I have instant access to a partition that OS X and Disk Utility cannot see (unless I'm using the 10.6 install disc). Why? This makes absolutely zero cents to me.
I'm not complaining, though, because now I'm making a decent backup copy of the files I need and I'll be more readily-able to fix the situation. I just can't believe Disk Utility can't do something that MacDrive can. I have long regarded Disk Utility as the defacto standard when it came to awesomeness in partition manipulation and disk management.
Last edited by Dash_Merc; 08-12-2010 at 10:49 PM.
So how's this for random?
I finish copying the required files from the OS X partition to the Win partition, wrap up at work, and head home. When I plug the hackintosh drive into my mbp to copy the files off the Win partition onto another drive so I can reformat the hackintosh drive...and there are no partitions.
Needless to say, I freak out.
So I plug it back into the hackintosh and boot it up with the USB installer and look to make sure the partitions are still there. They are. So I remove it and plug it back into my mbp, and HOLY CRAP THE MAC PARTITION IS VISIBLE AND ACCESSIBLE! What the hell? I didn't even *do* anything! I just *looked* at it. And that, apparently, fixed it?
Well,I guess it's time to directly copy off as many files as I can now. I just hope this lasts, because I'm gonna have to finish this work tomorrow at work. Now it's time for dinner and some Star Trek with my wife.
By metronomadic in forum Dual Booting
Last Post: 02-16-2012, 09:33 AM
By XSaenen in forum Dual Booting
Last Post: 12-09-2011, 12:59 PM
By fieryrage in forum Installation
Last Post: 05-08-2010, 02:49 PM
By rich1210 in forum Dual Booting
Last Post: 05-02-2009, 05:07 PM
By juato4 in forum General
Last Post: 05-14-2008, 09:35 PM