Ticket Options
Question Details
TICKET ARCHIVE -> Deleted Kext Files Accidentally.
eliosusa - Jul 11, 2005 - 3:31 am
I forgot to mention I was in the man/man8 directory. Thanks.
Eliosusa
Eliosusa
macbri - Jul 11, 2005 - 3:49 am
Hi Eliosusa -
If you were in the /usr/share/man/man8 directory then you have nothing to worry about. These are simply man pages for the (slightly dated!) UNIX manual page system. If you were to type "man kextd" you'd see a manual page explaining what kextd is. In your case you'll just see "no manual entry for kextd" since the relevant man page is gone.
If you wish to see a list of relevant files, take a look at http://developer.apple.com/documenta...ence/ManPages/ which has all the man pages online. But as far as the running state of your system this won't affect you at all.
Hope this helps,
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
If you were in the /usr/share/man/man8 directory then you have nothing to worry about. These are simply man pages for the (slightly dated!) UNIX manual page system. If you were to type "man kextd" you'd see a manual page explaining what kextd is. In your case you'll just see "no manual entry for kextd" since the relevant man page is gone.
If you wish to see a list of relevant files, take a look at http://developer.apple.com/documenta...ence/ManPages/ which has all the man pages online. But as far as the running state of your system this won't affect you at all.
Hope this helps,
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
eliosusa - Jul 11, 2005 - 11:12 am
I appreciate your help but I forgot to tell you that also I have deleted kextd in usr/libexec before deleting the man pages. Thanks.
Emilio.
Emilio.
macbri - Jul 12, 2005 - 4:01 am
Hi Emilio -
ahh, ok that *does* change things somewhat
So 'kextd' is used to load kernel extensions when required. These are like extra bits of software that provide extra features - drivers for hardware, that kind of thing. Having said that, what's the state of your Mac at the moment? Is it not booting, do you have problems logging in, what symptoms do you see in other words? Have you left the machine running since this happened?
Let me know, and we'll get you back on track as soon as we can!
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
ahh, ok that *does* change things somewhat
So 'kextd' is used to load kernel extensions when required. These are like extra bits of software that provide extra features - drivers for hardware, that kind of thing. Having said that, what's the state of your Mac at the moment? Is it not booting, do you have problems logging in, what symptoms do you see in other words? Have you left the machine running since this happened?Let me know, and we'll get you back on track as soon as we can!
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
eliosusa - Jul 12, 2005 - 9:09 am
Thanks. It is booting partially. I can see the apple and the circle running then it froze with black screen and I can see the mouse arrow in the middle but NO KEYBOARD and NO MOUSE working that is it. Now I tried to click "T" when it starts and I can see the sign of the transfer.....therefore I think I can connect another mac to transfer files. Also the keyboard let me open the CD to try the restore disc like I said previously but I cannot select the hard disk (there is no selection) and therefore cannot continue. The disk utility gave me some errors (I have to reboot two times to introduce the disk since the keyboard works for few seconds). "Preparing installation" then I go (with the mouse working) to "select the language" then "Wecome to the Macosx installer" "important info" "license" "selection destination" I don't have the destination disk displayed (options is grey out).
Then I go to "Installer" "open Disk utility" and I can see my hard disk and the DVD (the restore) When I select the disk it says "Not mount" format HFS+ capacity 76.69GB then I go to "verify disk".......Checking HFS Plus volume- Checking Extends Overflow File - Checking Catalog file (these are all in black) then instead in RED: Overlapped extent allocation (file641843d) - Incorrect block count for file system.log (it should be 72 instead of 73) - Incorrect block count for file wtmp (it should be 28 instead of 29) - Overlapped extent allocation (file 563750d) - Overlapped extent allocation (file641827d).
Then in black: The volume Eliosusa HD needs to be repaired.
Verify completed.
Then I start "Repair Disk" and get the same results of above and NO REPAIR (eventhough it says "repair completed").
Thanks.
Eliosusa.
Eliosusa.
Then I go to "Installer" "open Disk utility" and I can see my hard disk and the DVD (the restore) When I select the disk it says "Not mount" format HFS+ capacity 76.69GB then I go to "verify disk".......Checking HFS Plus volume- Checking Extends Overflow File - Checking Catalog file (these are all in black) then instead in RED: Overlapped extent allocation (file641843d) - Incorrect block count for file system.log (it should be 72 instead of 73) - Incorrect block count for file wtmp (it should be 28 instead of 29) - Overlapped extent allocation (file 563750d) - Overlapped extent allocation (file641827d).
Then in black: The volume Eliosusa HD needs to be repaired.
Verify completed.
Then I start "Repair Disk" and get the same results of above and NO REPAIR (eventhough it says "repair completed").
Thanks.
Eliosusa.
Eliosusa.
eliosusa - Jul 13, 2005 - 11:15 am
I have also tried to connect it with "T" and it does not mount the hard disk.
Emilio.
Emilio.
macbri - Jul 13, 2005 - 2:44 pm
Hi Emilio -
There's more going on than missing your kextd - looks like your volume is corrupted and I'd usually ask you to reformat and re-install but let's see if we can get the machine running long enough for you to copy off files etc first. So try this: put in your Mac OS X install disk and boot off that (hold down C while booting). When it's up, see if you can copy /usr/libexec/kextd from your install disk to your hard disk. Then reboot and see if your system comes up.
- Brian
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
There's more going on than missing your kextd - looks like your volume is corrupted and I'd usually ask you to reformat and re-install but let's see if we can get the machine running long enough for you to copy off files etc first. So try this: put in your Mac OS X install disk and boot off that (hold down C while booting). When it's up, see if you can copy /usr/libexec/kextd from your install disk to your hard disk. Then reboot and see if your system comes up.
- Brian
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
eliosusa - Jul 13, 2005 - 4:05 pm
Brian thanks for the reply. Could you be more specific? I have inserted the restore disk and what I have is the installer coming up and ask me "language" and bla bla until I see the selection and there is no hard disk that I can select. How can I copy without command line? Thanks.
Emilio.
Emilio.
macbri - Jul 13, 2005 - 4:54 pm
Hi Emilio -
I'm working from the OS X 10.4 install disk so it may be a little different, but when the Installer is running, do you see a "Utilities" menu at the top of your screen? Under this see if there is a "Terminal" which would give us the command-line we need. At that point you could enter:
cp -p /usr/libexec/kextd /Volumes/Eliosusa\ HD/usr/libexec
(I think that's what your hard drive is called. But to find out where it's mounted you can type
mount
in the terminal program and it should tell you where it is).
Let me know how it goes!
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
I'm working from the OS X 10.4 install disk so it may be a little different, but when the Installer is running, do you see a "Utilities" menu at the top of your screen? Under this see if there is a "Terminal" which would give us the command-line we need. At that point you could enter:
cp -p /usr/libexec/kextd /Volumes/Eliosusa\ HD/usr/libexec
(I think that's what your hard drive is called. But to find out where it's mounted you can type
mount
in the terminal program and it should tell you where it is).
Let me know how it goes!
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
eliosusa - Jul 14, 2005 - 10:50 am
THe Terminal button is grey out. I went back and force in the installer windows and it is always grey out untill I stop at the selection window. I also went in the Disk utility again and found Mount option but it did not worked it says Disk unmount. Is there anyway to start in command line directly?
Thanks.
Eliosusa.
Thanks.
Eliosusa.
macbri - Jul 15, 2005 - 9:04 pm
Hi Emilio -
First off I should say that since your partition appears corrupted and Disk utility cannot fix it, I've heard that DiskWarrior (www.alsoft.com) can often fix the situation in cases like this. at close to $80 it might seem a bit pricey, but on the other hand how much is your data (and time to replace it) worth? However, before commiting to that let's make sure we've tried all we can first.
Ok, so can you tell from Disk Utility what partition your boot voume is on? For example, on my powerbook it's on /dev/disk0s9. To find this, select your volume in(NOT the hard disk itself but the partiton labelled "Eliosusa HD" I think in your case. Then select File->Get Info and look near the top of the info window that pops up for something called "Disk Identifier" or something like that. Once you have that write it down because we'll need that in a moment.
Ok, next put in your OS X Install CD and reboot your machine. As soon as you hear the "chime" hold down option until you see a blue screen with your hard drive and CD shown as buttons - it may take a minute or more for this to show up, then release the option key. Usually the hard disk appears first, followed by the CD. Anyway, click on the CD volume (OS X Install CD) and then click the right-arrow on the screen. IMMEDIATELY, hold-down Command-S (the command key is the apple key alongside the spacebar, hold that and the 'S' at the same time), and keep them held down until you see a black screen with white text start to appear, at which time you can let go the keys. Now we're booting off the CD in single-user mode, and you're ready to continue when you see a prompt like this:
-sh-2.05b#
NOTE: at this stage you have write access to everything on your drive, so be VERY careful with your commands - double-check everything you type before hitting Enter!
First let's see if we can get an idea how damaged your filesystem is:
fsck_hfs -fn /dev/disk0s9
(of course in your case it will be whatever disk identifier you wrote down a moment ago). See if the messages give any clues.
OK next step let's see if we can mount the filesystem:
mount -t hfs /dev/disk0s9 /Volumes (again substitute your disk idnetifier here)
Assuming all goes well you should be able to do:
ls /Volumes
... and see the top-level contents of your filesystem. Ok, assuming that goes well you can do:
cp -p /usr/libexec/kextd /Volumes/usr/libexec/kextd
sync
umount /Volumes
reboot
I hope this helps - let me know how it goes, writing down any errors you see along the way. Good luck!
- Brian
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
First off I should say that since your partition appears corrupted and Disk utility cannot fix it, I've heard that DiskWarrior (www.alsoft.com) can often fix the situation in cases like this. at close to $80 it might seem a bit pricey, but on the other hand how much is your data (and time to replace it) worth? However, before commiting to that let's make sure we've tried all we can first.
Ok, so can you tell from Disk Utility what partition your boot voume is on? For example, on my powerbook it's on /dev/disk0s9. To find this, select your volume in(NOT the hard disk itself but the partiton labelled "Eliosusa HD" I think in your case. Then select File->Get Info and look near the top of the info window that pops up for something called "Disk Identifier" or something like that. Once you have that write it down because we'll need that in a moment.
Ok, next put in your OS X Install CD and reboot your machine. As soon as you hear the "chime" hold down option until you see a blue screen with your hard drive and CD shown as buttons - it may take a minute or more for this to show up, then release the option key. Usually the hard disk appears first, followed by the CD. Anyway, click on the CD volume (OS X Install CD) and then click the right-arrow on the screen. IMMEDIATELY, hold-down Command-S (the command key is the apple key alongside the spacebar, hold that and the 'S' at the same time), and keep them held down until you see a black screen with white text start to appear, at which time you can let go the keys. Now we're booting off the CD in single-user mode, and you're ready to continue when you see a prompt like this:
-sh-2.05b#
NOTE: at this stage you have write access to everything on your drive, so be VERY careful with your commands - double-check everything you type before hitting Enter!
First let's see if we can get an idea how damaged your filesystem is:
fsck_hfs -fn /dev/disk0s9
(of course in your case it will be whatever disk identifier you wrote down a moment ago). See if the messages give any clues.
OK next step let's see if we can mount the filesystem:
mount -t hfs /dev/disk0s9 /Volumes (again substitute your disk idnetifier here)
Assuming all goes well you should be able to do:
ls /Volumes
... and see the top-level contents of your filesystem. Ok, assuming that goes well you can do:
cp -p /usr/libexec/kextd /Volumes/usr/libexec/kextd
sync
umount /Volumes
reboot
I hope this helps - let me know how it goes, writing down any errors you see along the way. Good luck!
- Brian
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
eliosusa - Aug 16, 2005 - 12:44 am
Sorry to be late:
this is what I got: /sbin/mount_hfs: Invalid argument
The fsck returned the error was mention : Overlapped extent allocation (file 729338d)....etc and then The volume Eliosusa HD needs to be repaired. Thanks.
Emilio.
this is what I got: /sbin/mount_hfs: Invalid argument
The fsck returned the error was mention : Overlapped extent allocation (file 729338d)....etc and then The volume Eliosusa HD needs to be repaired. Thanks.
Emilio.
macbri - Aug 16, 2005 - 1:02 am
Hi Emilio -
It does look as though you might need a commercial product like Disk Warrior to repair you hard drive. I found the following thread on macosxhints.com: http://www.macosxhints.com/article.php?story=2003030211331230 which seems to recommend a commercial solution like DiskWarrior although there is some mention of the following trick possibly working:
Make a list of each "Overlapped extent allocation" error you get. Specifically you need the file identifier. For each one (if there's a handful) you can run the following command:
find / -inum 729338
(using the numbers listed in the errors)... and see if it's a valuable file and if not, delete it. Depending on how many errors you see this may well be more trouble than it's worth, so you can decide for yourself whether to try or not.
- Brian
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
It does look as though you might need a commercial product like Disk Warrior to repair you hard drive. I found the following thread on macosxhints.com: http://www.macosxhints.com/article.php?story=2003030211331230 which seems to recommend a commercial solution like DiskWarrior although there is some mention of the following trick possibly working:
Make a list of each "Overlapped extent allocation" error you get. Specifically you need the file identifier. For each one (if there's a handful) you can run the following command:
find / -inum 729338
(using the numbers listed in the errors)... and see if it's a valuable file and if not, delete it. Depending on how many errors you see this may well be more trouble than it's worth, so you can decide for yourself whether to try or not.
- Brian
--------
Brian S.
MacOSX.com Technical Support
brian@macosx.com
IF THIS IS YOUR QUESTION AND YOU WISH TO RESPOND, LOGIN HERE FIRST.
