I recently installed osx 10.5 using a prepatched dvd.
Everything works fine except 'time machine' The time machine application opens just fine, it all looks realy nice. But when I open de timemachine tab in the control panel it gives me an error;
"backup volume could not be found"
Ive tried several disks, both internal and external (usb). All formatted in osx journaled format.
I've restored permissions a million times now.
Any suggestions on how to fix this.
224 replies to this topic
#1
Posted 31 October 2007 - 09:09 AM
#2
Posted 31 October 2007 - 09:23 AM
Sounds like you need the moddified IONetworkingFamily.kext by ToH. Here it is...
http://www.megaupload.com/?d=HWVMONUU
After placing it it /System/Library/Extensions
sudo -s
*password*
rm -rf /System/Library/Extensions.mkext
chmod -R 755 /System/Library/Extensions/IONetworkingFamily.kext
chown -R root:wheel /System/Library/Extensions/IONetworkingFamily.kext
reboot, and keep your fingers crossed
HTH,
The Baron
http://www.megaupload.com/?d=HWVMONUU
After placing it it /System/Library/Extensions
sudo -s
*password*
rm -rf /System/Library/Extensions.mkext
chmod -R 755 /System/Library/Extensions/IONetworkingFamily.kext
chown -R root:wheel /System/Library/Extensions/IONetworkingFamily.kext
reboot, and keep your fingers crossed
HTH,
The Baron
#3
Posted 31 October 2007 - 09:41 AM
I hope it's that easy! Will try as soon as I get back home!!!
Any chance this wil result is boot failure?
#4
Posted 31 October 2007 - 09:52 AM
If you're worried move the old IONetworkingFamily.kext to /
If you have problems boot -s and move it back.
No problems here but YMMV, good luck.
If you have problems boot -s and move it back.
No problems here but YMMV, good luck.
#5
Posted 31 October 2007 - 09:55 AM
I used to run debian so moving file back and forward using singleusermode or terminals wont be an issue.
Thnx for the quick replies and clear howto's!!! very much appreciated!
edit: I can imagine more people having this problem. Sticky perhaps?
Thnx for the quick replies and clear howto's!!! very much appreciated!
edit: I can imagine more people having this problem. Sticky perhaps?
#6
Posted 31 October 2007 - 05:48 PM
the file appears to be unavailable at the moment. Is there any other link to it?
thnx
Edit: It works again!
thnx
Edit: It works again!
#7
Posted 31 October 2007 - 07:16 PM
works for me to thx
#8
Posted 01 November 2007 - 08:42 AM
<native language mode>
Toch handig he zo'n forum.
Weet jij trouwens een oplossing voor het niet afsluiten van je hackintosh in leo
</native language mode>
Toch handig he zo'n forum.
Weet jij trouwens een oplossing voor het niet afsluiten van je hackintosh in leo
</native language mode>
#9
Posted 03 November 2007 - 12:43 AM
Strange, this didn't fix the issue for me.
Any other options?
Any other options?
#10
Posted 03 November 2007 - 04:01 AM
Thanks Baron Fixed my problem of Time Machine too
#11
Posted 03 November 2007 - 07:02 AM
Applying this fix didn't get Time Machine to work, plus it stopped my ethernet from working. Had to un-apply the fix.
Any other ideas?
Any other ideas?
#12
Posted 05 November 2007 - 12:13 AM
Hi,
If you downloaded the kext using Safari, it has added an extended attribute to the file that will prevent the system from using it. This is new to 10.5 and is obviously an extended security measure. You can easily check this because there is an "@" symbol at the end of the permissions block on an ls : e.g., "drwxr-xr-x@ 10 root wheel 340 2 Nov 14:47 Contents"
The people who got this to work probably downloaded using Firefox.
You can see if there are extended attributes on a file using xattr. Here's a snippet:
bash-3.2# xattr IONetworkingFamily.kext/
com.apple.quarantine <=== not going to work with this!
And to fix this, run:
cd /System/Library/Extensions
xattr -d com.apple.quarantine IONetworkingFamily.kext
If that doesn't work, you may need to do this recursively if the component files and directories contain the same extended attribute. Thus:
cd /System/Library/Extensions
find IONetworkingFamily.kext -exec xattr -d com.apple.quarantine {} \;
This will take a minute. Ignore the "No such xattr: ..." warnings.
This may be relevant to many different 10.5 problems when files are downloaded using Safari.
I hope this helps.
Quelg
If you downloaded the kext using Safari, it has added an extended attribute to the file that will prevent the system from using it. This is new to 10.5 and is obviously an extended security measure. You can easily check this because there is an "@" symbol at the end of the permissions block on an ls : e.g., "drwxr-xr-x@ 10 root wheel 340 2 Nov 14:47 Contents"
The people who got this to work probably downloaded using Firefox.
You can see if there are extended attributes on a file using xattr. Here's a snippet:
bash-3.2# xattr IONetworkingFamily.kext/
com.apple.quarantine <=== not going to work with this!
And to fix this, run:
cd /System/Library/Extensions
xattr -d com.apple.quarantine IONetworkingFamily.kext
If that doesn't work, you may need to do this recursively if the component files and directories contain the same extended attribute. Thus:
cd /System/Library/Extensions
find IONetworkingFamily.kext -exec xattr -d com.apple.quarantine {} \;
This will take a minute. Ignore the "No such xattr: ..." warnings.
This may be relevant to many different 10.5 problems when files are downloaded using Safari.
I hope this helps.
Quelg
#13
Posted 05 November 2007 - 12:32 PM
Try quelgs's idea. It works.
Though instead of "xattr -d com.apple.quarantine IONetworkingFamily.kext" I used "xattr -d com.apple.quarantine /System/Library/Extensions/IONetworkingFamily.kext"
I did have to manually edit the Intel82XX driver inside the IONetworkingFamily.kext to include my Ethernet controller's device ID.
Though instead of "xattr -d com.apple.quarantine IONetworkingFamily.kext" I used "xattr -d com.apple.quarantine /System/Library/Extensions/IONetworkingFamily.kext"
I did have to manually edit the Intel82XX driver inside the IONetworkingFamily.kext to include my Ethernet controller's device ID.
#14
Posted 07 November 2007 - 02:19 AM
neikous, on Nov 6 2007, 12:59 AM, said:
Hmm, thanks for having me try more stuff but it still didn't work :-/
I can try it again but I am having pretty bad luck here.
Any other suggestions?
I can try it again but I am having pretty bad luck here.
Any other suggestions?
That's a shame you weren't able to get it to work. Mine worked fine after applying the IONetworking kext replacement (after xattr -d etc. because I downloaded using Safari).
Have you tried in TM options: change disk - NONE and then change disk - YOUR DISK?
Also, is your drive HFS+ formatted? I assume it must be otherwise you wouldn't see it as an option in the first place. Still - worth checking. Also check that the drive is GUID partitioned not MBR. I believe that causes problems in TM.
One final check: is your disk drive name anything fancy with special characters? There have been reports of problems if the name uses special characters. Perhaps worthwhile is to use diskutil to erase the drive, create a simple name like BACKUP and ensure HFS+ (Mac OS Extended - Journaled)
Check in diskutil that the drive has "owners enabled" at the bottom left of the information screen (I suspect TM will need this set, though I'm not sure).
Also, as a last resort, try creating a blank file called ".com.apple.timemachine.supported" in the root of the drive if it isn't already there.
Other than that, I'm out of ideas. It does sound like a problem with the IONetworking kext though. It might be worthwhile going through the whole process step by step again as sometimes a step has been missed and isn't noticed.
Quelg
#15
Posted 11 November 2007 - 07:44 PM
Hi,
I got another problem, T&M doesn't show any HD to backup at all!
For the rest all works fine on my p5B mobo.
I got the flat install.
Maybe som1 an idea?
I got another problem, T&M doesn't show any HD to backup at all!
For the rest all works fine on my p5B mobo.
I got the flat install.
Maybe som1 an idea?
#16
Posted 14 November 2007 - 08:36 AM
I had given up all hope with my BrazilMac install, which has been working well, except for Time Machine. Then I did this:
http://forum.insanel...hl=time machine
I dragged and dropped from another partition, repaired permissions as root using chown chmod in Terminal, deleted the extensions cache, and rebooted with the -f.
Time machine started to work on my Lacie USB drive. My ethernet stopped working. With some luck I can edit the IONetworkingFamily.kext to get it going again. At least my Airport was still working.
Can someone tell me what the -f boot option does?
http://forum.insanel...hl=time machine
I dragged and dropped from another partition, repaired permissions as root using chown chmod in Terminal, deleted the extensions cache, and rebooted with the -f.
Time machine started to work on my Lacie USB drive. My ethernet stopped working. With some luck I can edit the IONetworkingFamily.kext to get it going again. At least my Airport was still working.
Can someone tell me what the -f boot option does?
#17
Posted 18 November 2007 - 06:32 PM
Well I finally got my time machine working again. To do so i used this binary instead: http://rapidshare.co...-_581_.zip.html
Note that this is NOT the whole kext, just the binary. Just drop that in IONetworkingFamily.kext/Contents/MacOS and replace the old one. Chown/chmod and reboot with -f and time machine should work
Note that this is NOT the whole kext, just the binary. Just drop that in IONetworkingFamily.kext/Contents/MacOS and replace the old one. Chown/chmod and reboot with -f and time machine should work
#18
Posted 20 November 2007 - 12:56 PM
I finally got the time machine working by using the following patch:
http://rapidshare.co...-_581_.zip.html
It didn't work after the first reboot, I almost restored my IONetworkingFamily.kext as I did with many previous IONetworkingFamily patches. It worked when I rebooted for the second time.
I believe the UUID error prevents Time Machine from working. You can check if you still have UUID errors by
http://rapidshare.co...-_581_.zip.html
It didn't work after the first reboot, I almost restored my IONetworkingFamily.kext as I did with many previous IONetworkingFamily patches. It worked when I rebooted for the second time.
I believe the UUID error prevents Time Machine from working. You can check if you still have UUID errors by
grep UUID /var/log/system.log
#19
Posted 20 November 2007 - 03:51 PM
fishyeah, on Nov 20 2007, 12:56 PM, said:
I finally got the time machine working by using the following patch:
http://rapidshare.co...-_581_.zip.html
It didn't work after the first reboot, I almost restored my IONetworkingFamily.kext as I did with many previous IONetworkingFamily patches. It worked when I rebooted for the second time.
I believe the UUID error prevents Time Machine from working. You can check if you still have UUID errors by
http://rapidshare.co...-_581_.zip.html
It didn't work after the first reboot, I almost restored my IONetworkingFamily.kext as I did with many previous IONetworkingFamily patches. It worked when I rebooted for the second time.
I believe the UUID error prevents Time Machine from working. You can check if you still have UUID errors by
grep UUID /var/log/system.log
scannerfm77-leopards-acpi:~ scannerfm77leopard$ grep UUID /var/log/system.log Nov 20 00:29:31 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CE Nov 20 00:50:58 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CE Nov 20 00:57:04 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CE Nov 20 01:11:31 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CE Nov 20 08:29:15 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CE Nov 20 22:26:51 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CEAbove is my log. Is that mean something still wrong?
#20
Posted 20 November 2007 - 04:01 PM
scannerfm77, on Nov 20 2007, 03:51 PM, said:
scannerfm77-leopards-acpi:~ scannerfm77leopard$ grep UUID /var/log/system.log Nov 20 00:29:31 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CE Nov 20 00:50:58 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CE Nov 20 00:57:04 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CE Nov 20 01:11:31 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CE Nov 20 08:29:15 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CE Nov 20 22:26:51 localhost kernel[0]: Waiting for boot volume with UUID A9AF3639-B133-3172-BBD9-CCB488B6B8CEAbove is my log. Is that mean something still wrong?
If you don't get "_CFGetHostUUIDString: unable to determine UUID for host. Error: 35" in your log or when you run some terminal command, you should be alright and your time machine should work (try partition your TM drive with GUID scheme and reselect the drive for TM after done the patch).
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users



Sign In
Create Account








