View Full Version : [other] How to fix, please!
Officer Dibble
May 10th, 2008, 01:45 PM
Hi, can anyone tell me what's going on here, please?
This error (see attached image) is occurring in Leopard on a MacBook at boot up. I pressed Command 'S' to get this screen - otherwise it just stays grey after the boot chime and flicks between a 'no-entry' symbol and the Apple Logo rapidly.
Please help.
cyberdork33
May 10th, 2008, 01:53 PM
please use more descriptive thread titles...
Your system is unable to load the OSX kernel. I would say the file has become corrupted somehow. boot from the OSX disc and repair permissions.
Uinluan
May 10th, 2008, 02:00 PM
It would appear that your system may have crashed. I would recommend booting from your leopard install disk and trying to repair permissions to that drive and then boot from it to see if it comes up.
Officer Dibble
May 10th, 2008, 02:08 PM
Thanks for such a quick response... still need the the install disk though... grrr. :(
Uinluan
May 10th, 2008, 04:23 PM
If you have another Mac and a firewire you could put the machine that is having the problem in target mode by holding the T button down as it boots until you get the firewire icon floating around on the screen then plug that into your other mac it will show up as a mounted firewire drive. Open up disk utility on the good machine and run repair permission on the drive that has been mounted as a firewire drive from the other machine. Don't know if you have another Mac but that is another way to do it.
Officer Dibble
May 10th, 2008, 05:36 PM
If you have another Mac and a firewire you could put the machine that is having the problem in target mode by holding the T button down as it boots until you get the firewire icon floating around on the screen then plug that into your other mac it will show up as a mounted firewire drive. Open up disk utility on the good machine and run repair permission on the drive that has been mounted as a firewire drive from the other machine. Don't know if you have another Mac but that is another way to do it.
That's a brilliant idea, and a fantastic concept on the part of the peoploids at Apple.
As good as the Mac probably is, I don't know any other people that own one... otherwise I would have borrowed their disk by now.
Once again, a brilliant idea, many thanks. :)
cyberdork33
May 10th, 2008, 10:31 PM
yea basically mounting the disk in some system that is not running from the partition you need to fix will allow you to fix it... You might eeven be able to mount it in linux and fix it, but I am not sure what the permissions need to be... there is a thread in the mactel FAQ that shows how to do a filesystem check from linux, but honestly, I would recommend that method...
russo.mic
May 11th, 2008, 02:16 PM
yea basically mounting the disk in some system that is not running from the partition you need to fix will allow you to fix it... You might eeven be able to mount it in linux and fix it, but I am not sure what the permissions need to be... there is a thread in the mactel FAQ that shows how to do a filesystem check from linux, but honestly, I would recommend that method...
can you repair OS X permessions from Linux? I don't think that would work...
cyberdork33
May 11th, 2008, 11:08 PM
can you repair OS X permessions from Linux? I don't think that would work...
yes, should be able to. has to be writable though.
russo.mic
May 11th, 2008, 11:58 PM
Wow, just did it to see CD. Your right. you can change a file's permissions in linux, and they carry over to OS X. I would have thought that wouldn't work for some reason.
Learn something new everyday.
Russo
Officer Dibble
May 16th, 2008, 03:14 PM
It would appear that your system may have crashed. I would recommend booting from your leopard install disk and trying to repair permissions to that drive and then boot from it to see if it comes up.
Didn't work... still having the same problem... however, now that I have an Install Disk I can provide any logs necessary to hopefully resolve this. :)
Any further suggestions? :confused:
neorou
May 16th, 2008, 07:22 PM
OK. Just a long-shot, but have you tried zapping PRAM and maybe even clearing the NVRAM? Also, if you boot from the Ubuntu CD will it boot normally?
Officer Dibble
May 17th, 2008, 11:14 AM
OK. Just a long-shot, but have you tried zapping PRAM and maybe even clearing the NVRAM? Also, if you boot from the Ubuntu CD will it boot normally?
Yep, I've cleared PRAM and NVRAM, and Ubuntu LiveCD (8.04) will boot without issue.
As a result of booting into Ubuntu I found what could be an unusual boot configuration while checking things out with Gparted:
/dev/sda1 fat32 Size=200MB Used=18MB Unused=181MB boot
/dev/sda2 HFS+ Size=105.88MB Used=24.91GB Unused=80.97GB
Unallocated 128MB
/dev/sda3 fat32 Size=5.6GB Used=11.63MB Unused=5.58GB msftres
Does anything look unusual to you about this?
Journalling is enabled and I don't know how to disable this - so it's not allowing me to write to the HDD.
cyberdork33
May 17th, 2008, 12:16 PM
Does anything look unusual to you about this?No
If repairing the volume didn't work then I think you are going to have to take more drastic measures... like copying the kernel off your OSX DVD or restoring a backup or reinstalling.
See the "Advanced alternative" portion of this page for getting a new copy of the kernel:
http://docs.info.apple.com/article.html?artnum=106805
Officer Dibble
May 17th, 2008, 01:14 PM
If I wanted to reinstall Leopard with a view to dual booting with Ubuntu, would I be better completely wiping the drive, or would the installation disk do this for me?
You guys are really helpful, thanks for your advice in anticipation. :)
neorou
May 17th, 2008, 02:31 PM
Dibble,
If you have a Leopard DVD, I would definitely start with a complete zeroing of an HD using the Leopard DVD's disk utility. Then I would use disk utility to make my partitions first. I would also put the OS X HFS+ partition first - perhaps the Mach kernel looks for it in the partition serially as it boots after something goes wrong, and if the kernel encounters a non HFS+ partition (like the FAT32 that you had), it may not know what to do - thus the kernel panic.
I would use iREFit to manage the boot selection (http://refit.sourceforge.net/) along with Boot Camp.
Before installing iREFit or UBUNTU, I would definitely run all the Mac updates.
If after all of this you are still having errors, I would locate the hardware test cd for you mac and run it just to see if there are any hardware issues. Make sure you do the extended test. You may want to do this anyway to rule out any potential hardware issues. The cd is not perfect, but as a long time mac user, I would rather have it than not.
Best of luck.
blurg
May 17th, 2008, 06:48 PM
I would also put the OS X HFS+ partition first - perhaps the Mach kernel looks for it in the partition serially as it boots after something goes wrong, and if the kernel encounters a non HFS+ partition (like the FAT32 that you had), it may not know what to do - thus the kernel panic.
The 200MB FAT32 partition is his EFI partition, leave it alone if you're keeping OS X, it is supposed to be there.
cyberdork33
May 17th, 2008, 10:43 PM
The 200MB FAT32 partition is his EFI partition, leave it alone if you're keeping OS X, it is supposed to be there.
yes and you should be able to reinstall into the existing OSX partition without a problem though it may disable rEFIt untill you reinstall it.
russo.mic
May 18th, 2008, 04:56 AM
If your gonna reinstall OS X, I would partition from the get-go.
Create your partitons with the OS X Disk Utility during installation, and go from there.
Officer Dibble
May 18th, 2008, 03:05 PM
You guys are megastars, many thanks to you all. =D>
I'm going to work my way through this again now - will let you know how I get on. :)
vBulletin® v3.7.4, Copyright ©2000-2008, Jelsoft Enterprises Ltd.