Time Machine corrupted?

When I turn Time Machine on, and I have to choose a backup disk, I can see my Time Capsule, but I thought I used to have an option for "none." Now I don't have that option, and my Time Capsule has not been working since I last recall seeing it. I have a MacBook Pro that backs up without a problem to the Time Capsule, so I think the problem must be with Time Machine on my iMac. Any thoughts?

OK, thanks for the info.
We can try a series of steps to see if that will solve your issue. If it doesn't, I recommend that you contact Apple directly. Keep a record of the steps to help in the diagnoses.
On your iMac:
Open System Preferences (gear icon) on the dock and click on Sharing
Make sure that your computer name appears here. Do not exceed 27 characters including spaces for the name.
Open Hard Drive > Applications > Utilities > Disk Utility
Click on the name of your hard drive on the left side of the pane with exactly the same name as the hard drive on your desktop. If you have not renamed it, it will be called Macintosh HD
Click Repair Disk Permissions on the right side of the window
This operation will take 30-45 minutes on average. Just let it run until complete. You will get a message when it is done.
Close Disk Utility
Open Hard Drive > Library > Preferences
Locate the "com.apple.TimeMachine.plist file and delete it.
Restart your computer
Click System Preferences (gear icon) on the dock and then click Time Machine to setup the application again.
Please post back on your results

Similar Messages

  • I've lost my photos (crashed hdd, iPhoto library on Time Machine corrupt too).  Is there a way to create a picture from the thumbnail that remains in iPhoto?  The quality is obviously poor, but better than nothing.

    I've lost my photos (crashed hdd, iPhoto library on Time Machine corrupt too).  Is there a way to create a picture from the thumbnail that remains in iPhoto?  The quality is obviously poor, but better than nothing.

    Time machine should have a good copy - how are you determining that it is corrupt
    If you want the thumbnails as photos right click on the iPhoto library and make a copy of the data folder and then import it into a new iPhoto library - it contains your thumbnails
    LN

  • Very frequent Time Machine corruption since I upgraded to Mountain Lion

    Since I upgraded to Mountain Lion, I encounter very frequent Time Machine corruption.
    A few backups are OK, and then, I get an error "Time Machine has verified your backups and needs to create a new copy in order to enhance fiability...".
    In the console, I can see a lot of these errors :
    29/07/12 11:10:33,384 com.apple.backupd[17480]: Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 "The file “objects.xib” couldn’t be opened." UserInfo=..... {NSURL=file://localhost/Volumes/Copies%20de%20sauvegarde%20Time%20machine/Backu ps.backupdb/...objects.xib, NSFilePath=/Volumes/Copies de sauvegarde Time machine/Backups.backupdb/....objects.xib, NSUnderlyingError=... "The operation couldn’t be completed. Input/output error"}
    29/07/12 11:37:53,834 com.apple.backupd[17758]: Error: (-5000) SrcErr:NO Copying /Applications/VLC.app/...
    29/07/12 11:47:52,633 com.apple.backupd[17758]: Error: (-43) SrcErr:NO Copying /Applications to /Volumes/Copies de sauvegarde Time machine/Backups.backupdb/...
    Everything has been working perfectly well on OSX Lion for months...
    I already have reselected my Time Machine volume, and already have accepted a full new backup (3 times !) and it always finish like this...
    Any idea ?

    I had the same general problem: every few minutes I would get the message "There was a problem connecting to the server 'myserver'. Contact your system administrator for more information."
    The problem went away for me when I reset the sync server.
    http://support.apple.com/kb/TS1627
    I hope this works for others as well.

  • Time Machine corrupted iPhoto library? Help!

    Hi,
    I need some advice. It appears that I have lost thousands of photos. I know that's not true cos I have a Time Machine backup, but I want to run my situation past you before trying to recover my library. You see, I had a Time Machine backup error. Actually, scratch that, I had a problem with iPhoto not showing some particular photos. They showed up as just a dotted outline, yet when I chose 'show original file' or clicked to edit the photo, it appeared. So, the photos were there, but the thumbnails had a problem.
    After some time spent searching for a fix, I started iPhoto with the command and option keys pressed and chose all options to rebuild iPhoto. This looked like it was gonna take some time (I have over 4500 photos) so I left it alone and went to bed. In the morning, iPhoto appeared to be fixed but Time Machine had reported an error while backing up. I clicked ok, did a new backup by clicking 'backup now' which worked fine and carried on as usual.
    I've used iPhoto some more today and then, this evening, another TM backup failed. I tried again, and it failed again. I searched the internet to figure out why and discovered how to view the log file. This reported this: Jun 19 21:22:59 lee-webbs-intel-imac /System/Library/CoreServices/backupd[10907]: Error: (-8062) SrcErr:NO Copying /Users/leewebb/Pictures/iPhoto Library/Library6.iPhoto to /Volumes/Time Machine Backup/Backups.backupdb/Lee Webb’s intel iMac/2010-06-19-210546.inProgress/5A645817-7095-47FC-A658-A447B5A5814C/mac hd/Users/leewebb/Pictures/iPhoto Library
    Jun 19 21:23:46 lee-webbs-intel-imac /System/Library/CoreServices/backupd[10907]: Copied 1656 files (294.5 MB) from volume mac hd.
    Jun 19 21:23:46 lee-webbs-intel-imac /System/Library/CoreServices/backupd[10907]: Copy stage failed with error:11
    Jun 19 21:24:17 lee-webbs-intel-imac /System/Library/CoreServices/backupd[10907]: Backup failed with error: 11
    So, something seems to be wrong with the iPhoto library. I reckon that the rebuild process was somehow interrupted/corrupted by a TM backup. Following some instructions I found in C3 here: http://discussions.apple.com/thread.jspa?threadID=2057525 I ran a verify on my TM backup drive. This returned with OK. I then excluded my iPhoto library from my backup and ran the backup again. It worked fine, which would confirm that the iPhoto library is indeed the problem. Good. Ok. So, that's where I am now. Except it isn't. When I now start up iPhoto, my library has shrunk down to 748 photos! Eeek! What's happened, and what can I do about it? In iPhoto, those 748 photos add up to 1.4gb yet the iPhoto library file is still 12.87gb.
    Please can you help me.
    I just want to make sure I do the right thing instead of panicking. I've switched off my TM backup for now.
    Many thanks,
    Lee

    Hi,
    I need some advice. It appears that I have lost thousands of photos. I know that's not true cos I have a Time Machine backup, but I want to run my situation past you before trying to recover my library. You see, I had a Time Machine backup error. Actually, scratch that, I had a problem with iPhoto not showing some particular photos. They showed up as just a dotted outline, yet when I chose 'show original file' or clicked to edit the photo, it appeared. So, the photos were there, but the thumbnails had a problem.
    After some time spent searching for a fix, I started iPhoto with the command and option keys pressed and chose all options to rebuild iPhoto. This looked like it was gonna take some time (I have over 4500 photos) so I left it alone and went to bed. In the morning, iPhoto appeared to be fixed but Time Machine had reported an error while backing up. I clicked ok, did a new backup by clicking 'backup now' which worked fine and carried on as usual.
    I've used iPhoto some more today and then, this evening, another TM backup failed. I tried again, and it failed again. I searched the internet to figure out why and discovered how to view the log file. This reported this: Jun 19 21:22:59 lee-webbs-intel-imac /System/Library/CoreServices/backupd[10907]: Error: (-8062) SrcErr:NO Copying /Users/leewebb/Pictures/iPhoto Library/Library6.iPhoto to /Volumes/Time Machine Backup/Backups.backupdb/Lee Webb’s intel iMac/2010-06-19-210546.inProgress/5A645817-7095-47FC-A658-A447B5A5814C/mac hd/Users/leewebb/Pictures/iPhoto Library
    Jun 19 21:23:46 lee-webbs-intel-imac /System/Library/CoreServices/backupd[10907]: Copied 1656 files (294.5 MB) from volume mac hd.
    Jun 19 21:23:46 lee-webbs-intel-imac /System/Library/CoreServices/backupd[10907]: Copy stage failed with error:11
    Jun 19 21:24:17 lee-webbs-intel-imac /System/Library/CoreServices/backupd[10907]: Backup failed with error: 11
    So, something seems to be wrong with the iPhoto library. I reckon that the rebuild process was somehow interrupted/corrupted by a TM backup. Following some instructions I found in C3 here: http://discussions.apple.com/thread.jspa?threadID=2057525 I ran a verify on my TM backup drive. This returned with OK. I then excluded my iPhoto library from my backup and ran the backup again. It worked fine, which would confirm that the iPhoto library is indeed the problem. Good. Ok. So, that's where I am now. Except it isn't. When I now start up iPhoto, my library has shrunk down to 748 photos! Eeek! What's happened, and what can I do about it? In iPhoto, those 748 photos add up to 1.4gb yet the iPhoto library file is still 12.87gb.
    Please can you help me.
    I just want to make sure I do the right thing instead of panicking. I've switched off my TM backup for now.
    Many thanks,
    Lee

  • Time Machine corrupting external USB hard drives

    In February I installed two Mac Minis running 10.8 Server. Each machine had an external hard drive connected to it.
    Sometime over the Labor Day weekend, both drives stopped working. When I came in Tuesday, each machine had a message on the screen that the Time Machine drive had been improperly ejected. I powered down both drives and then powered them back up. Here's what is going on with each machine:
    MACHINE #1:
    Has a Western Digital 1TB drive formatted as OS X Extended Journaled.
    Disk Utility is able to see the external drive; however, whenever I try to back up, I get the message "Time Machine couldn't complete the backup... Files can't be copied onto the backup disk because it appears to be read-only."
    In Disk Utility, if I select the partition and Verify Disk, I get the message "Disk Utility stopped verifying Backup. Couldn't unmount disk."
    When I try to reformat the drive, I get the message "Disk Erase failed. Disk Erase failed with the error: Couldn't unmount disk."
    The Time Machine System Preference pane shows "None" for both oldest and latest backup times; however, I am able to enter Time Machine and see files going back to April.
    MACHINE #2
    Has a Segate 2TB drive formatted as OX X Extended Journaled.
    Initially Disk Utility would recognize this drive about 50% of the time. I would power it down and back up. Sometimes it would appear in Disk Utility, sometimes it wouldn't. Whenever I would try to verify or repair this disk, it would immediately unmount and I would get the message that the disk was not ejected properly. When I try to backup using Time Machine, TM acts like it is preparing to back up and then the disk disappears from Disk Utility and from the Desktop and I get the message that The disk was not ejected properly.
    This machine showed it was last backed up on September 1.
    After fiddling with it, I was able to format the drive. After formatting the drive, I started a Time Machine backup and the drive unmounted again.
    It seems that some event over the weekend caused both drives to corrupt. There was no sign of a power-outtage. Can anyone suggest how I can track down what caused this? Would there have been a maintenance script that would have run on Sept 1 that could have messed both drives up? Some other system event? Losing the data isn't a big deal. I just want to make sure I prevent whatever caused this in the future. Any tips would be much appreciated.

    Yeah, I don't know much about the logs. I flipped through some using Console but didn't really know what I was looking for. I was hopeing to see an event that was followed by a notice that the USB drives had been improperly ejected since that was a message I received on both machines.
    Since both machines were affected at the same time it seems logical it would be a scheduled event or, as you suggested, some power issue.

  • Time machine corrupted sparsebundle? how to repair? time machine restore not working

    On my macbook pro, after starting with Cmd-R, I erased the hard disk, re-installed Mavericks and I want to restore my back up with Time Machine. I select the NAS where the backup is, it sees the backup file but it says: "There is a problem with this backup and it can't be restored". I also copied the backup file (with extension sparsebundle) to another external hard disk and tried to use it from there but I have the same problem. With my iMac (as the laptop is not usable since I started it with cmd-R), when I double click on the backup file (ext sparsebundle), it mounts and I can actually see and access the files that are there. I do not understand why the restore is not working with the Time Machine. It seems the sparsebundle is corrupted. I tried these instructions: http://www.garth.org/archives/2011,08,27,169,fix-time-machine-sparsebundle-nas-b ased-backup-errors.html
    But I am stuck at this step: tail -f /var/log/fsck_hfs.log
    iMac-6:~ root# tail -f /var/log/fsck_hfs.log
    /dev/rdisk3s2: ** Checking Journaled HFS Plus volume.
    /dev/rdisk3s2: ** Detected a case-sensitive volume.
    /dev/rdisk3s2:    The volume name is Time Machine Backups
    /dev/rdisk3s2: ** Checking extents overflow file.
    /dev/rdisk3s2: ** Checking catalog file.
    /dev/rdisk3s2:    Invalid key length
    /dev/rdisk3s2: (4, 57529)
    /dev/rdisk3s2: ** The volume Time Machine Backups could not be verified completely.
    Nothing seems to happen even after a few hours (like 3 hours). The sparsebundle bakcup file is about 200 GB big. It does not seem to do anything as I do not notice any disk activity.
    Could someone please advise how to do the restore with the Time Machine or how I can repair the backup file?

    Well, if Time Machine is the only thing on that hard drive and there is only one partition, sooner or later, Time Machine will fill up the entire thing and you can't use it for anything else.
    Now, you can start over, but that will mean that your Time machine backups will be wiped out. If that is what you want, it is a rather easy process easily accomplished in Disk Utility:
    With hard drive connected, open Disk Utility (Applications -> Utilities). Highlight the Time Machine hard drive (the top entry for it). Click on the Partition tab. In the window, pick 2 partitions under the "volume scheme" and then slide the little thing at the bottom to adjust the size of each partition. Make sure the format is Mac OS Extended (Journaled) and, under options, click the GUID partition scheme. Name each one (i.e. "Time Machine" and "backups") and click "apply". Disk Utility will first erase the drive and then create 2 partitions (2 totally separate drives so to speak). You're done.....
    You can then set up the one for Time Machine and the other to drag over whatever files you want.

  • Why Does Time Machine Corrupt Files It Restores?

    Time Machine does not restore MS Word files and documents correctly. In the case of a play I am writing, the formatting is completely off and there are unusual symbols appearing which are not in the original document. In trying to restore FileMaker files and documents, I found that I cannot even open the document. A window displaying the title appears and that is all. This renders Time Machine useless.

    The reason is that it has corrupted itself.
    See http://pondini.org/TM/C13.html
    TM over wireless and with Yosemite.. is corruption in a box.
    I did not need to do this with the previous Time Capsule.
    I think it is more the OS at issue than the TC.. but certainly poor setup of the TC matters.. you have to have very good wireless connection single hop.. no double repeater stuff. Anytime TM stops or fails half way through a backup it is likely to corrupt itself.

  • What to do if Time machine corrupted.

    This is not a question, but thought I'd post my story to possibly help anyone else who might encounter a similar issue.
    Let me start by saying that I installed Leopard this past weekend and have had only noticed one issue ( I've noticed that if you fail to eject a dmg before deleting the dmg file, sometimes you can then only eject the dmg through Disk Utility or by restarting ). I did a clean install but left my old windows partition on my HD for use with Bootcamp ( updating the drivers after 10.5 install ).
    What happened to me was, I was installing some freeware games I had downloaded from the Mac OS X download site. While trying out one of the games, it had entered full screen mode and i couldn't figure out how to exit the game so I had to manually shut down my iMac using the power button. Well, this must have messed with some of the system settings, possibly corrupting something in TM's files, because the next time TM tried to do a backup, it just got stuck on "processing" forever. I tried several times to tell TM to do a Backup manually, with the same result each time. Luckily for me, since I have only been using 10.5 for a short while, the previous TM backups contained nothing crucial, so all I wanted to do was somehow start from scratch with Time Machine. I looked around but couldn't find instructions on exactly how to do that, but here;'s what I figured out through trial and error.
    1) Turn off Time Machine from Preferences
    2) Through Disk Utility, reformat/partition the external drive making sure to do so as Mac Extended ( Journaled ), leaving off the OS 9 disk drivers and making sure to use GUID partition table. I also changed the name of the volume just to make sure TM would not be confused at all.
    3) Return to System Preferences TM pane and click "change disk"
    4) Select the new destination volume
    Time machine did a brand new first backup, thus starting over.
    All is well.

    Thanks for your reply.
    I checked the exclusion list: The only thing listed is my Time Machine backup drive, so that shouldn't be it. But I hadn't checked that!
    What's interesting is that if you get info on both of my eSATA volumes, they have 250.15GB and 242.81GB used. Then, getting info on my Time Machine backup drive shows that there is 543.04GB used. So it seems that it's actually backing the stuff up.
    The drives are all formatted OS Extended (Journaled).
    We'll definitely keep Retrospect up and running. It works very well, it's just not as 'cool' as Time Machine.
    Message was edited by: QP Graphics

  • MAJOR TM Bug found in 10.6.1! Time Machine corrupts HFS+ Filesystem! Raid 0

    Hey there,
    i guess i just found a major bug in 10.6.1 and Time Machine which will corrupt the whole Partion which was selected for the Time Machine Backup.
    This is what i got here atm:
    2x Western Digital MyBook Mirror Ed. (ext. 2TB Raid0 HDD (2x1TB))
    1x Mac Pro running 10.6.1
    1x Macbook Pro running 10.6.1
    1x Mac Mini running 10.5.8
    Ok here we go:
    I just updated to Snow Leopard a few weeks ago and wondered why my always working WD MyBook was not working as a Time Machine Backup Partition anymore.
    Everytime i started a backup it failed after 10 gig or so. After reading all over the troubleshooting and this forum i am a 100% sure that this is not a usually bug like not formatting the hard drive to GUID Mode or so.
    Well... i tried the second MyBook.. same result on both Macs running 10.6.1
    Now i got suspicious and opened the MyBook in order to put those 2 HDDs in my Mac Pro and built a 2TB Raid0 via OSX.
    Guess what? Same result when running Time Machine! Running Time Machine on a single 1 TB HDD was working perfectly fine.
    No i just remebered that there was a Mac Mini hooked up to my TV that was still running 10.5.8 just because of Plex... Hooked up BOTH MyBook Mirror Editions and both worked perfectly fine!
    Now where can i report this error? I have no doubt that Time Machine on 10.6.1 is corrupting the HFS+ Filesystem when the partition is a RAID 0 Partition.
    Please let me know what you think and where i can report this bug. Anyone knows if this one is already fixed in 10.6.2?
    Thanks!
    André

    Yeah i did check the firmware updates for both mirror editions. Both are up to date. What botheres me is that they are not working aswell when they are out of their enclosure and directly built in to the mac pro. Can this really be a firmware issue then?
    From what I've read on repair/recovery sites, WD does put some of their firmware on a special part of the drive's platter itself. So it's still possible to have instructions on the actual disk that can create a problem. I do not know if this is causing your issue, it's just something I became aware of when shooting trouble on some MyBook/Mac issues. There are some WD enhancements to power management that may be problematic for Time Machine. I don't really know the whole story, just relaying what I've read.
    It's also possible that 10.6.2 (in beta) will help with an issue like yours. In our machines we've been using Hitachi and Seagate and the occasion Samsung drives for the last few years. Our external closures come from OWC and we haven't had any of the firmware issues that happened with the Leopard release and WD and now maybe the SL release.
    The only way I would be able to point a finger right now would be to swap in a couple of other drives and see how they work. Right now it doesn't matter who's at fault, Apple or WD. The drives don't work. If it's a problem with your installation you may be able to determine that by doing the above tests. If it's a problem with Apple's drivers there may not be a repair possible or a future update will be required. The same goes for the WD drives.
    Sidenote: For our own network, we have decided to do away with Leopard Server on an old Dual G4 1.42 tower and use our new ReadyNAS drive from Netgear. It's already working perfectly with Time Machine for several computers, file storage for PC/Mac/Linux, torrent download machine, basic web server, etc. We've put in 4 1TB drives and got 2.7TB of redundant hot swap raid. We'll replace the 1TB drives with 2TB drives, one at a time (although the available space won't increase until all 4 drives are swapped in), while the NAS is online, to increase our storage as required and the drives come down in price.
    We decided that if the data is important then a striped 2 drive volume isn't safe enough. We would have needed to mirror the drives and loose half the space and still have to keep the old server online.
    I'll watch this thread for information from others. I don't have the drives you are using to test with.

  • Time Machine corrupting file system

    I've been using Time Machine on an external hard drive for a long time with success. Recently the volume got corrupted and I could not repair it from disk utility. After formatting the drive I did backups for a few more days and it happened again. I used diagnostic tools from the disk manufacturer and they did not indicate any physical failure in the equipment.
    Has anyone had a similar experience?
    Thanks in advance!

    That misbehavior is typical of a failing disk, diagnostics or not.  Replace it.

  • Time Machine Corrupted (every 3-8 days)

    Hi,
    I have a Synology NAS (DS212+) and I one hard drive for my time Machines backup and as you know it takes days to backup all your PCs with time Machine and after few days I get this message :
    It's all ready the 3rd times it doing it and restarting the time machine from scratch, very frustrating.
    I'm not sure if it's a fault from DSM 4.0-2228 (latest version) or Mac OS X 10.7.4
    Does anyone experience the same issue ? Any solutions?  :cry:

    Hi, the error message is “Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you.”
    Thank you very much your link took me to the Apple Supports page : http://support.apple.com/kb/HT4076?viewlocale=en_US&locale=en_US
    I will try it out and hopefully that will fix the issue.
    Thanks

  • Time machine corrupts mountain lion

    after upgrading to mountain lion using time machine to install my itunes , photos etc ML refused to open and all i got was a no entry sign .
    i was also unable to do a safe boot . so eventually i resorted to a clean install of ML then used migration assistant to get all my files across and this caused the same problem .so i installed ML again and tried just putting my apps back on and the same happened .
    i now have ML up and running properly but all my photos and about 1500 albums from my itunes stuck on my external hd . is there anything obvious that could be causing this as i dont want to try loading them again just to have to spend 4 hours re-installing ML again ?

    TechCoach007 wrote:
    I can't get Time Machine to run after upgrading to Mountain Lion.  I even reformatted the drive using the drive utility in the utilities folder.
    I also tested the drive for errors and the disk utility indicates that it is OK.  Time Machine runs until it backs up approximately 5GB of data and then fails.
    Has anyone else experienced this problem.  I am using an Iomege Mac Companion 2Tb drive.
    I'm having trouble having Time Machine to work in ML.  I have a Time Capsule (1 TB), which until the upgrade was working fine.  It even worked great with a little hack, TimeMachineEditor, to change the frequency of the back ups.  I turned that off, just in case it wasn't ML compatible, still doesn't seem to be working properly.  I don't want to erase that Time Capsule, not at least I'm comfortable with ML.
    I thought I'd post this here in this thread since it is related - of sorts.  I will check out the troubleshooting link to see if it has any help.
    Tom

  • Time machine corrupts all old back ups

    This is possibly the straw the breaks the camels back!
    We had issues with smb in Lion almost causing a complete a complete breakdown in our rendering at the studio, now we have a complete and utter failure of time machine in Mavericks!!!
    We had 4tb free on the back up 8tb thunderbolt drive with a small back up of 40gb needed after installing Mavericks. The back up failed stating not enough disk space avaialble as 4.2tb was needed!!!
    I can only assume after upgrade mavericks decided to back up the entire disk again, it failed and has now deleted all old data.
    In this case luckily we didn't actually lose any critical data as this is backing up a raid 5 drive as a secondary line of safety.
    That said this a getting very worrying, every update from Apple in the last 4 years has caused us one issue or another. We are getting to the point where we simply can't trust Apple with Enterprise level support or relaibilty.
    I can only assume from other cases on here this is a known issue but was realeased anyway?
    Think we are at the point where we simply won't upgrade any Apple products until 12 months after release, hopefully giving them time to iron out all the bugs. Which is not what I expect from Apple, and kind of ruins the point of why one might use Macs in the future.

    Can anyone suggest a more reliable back up software solution?

  • Time Machine Corrupts Backup Drive ...

    Well, maybe I was a little facetious with the title ....... that was just to attract you to click
    I have a 500gb LaCie Desktop Hard Drive. I use FW 800 to my Mac. I use the hard drive as a TM drive only, no other data is on it.
    I've had this problem several times recently.
    I erase the hard drive through disk utility. It is 100% empty. I go into TM, set it as the TM Drive, and it backs up my 250gb (50gb free) internal hard drive fully.
    It will TM properly about 7-10 times. After that, randomly, with nothing invoking it, i'll get a "this drive is read-only" error when TM is going about its business, and won't be able to further back up to the drive.
    There is plenty of extra space to back up. Doing an information (command + i) on the hard drive, expensing the privileges drop-down and unlocking the menu does not let me change the "read-only" drop down for any of the users.
    My thought was to go into Root and change it there, but I know when you start screwing around with root when something doesn't want to be done, things usually get messed up somewhere further down the line.
    Right now is not a busy time for me, so the TM backup isn't crucial, but I'd like to get it up and running again ASAP.
    Further Information: I am able to copy files to and from the hard drive. It is fully operational and connects to other computers as well.
    Repaired / verified disk permission on both internal and external already.
    Suggestions???

    sounds like it could be a problem with the drive itself. you should reformat it completely using the partition tab (NOT the erase tab) in DU. then back up again and see what happens. if the problem keeps coming back after that i would suspect a faulty drive.

  • How can I replace just the corrupt page(s) in the domain file of iWeb using Time Machine?

    I back up with Time Machine and have an extensive elaborate website I created in iWeb '09 over a couple months and publish to a local folder and then upload to my server, but in the last few days I notice certain pages (that I haven't even worked on or touched) somehow become corrupted or "cross-contaminated" with elements and images from other pages.  Once I see they are corrupt I make sure not to publish them (if the current published versions are the correct, non-corrupt versions) or if they did get published I can use Time Machine to retrieve the .html file and page files folder for that specific page and replace it in my published folder/server so it shows correctly on the Web.  However, that does not replace the corrupted page(s) you see and work with when you launch iWeb and try to edit or continue working on that page.
    I am confused as to how I go to the package contents of the domain file and replace just that page with a previous version from time machine.  I don't want to replace the entire domain file because I have new changes I made to other pages even in the past hours.  How can I keep the good pages and just get earlier, non-corrupted versions of the corrupt page(s)? I know it's not as easy as with the published site folder where you can just replace the page's .html file and folder, but I don't want to have to re-create the corrupted page(s) from scratch or have to replace it with the last non-corrupted domain file and then have to redo all my recent changes to new pages I made before discovering the corrupt page(s).  Thanks for your help as now I can't make changes to the page(s) within iWeb itself.

    Thanks for the response, Wyodor.  I don't know what that is, but I'll have a look.  Is it an alternative to iWeb or a way to transfer pre-existing iWeb sites?  When you say merge domain files, is that like so multiple copies of the same site show up then you can pick and choose the non-corrupted pages and group them then delete the corrupted ones?  I am on Snow Leopard with no plans or need to upgrade anytime soon.
    And yes, I will read your links but just wanted to ask those questions.  Maybe they'll answer my questions, maybe not.
    I was able to discern that within the domain file is a domain folder with all the site folders, each with their own page ".gz" files which expand into ".xml" files.  I was trying to figure out if you could simply drag the corrupt pages out that way and replace them with backup copies that are still good.  I am having trouble discerning which pages are which as they all have random names like site-page-30F175E3-AE33-4F10-A490-1A096D9B185B.xml and although I expanded and opened each in Text Wrangler, I still couldn't discern which were which for sure, and trial and error proved cumbersome.  Also, I did notice some of the later corrupted domain files had one or two more pages than the site itself has, so not sure how they got added or duplicated or what.
    Again, I'll look at your links, but do you know about swapping out individual page .xml files this way within the domain file?

Maybe you are looking for