Time Machine drive showing much smaller amount of data than on internal HDD.
I am helping a friend that has an iMac running 10.7.5 with a TM backup drive. External HDD is formatted as Extended Journaled Case Sensitive.( Default via TM grabbing the disk initially and setting it up.)
Both internal HDD and TM HDD have been verified in Disk Utility. TM drive shows the size of the backups.backups folder as 11GB and the internal drive has 320GB of data on it. No items were excluded from the TM backup as an option. Running a backup to TM is successful with no error messages.
Disk Permissions were repaired on the internal HDD but it is not an option for the TM HDD ( grayed out in DU) .
I tried the tips from this thread:
https://discussions.apple.com/message/19018287#19018287
about unchecking the ownership in the Get Info window for the TM drive but the checkbox is not available. I went thru Terminal to enable ownership on the drive and it appeared successful but still no ability to Repair Disk Permissions in Disk Utility.
Pondini has had GREAT advice on all things TM!!!!! What a fantastic resource for us all! This is the only backup of the data at this point. The friend is also having issues with a large iPhoto Library and before I option & boot iPhoto to repair library permissions etc, I want to know the TM HDD is truly functioning correctly.
Any thoughts?
It has failed. It says it requires 318 GB of space, which is ludicrous.
Feb 1 17:02:25 koishi /System/Library/CoreServices/backupd[7799]: Backup requested by user
Feb 1 17:02:25 koishi /System/Library/CoreServices/backupd[7799]: Starting standard backup
Feb 1 17:02:25 koishi /System/Library/CoreServices/backupd[7799]: Backing up to: /Volumes/kuhi/Backups.backupdb
Feb 1 17:02:25 koishi /System/Library/CoreServices/backupd[7799]: Ownership is disabled on the backup destination volume. Enabling.
Feb 1 17:02:25 koishi KernelEventAgent[37]: tid 00000000 received unknown event (256)
Feb 1 17:02:26 koishi /System/Library/CoreServices/backupd[7799]: Event store UUIDs don't match for volume: koishi
Feb 1 17:05:20 koishi login[7705]: DEAD_PROCESS: 7705 ttys001
Feb 1 17:07:49 koishi /System/Library/CoreServices/backupd[7799]: Backup content size: 292.1 GB excluded items size: 26.4 GB for volume koishi
Feb 1 17:07:49 koishi /System/Library/CoreServices/backupd[7799]: Starting pre-backup thinning: 318.79 GB requested (including padding), 297.64 GB available
Feb 1 17:07:49 koishi /System/Library/CoreServices/backupd[7799]: No expired backups exist - deleting oldest backups to make room
Feb 1 17:07:49 koishi /System/Library/CoreServices/backupd[7799]: Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
Feb 1 17:07:49 koishi /System/Library/CoreServices/backupd[7799]: Backup Failed: unable to free 318.79 GB needed space
Feb 1 17:07:54 koishi /System/Library/CoreServices/backupd[7799]: Backup failed with error: Not enough available disk space on the target volume.
I will now force a Spotlight re-indexing of my source drive.
d.
Similar Messages
-
Time machine always backs up same amount of data
When backing up with Time Machine it always backs up the same amount of data each time (140GB). I am not modifying 140GB of data each day or even each week so why does Time Machine always default to this amount of data?
I would like TM to only backup modified data so that I am not waiting hours for TM to complete backup. Looking for a reset or workaround for this issue.
Mac Pro 10.8See D4 in the 1st linked article.
Time Machine Troubleshooting
Time Machine Troubleshooting Problems -
Can I use a TIme Machine drive of my Macbook to transfer data to a new IMac
Hi everyone
I currently have a 2.6GHz Intel Core 2 Duo Macbook Pro as my main machine, using System 10.6.4.
I'm keen add a second computer which will allow me to run both systems at the same time.
My day job is a music producer, so I have plenty of audio programmes and plug ins, that are all intel spec and up to date, so I'm aware of tranferring new password codes etc to a new hard drive however I wondered if there were any potential issues transferring the data from my Macbook Pro and or it's Time Machine Drive to a new iMac ? I'm guessing not as they are both Intel Machines and will be running the same operating system, but any guidance to re-assure me would be greatfully received.
Many thanks in advance to any replies.
RobertI wouldn't use Migration Assistant for anything but to transfer your Home folder assuming you wanted to operate out of the same account on both machines. That's certainly the easiest approach. It's what i do between my Mac Pro and my MBP.
But Migration Assistant is not a tool for maintaining synchronization between two computers. For that you can either have the two computers on the same local network and sync them over the network with third-party software. Or you can maintain an external "common" backup that is used to keep the two computers up to date using third-party software.
My choice is the common backup on an external hard drive. I use a notebook sized drive because it's easy to take with me when I travel. I backup the most recently changed computer to the external drive. Then connect it to the other computer and do an incremental update. This keeps both computers in sync. You just need to remember which was the most recently changed computer.
If you have a local network, then when both computers are connected to the network you can enable File Sharing on one of the computers, then sync the two with third-party software.
Backup Software Recommendations
1. Retrospect Desktop (Commercial)
2. Synchronize! Pro X (Commercial)
3. Synk (Backup, Standard, or Pro)
4. Deja Vu (Shareware)
5. Carbon Copy Cloner (Donationware)
6. SuperDuper! (Commercial)
7. Intego Personal Backup (Commercial)
8. Data Backup (Commercial)
9. SilverKeeper 2.0 (Freeware)
10. MimMac (Commercial)
11. Tri-Backup (Commercial)
Others may be found at VersionTracker or MacUpdate.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files. -
Time Machine Slow & Backs Up Large Amounts of Data - The Fix
This is about Time Machine becoming very slow and taking hours to backup and trying to backup large amouts of data each time.
I spent a month on the phone with 2nd level Tech support and engineering - every other day.
I have 4 computers (one was a clients), all with different backup systems: Time Capsule over CAT 6 Gigabit Ethernet through a Thunderbolt monitor, internal eSata to external 6 TB RAID 5, Wireless to Time Capsule, Firewire 800 to External 2 TB RAID 1 dive.
With the install of 10.8.5 (the itermediate update to 10.9) I immedialety had Time Machine problems on all four computers. As I said, I spent a month talking with Apple. Also during this time I purchased 2 new MacBook Pro 13 Retinas. Installed Norton Internet Security 5 on them and they had the same problem. The new Retina's had 10.9 on them, so this is about 10.8.5 and 10.9.
After doing Data Capture on 3 of the computers for engineering (a new MBPro13R and my MacPro, and a MBPro 13 Mid-2012), engineering finally figured out what was happening.
Norton Internet Sucrity 5 for Mac is not longer compatible. As my 2nd level tech said: " Engineering told him, engineering needs to call Norton and figure out what they did to their program to cause this."
The fix is to completely remove Norton and all it's components (using the uninstall app inside the Symantec folder). Once you do that, Erase your backup drive, Restart everything, Re-connect your computer to your drive - then it immediately works perfectly.
Do Not Re-Install Norton.
I have now done this exact operation on 7 different machines. Time Machine works instantly. Time Machine is not the same program from 10.8 - it has been completely rebuilt, so I doesn't backup in the same way. But it works perfectly on all my computers now.
Don't forget the first backup will take hours since it is starting over clean and must do a complete backup the first time. After that it works fine.
I'm not going to put Norton back in my computers until I find that Norton has acknowledged this problem, or they come out with Norton Internet Security 6.
I reposted this here because on another post it was on the 20 page.
Hope this helpsGuitarfx wrote:
Time Machine has worked properly for me for several months. However, in the last week or two I have noticed some very strange behavior. Basically, Time Machine wants to backup virtually my entire system every few days or so.
How often do you let TM do backups? If it hasn't backed up for several days, it may indeed be doing a new, full, backup. Apple doesn't document this, but many folks believe it's about 10 days.
Download the +Time Machine Buddy+ widget from: http://www.apple.com/downloads/dashboard/status/timemachinebuddy.html. It shows the messages from your logs for one TM backup run at a time, in a small window.
It first shows the most recent backup. Navigate to one of the large backups, and examine the messages. If you see something there that seems suspicious, copy and post the messages here (be sure to get them all, as sometimes they overflow the small window).
I presume that for whatever reason, Time Machine believes my files are changing and therefore proceeds backing them all up. I can't really think of anything special I have done with my system in the last month which would cause this, but have tried formating my Time Capsule and starting over with a fresh backup--to no avail.
There are some applications that cause large backups, often because they use a single file, often a database, to store their data. Entourage is a common one: every time you send or receive a single message, the whole database is changed, and will be backed-up the next time. Apple mail, of course, stores messages individually to prevent this.
FileVault is similar, in an even bigger way: it converts your entire Home Folder into a single, encrypted disk image. So any change to anything in your Home Folder is treated as a change to the encrypted image. TM minimizes the impact, though, by only backing it up when you log out.
So consider this while examining the results from TimeTracker, as VA2020 recommended. -
Time Machine backing up the same amount of data EVERY time
Just upgraded to a MBP 17" and started new backups on a clean drive a couple of days ago. First backup took about 14-15 hours and now everytime it does a subsequent backup it is backing up 5.0G every time.
Any idea why? I have never seen it do this before and I have NOT been downloading/adding anything to my machine. Find it hard to believe I am getting 5.0G of cache data from browsing web sites every few hours.John Potts wrote:
Mine does the same, except it's "only" 1.4GB each time. It does this even though zero new data has been added to the hard drive (by me).
I have tried TimeTracker as recommended above but it seems to be very pre-beta indeed: according to the log, each Time Machine backup adds 0KB. And the original backup was also 0KB.
The backups will show zero until you click them, or set the Preference option to +*Automatically load backups.+* And the first one always shows zero (you really don't want to wait while it calculates the size of everything that was on your system). If they still show zero, you may be using an account that doesn't have permission to see them. Try signing-on as an Admin.
Moreover, when I invoke TimeTracker it remains on the desktop and can't be quit.
Did you try Quit? Either from the menubar or Cmd-Q?
I have my VM folder marked as excluded from back up, along with three external hard drives. Obviously, something must be going on that I don't know about. Are there are other tools that track the TM backups (in addition to TimeTracker)?
Try the BackupLoupe application, at: http://www.soma-zone.com/BackupLoupe/
But you'll likely have the same problems with it as you did with Time Tracker, as they don't sound like problems with the app itself, but your permissions. -
Time Machine drive is smaller than my Macbook Pro's drive.
Hello, ever since I've bought my new Macbook Pro about a month ago I've been doing Time Machine backups every day on an external laptop hard drive that is 40GBs in size. My Macbook's drive is already filling up and is going up to par with 40GBs the same as the external drive's size.
Just today I've done the routine Time Machine backup, and told me the drive is full so it needed to delete older time machine backups to be able to backup new ones.
My question, what if my Macbook's drive gets really filled up, for example up to 100GBs, will the external still be doing backups? Might be a silly question but to tell you the truth I dont know much on how the Time Machine backup utility works.Your TimeMachine backup should initially create a full back up and then do incremental backups. So, depending on how large your initial back up was (which would include all installed apps, music files, video files, etc... unless you specifically excluded them) any extra space will be used for backing up only newer versions of files that have changed. When an "older" back up is deleted... it is just deleting the oldest version of files for which it has multiple versions stored. If the amount of data on your internal drive goes over the amount of space available, TimeMachine will not be able to keep all of your data backed up and you will receive the drive full message (you just can't back up more data than you have space for... although... off the top of my head, I'm not sure if TimeMachine compresses the backups... but even still, you're working with very little elbow room). Also... unless your external laptop drive is an SSD... 40GB would indicate that it's fairly old. You may want to consider looking at just getting a newer external hard drive. High capacity drives in the 500GB (2.5" form factor) can be found for U.S. $50 and less now.
-
Time Machine only shows the current copy of the file I am trying to restore. There is none of the time machine backup histories shown. I am running OSX 10.7.5. I see the backup files on my external Time Machine hard drive in the Backups.backupdb folder.
Time Machine does show the history of my Macintosh HD, but when I try to navigate to the folder I wish to restore the backup history disappears. I've been searching for answers and I have not found one that works for me.Time Machine only shows the current copy of the file I am trying to restore. There is none of the time machine backup histories shown. I am running OSX 10.7.5. I see the backup files on my external Time Machine hard drive in the Backups.backupdb folder.
Time Machine does show the history of my Macintosh HD, but when I try to navigate to the folder I wish to restore the backup history disappears. I've been searching for answers and I have not found one that works for me. -
Time Machine drive does not show in Migaration Assistant
Greetings,
I am trying to migrate my user from my Time Machine backup drive with Migration Assistant, bu the drive does not show in the list. Other drives show that are not Time Machine drives.
HelpDear Pondini,
I found the .exclusions.plist file at the 3/6 backup and it has the bunch of exclusions list...I guess this was the reason. But I really didn't set this up.
Thanks again. Somehow, I don't have "com.apple.mail.plist" in "~/zzang/library/preference". I foundt it under "~/zzang/library/containers/com.apple.mail/Data/Library/Preferences/".
1. I first deleted the current preferences files and copied the com.apple.mail.plist from the backup to ~/zzang/library/preference/ folder.
2. I also delted all the files under ~zzang/Library/Mail.
3. I copied contents under ~Library/Mail/ from backup.
4. I started Mail and saw basic account settings and different mail accounts were there. But all the contents (mail, signature, mailboxes under each accounts (sent, deleted, spam, etc.), mailboxes on my mac, are missing.
5. I rebuilt the root mailboxes and no effect.
6. Hence, I checked copied mailboxes and got information and it only has size of 8KB each. When I copied, it was copying 6.6GB. I don't know what is going on here.
7. Hence, I started again from the process 1 above. It is now copying 6.6GB again.
8. What I noticed when I started Apple Mail, it says it will import mail but it was very short and then went back to the same status. No contents....
I looked at more details...
Original backup has V2 directory and no other directories or files ~zzang/Library/Mail while my current Mac created bunch of other things over there. See below images.
3/6 backup
Copied mail on the computer. -
External time machine drive no longer being automatically recognized
Recently my RMBP has stopped recognizing my external time machine drive. When ever I connect my 1 TB WD drive to my mac, it shows up on my desktop as usually but will not get recognized by time machine. I used to be able to connect the drive, have it show up on my desk with the orange USB logo, and then it would be auto recognized and the time machine logo would appear on it and it would start backing up. Now, I connect it and it just stays at the orange USB logo. I have to go to the time machine menu bar icon and open time machine's preferences and manually select the drive to get it to back up. This happens both on battery power and while I'm charging. I have already verified the disk in disk utility and have repaired as well. I don't recall when this started happening. I was running the 10.9.4 beta before its public release, but it hadn't been working before I upgraded to that either.
This simple procedure will clear your Time Machine settings, including exclusions. The backups won't be affected. If you have a long exclusion list that can't be recreated easily, you may prefer a more complicated procedure that preserves the exclusion list. In that case, ask for instructions. Otherwise, do as follows.
Triple-click anywhere in the line below on this page to select it:
/Library/Preferences/com.apple.TimeMachine.plist
Right-click or control-click the highlighted line and select
Services ▹ Reveal in Finder (or just Reveal)
from the contextual menu.* A Finder window should open with a file selected. Copy the file to the Desktop. Then move it (the original, not the copy) to the Trash. You'll be prompted for your administrator password. Restart the computer and recreate your settings in the Time Machine preference pane. It will show that you have no backups. Don't worry; your backups haven't been touched. Run a backup to test. The backup may take much longer than usual. If TM now performs as expected, delete the file you copied to the Desktop.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combinationcommand-C. In the Finder, select
Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return. -
How do I (fully, absolutely) erase time machine drive?!
I have looked and looked, BUT I cannot find the frickin' answer to this question. I was running Mavericks from an external USB 3.0 SSD which seemed to work great (MUCH faster OS and app loading than the 1TB HD in my Mini) UNITL it just refused to boot...grey logo screen, wheel turning, but no boot. I tried all the recommended steps but it is not working. So, I decided to just give up on the external boot thing and go back to booting from my built in HD. However, I need to redo my backup (right?) since it is from a different OSX install (the external boot drive). But the **** external backup drive will not erase! I formatted it in disk utility but when I go into Time Machine it shows only a fraction of the available GB (424GB out of 1TB) which means it is *still* hanging on to the old backup. How do I format this disk so that it is as if it is fresh from the factory? This is insane...why doesn't disk utility do this? I am about to give up on Mac altogether over this &%#@. As usual, the answer is probably easy but obscured by Apple's reluctance to allow the user the power they need. Thanks for any help.
Over the years I have gotten tired of using TM a couple of time and reformatted the drives to use for other things.
1. Connect the External HD and open Disk Utility in your Utilities Folder.
2. Highlight the HDs first icon in the list of drives and select the Partition tab.
3. Under Volume Scheme select 1 Partition and click on the Options... button.
4. Select GUID Partition Table in the drop down window and click OK.
5. Set the Format to Mac OS Extended (Journaled), name it and click the Apply button.
6. Once that is done, then you can use the empty drive for CCC or SuperDuper. -
How do we regain control over our Time Machine drive revisited
+I posted this question as two posts over in the+ *Intel-based iMac* +forum but I think I may have put it in the wrong place. Please forgive me if you've already read this over there. If someone tells me how to delete a post I will or perhaps a Moderator can/will do it for me.+
+O M Oz+
Recently our 2.66 Intel Core 2 Duo started into a cycle of rebooting itself during the startup sequence. Eventually we decided to Restore the disk from the Time Machine Backup which is kept on an external 1TB La Cie drive.
After the Restore was complete; Time Machine attempted to do a backup run but we got an error message saying the drive could not be accessed to write the backup. Only the very last backup could be seen from the Star Wars screen. The icon had changed to the generic usb drive icon with a padlock.
I attempted a Full Reset of Time Machine by deleting the Preferences as described in the Troubleshooting thread. Since then we have not been able to access the Time Machine drive at all with either Time Machine or Finder.
A check of Sharing and Permissions shows that all users are listed having custom access which seems to mean you cannot read or write the drive. Disk Utility reports the drive as seeming to be okay when run in either Verify or Repair modes.
I have also attempted to run the sudo command from Terminal with no success. I'm running out of ideas. I don't want to do a low level reformat of this drive yet because it IS a backup drive and I'm not clear on the status of the restored drive.
*Next Day after sleeping on it, I posted...*
I've been thinking it over carefully and think I might have done the damage myself.
Before things went pear shaped I needed to back up the 80GB Hard Drive for a laptop but was just a little short of space on the 1TB drive. In Finder I went into the backup.backup folder and deleted the oldest backup under Finder.
From what I NOW know of the data structures of Time Machine I suspect this would have also removed the backups of whatever it is that logs the various permissions. Am I right?
If I am right can I recover from this and still save the the older backups?
Old Mac OzI half expected you would be the first to reply, Pondini
Pondini wrote:
Old Mac Oz wrote:
. . . The icon had changed to the generic usb drive icon with a padlock . . .
. . . *we are not able to access* the Time Machine drive at all *with either Time Machine or Finder*. > >. . .From what I NOW know of the data structures of Time Machine I suspect this would have also removed the backups of whatever it is that logs the various permissions. Am I right?
Not exactly, but yes, that can damage your backups.
Try to repair them, per #A5 in the Troubleshooting Tip. If that succeeds, your backups are probably ok. If not, It's possible that +Disk Warrior+ can. It's expensive (about $100), and probably a good investment for the future, but there's no guarantee.
I have already tried that but Disk Utility reports that there is nothing wrong with the disk; clearly that is wrong. I cannot reset the permissions to let me (as the Administrator) even read the disk
If that succeeds, and the 80 GB backup from another Mac is still there, you can delete it via Time Machine. See #12 in the Frequently Asked Questions *User Tip,* also at the top of this forum.
The 80GB backup was a simple Finder copy from the extracted Hard Disk onto my Time Machine disk, just simply regaining Finder access will allow me to rescue that
Also, everything you restored to your internal HD is considered as new, so it must be backed-up again. That will, of course, take a lot of space. It's possible that Time Machine deleted a large number of your old backups to make room. If it didn't, because it couldn't do the backup, it will when it can.
I understand that is what should happen.
So . . . try the repair. If that works, see if the old backups are still there, and also see how much space is available on your TM drive. If there's not enough room for a new full backup of your internal HD, plus 20% for workspace, TM will have to delete some old backups. If the disk isn't well over twice the size of the data it's backing-up, your best bet may be to erase the drive and let Time Machine start fresh.
I am coming to that conclusion. The drive is plenty big enough, it's a Terabyte backing up a 300GB disk. Activity Monitor and Finder using +Get Info+ both tell me the drive has 931.39GB available with about 907GB used, we just cannot access any of the data this usage represents due to the locked permissions.
Since I last posted I have also tried resetting PRAM and running sudo from Terminal as per #C5 in the Troubleshooting Tip to reset the permissions to no avail.
The Restore has not been a success so I am probably going to have to wipe the whole computer and rebuild the system, something I am understandably unwilling to do.
I asked here because the problem seems to be related to a recent Time Machine run and the drive I used. Am I asking my question in the correct forum?
Thanks for your input so far.
Old Man Oz -
Lost the ability to Spotlight Index my Time Machine drive
I have an external, Firewire Time Machine drive which has been working without problems up to now. This evening I had a backup which hung up in the "preparing" stage (no file transfers begun yet). When I went to look in the console, there was a device error apparently related to trying to detect the powered-on state of my Time Machine drive. Apparently Time Machine did not handle this gracefully. In the course of trying to clear that I got into a state where I had to force shutdown of the system (holding the power button). (I accidentally clicked on the Time Machine icon which got hung up trying to display the histories, and left me with no access to the Desktop....)
Things appeared to check out fine when I brought the machine back up (including Verify Disk of both the main and Time Machine drives and Repair Permissions of the main drive), and I finally did a Back Up Now in Time Machine. Due to the forced shut down, this became a "Deep Traversal" "preparing"stage. We'll I've seen those before, so no worries. However it lasted quite a bit longer than it should, at which point I noticed that Spotlight was indexing the Time Machine drive.
So at this point I dragged the Time Machine into the Spotlight Privacy list. Rather than going away completely as I expected, the indexing of the Time Machine drive apparently went into some sort of clean-up phase that said it was still indexing for another 5 minutes (where it had, just prior, said it was going to be indexing for another 2 hours). The progress bar advanced normally as if it really did do 5 minutes more of indexing of the Time Machine drive. I've not seen this before
When that finished, the backup which had been "preparing" during all of this also finished "preparing", transferred the several MB of files I expected, and finished normally. There were no errors in the console related to any of this.
I rebooted, and once again did a pair of Disk Verifies and a Repair Permissions without problems. Opened up the console to track things, and poked around in the Time Machine. All was normal as far as I can tell. I also explored the Time Machine drive via the Finder. No problems.
So I now went into Spotlight Privacy and removed the Time Machine drive from the privacy list expecting it to do the re-indexing I had stopped above. Spotlight started indexing the drive and a couple seconds later it stopped. I tried again -- into and out of privacy -- same result, a couple seconds of indexing and then it stopped.
At this point I noticed the console was saying I had some bus errors in the I/O system, and that's what was terminating the md worker process and stopping the indexing.
So I shut down, unplugged the Time Machine drive, and went through my maintenance ritual.
I reset the PMU (this is a powerbook), reset PRAM, booted once in Safe Mode, booted normally, and ran Disk Utility again to Verify and Repair Permissions on the main hard drive. All of that went without a hitch. No failures, faults or funnies.
I ran through the list of Applications I use, keeping an eye on the console. Again no problems.
So I shut down, plugged the Time Machine drive back in and booted back up. I put the drive into Spotlight Privacy and turned off Time Machine backups. I then did a Verify Disk on that drive. No problems. I went into the Time Machine history display. No problems. And no problems looking at it in the Finder either. In particular, no bus errors or anything else funny in the console.
I rebooted and did a new Back Up Now. It completed without problems. It was another Deep Traversal backup due to the Safe Mode Boot, but it went without a hitch. I rebooted and did another Back Up Now and got a normal speed incremental backup again without a hitch. The bottom line is that as far as I can see that Time Machine drive is working just fine.
So I went into Spotlight Privacy and removed it from the list. Once again it started to index and stopped in a couple seconds. But this time there were NO Console error messages.
I moved my main hard drive into Spotlight Privacy and removed it and it re-indexed from scratch just fine. Tried again with the Time Machine drive -- indexing stopped in a couple of seconds with no message in the Console. Spotlight searches find all the right stuff in the main drive. Spotlight and finder searches find only the top level Time Machine folders in the Time Machine drive.
I also tried removing the Spotlight plist from my account's Library / Preferences. Spotlight created a new plist as expected but it still won't index that darned Time Machine drive.
Apparently there is something left over from when I originally aborted the Spotlight indexing of that drive which is causing Spotlight to think it has no work to do. I'm not seeing any I/O errors of any sort any more (I think my maintenance pass took care of that) and Time Machine backups and history access continue to work just fine. And again, the Time Machine disk Verifies just fine.
So I've run out of things to try.
Is there a hidden file that I need to remove from that drive so that Spotlight no longer thinks it already has it indexed?
--BobWell unfortunately the command
sudo mdutil -E /Volumes/MyDiskName
didn't help.
The command itself echoed the name of the volume and then said "Indexing Enabled", which looked good. But the Spotlight indexing stopped after a couple seconds. The Console reported the Terminal sudo command and nothing else.
I tried moving the Time Machine drive in and out of Spotlight privacy and once again the indexing started and stopped a couple seconds later with no Console messages.
I then tried another trick I've learned to make Spotlight indexing happen which is to do a Finder search for, say, all folders (limited to the one drive) via Command-f and while Including both System Files and files both Visible and Invisible. And indeed Spotlight indexing started but again stopped a few seconds later.
However, this time there were console messages and a crash report.
The Console shows (with personal information x'ed out):
12/31/07 1:30:38 PM mds[28] (/)(Error) IndexCI in openindex_filelazy:open file error: 2, 0.indexGroups
12/31/07 1:30:41 PM ReportCrash[146] Formulating crash report for process mds[28]
12/31/07 1:30:42 PM com.apple.launchd[1] (com.apple.metadata.mds[28]) Exited abnormally: Bus error
12/31/07 1:30:42 PM com.apple.launchd[1] (0x10ba40.mdworker[96]) Exited: Terminated
12/31/07 1:30:42 PM com.apple.launchd[1] (0x1004a0.mdworker[108]) Exited: Terminated
12/31/07 1:30:42 PM mds[147] (/Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF)(E rror) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF/0. ; needs recovery
12/31/07 1:30:43 PM ReportCrash[146] Saved crashreport to /Library/Logs/CrashReporter/mds2007-12-31-133038Xxxxxx-Xxxxxx-Computer.crash using uid: 0 gid: 0, euid: 0 egid: 0
The Crash Report reads as follows (again with personal information x'ed out):
Process: mds [28]
Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
Identifier: mds
Version: ??? (???)
Code Type: PPC (Native)
Parent Process: launchd [1]
Date/Time: 2007-12-31 13:30:38.746 -0500
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000030
Crashed Thread: 15
Thread 0:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0000cfa0 0x1000 + 49056
5 mds 0x00005580 0x1000 + 17792
Thread 1:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 2:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 3:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 4:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 5:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 6:
0 libSystem.B.dylib 0x92eda3ec _semwaitsignal + 12
1 libSystem.B.dylib 0x92f16fa0 pthread_condwait + 1580
2 mds 0x00009648 0x1000 + 34376
3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 7:
0 libSystem.B.dylib 0x92ee0ea0 read$UNIX2003 + 12
1 mds 0x000091b4 0x1000 + 33204
Thread 8:
0 libSystem.B.dylib 0x92f15438 kevent + 12
1 mds 0x0007e584 0x1000 + 513412
Thread 9:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 10:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 11:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 12:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 13:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.spotlight.index 0x00207f0c _handleExceptions + 208
3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 14:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 15 Crashed:
0 com.apple.spotlight.index 0x002046cc ContentIndexContainsContentByDocId + 204
1 com.apple.spotlight.index 0x00164358 QueryFunctionCallbackContext::findContent(db_obj*, __CFString const*, char*, int) + 244
2 com.apple.spotlight.index 0x001634d0 qpContentIndexMatch(datastoreinfo*, dblazyobj*, query_piece*, void*, int) + 328
3 com.apple.spotlight.index 0x0015587c comparefile_againsttree + 828
4 com.apple.spotlight.index 0x00155d30 comparefile_againsttree + 2032
5 com.apple.spotlight.index 0x00155d5c comparefile_againsttree + 2076
6 com.apple.spotlight.index 0x001e307c -[SISearchCtx isObjectInQuery:withQuery:shortcut:] + 144
7 com.apple.spotlight.index 0x001fa268 -[SISearchCtx_FSWalk performSearch:] + 996
8 com.apple.spotlight.index 0x001e2cbc -[SISearchCtx executeSearchContextCracked_2:jobNum:] + 136
9 com.apple.spotlight.index 0x00177e80 siwork_queueprocess + 752
10 com.apple.spotlight.index 0x0017811c sischeduleronce + 356
11 com.apple.spotlight.index 0x0017816c sischeduleronce + 436
12 com.apple.spotlight.index 0x001784f8 sischeduler_run_waitingtimeout + 640
13 com.apple.spotlight.index 0x0016529c runLoop + 72
14 com.apple.spotlight.index 0x00165308 query_runLoop + 32
15 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 15 crashed with PPC Thread State 32:
srr0: 0x002046cc srr1: 0x0200f030 dar: 0x00000030 dsisr: 0x40000000
r0: 0x002046a4 r1: 0xf09a4380 r2: 0x00000000 r3: 0x00000000
r4: 0xf09a43c0 r5: 0x00000000 r6: 0x000074d1 r7: 0x00000000
r8: 0x003fc080 r9: 0x00000000 r10: 0x00000000 r11: 0x44000444
r12: 0x92ede094 r13: 0x00000000 r14: 0x00000000 r15: 0x00373410
r16: 0x00000000 r17: 0x00239e98 r18: 0x00000001 r19: 0x00227b9c
r20: 0x00000000 r21: 0x00245554 r22: 0x00000001 r23: 0x00000001
r24: 0x00000000 r25: 0x00000005 r26: 0x00000000 r27: 0x00000000
r28: 0x00000000 r29: 0x00000005 r30: 0xf09a43c0 r31: 0x00204610
cr: 0x24000444 xer: 0x20000004 lr: 0x002046a4 ctr: 0x92ede094
vrsave: 0x00000000
Binary Images:
0x1000 - 0xc1ffb mds ??? (???) <af9cc958b4b030835101ff024186c7d3> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
0xde000 - 0xe0ffd com.apple.MDSChannel 1.0 (1.0) /System/Library/PrivateFrameworks/MDSChannel.framework/Versions/A/MDSChannel
0x139000 - 0x23fffb com.apple.spotlight.index 10.5.0 (398.1) <5843125c709dd85f22f9bd42744beea5> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/Spotlight Index
0x1ca9000 - 0x1caaffc liblangid.dylib ??? (???) <5f078ac1f623f5ce432ea53fc29338c0> /usr/lib/liblangid.dylib
0x2198000 - 0x22bdffb libmecab.1.0.0.dylib ??? (???) <cd875e74974e4ec3a0b13eeeb236fa53> /usr/lib/libmecab.1.0.0.dylib
0x8fe00000 - 0x8fe309d3 dyld 95.3 (???) <a7be977c203ec5c76b2f25a7aef66554> /usr/lib/dyld
0x90123000 - 0x9016effb com.apple.Metadata 10.5.0 (398) <b6bb1fd5a7a9135f546b2d8cbd65eafc> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x901ab000 - 0x902d0ff3 com.apple.CoreFoundation 6.5 (476) <9073c2bfdf6842562c8b7f0308109c02> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9060a000 - 0x90612fff libbsm.dylib ??? (???) <c1fca3cbe3b1c21e9b31bc89b920f34c> /usr/lib/libbsm.dylib
0x90683000 - 0x90688ff6 libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x90757000 - 0x907d2fff com.apple.SearchKit 1.2.0 (1.2.0) <1b448fbae02460eae76ee1c6883f45d6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x9088a000 - 0x9090ffff libsqlite3.0.dylib ??? (???) <7b379cb4220346e99c32c427d4539496> /usr/lib/libsqlite3.0.dylib
0x90aa7000 - 0x90ab5fff libz.1.dylib ??? (???) <1a70dd3594a8c5ad39d785af5da23237> /usr/lib/libz.1.dylib
0x90b50000 - 0x90be2fff com.apple.framework.IOKit 1.5.1 (???) <591b8b0cc4261db98a6e72e38eef5f9a> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x91105000 - 0x9116cffb libstdc++.6.dylib ??? (???) <a4e9b10268b3ffac26d0296499b24e8e> /usr/lib/libstdc++.6.dylib
0x9116d000 - 0x912b5ff3 libicucore.A.dylib ??? (???) <250daed2fb2e6bf114480e2e4da0728b> /usr/lib/libicucore.A.dylib
0x91c3c000 - 0x91d32ffc libiconv.2.dylib ??? (???) <05ae1fcc97404173b2f9caef8f8be797> /usr/lib/libiconv.2.dylib
0x91d3a000 - 0x91db4ffd com.apple.CFNetwork 220 (221) <00b882d3d3325526b78ded74880759fe> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x9236a000 - 0x92382ffb com.apple.DictionaryServices 1.0.0 (1.0.0) <fe37191e732eeb66189185cd000a210b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x92383000 - 0x9238effb libgcc_s.1.dylib ??? (???) <ea47fd375407f162c76d14d64ba246cd> /usr/lib/libgcc_s.1.dylib
0x92742000 - 0x92769fff libxslt.1.dylib ??? (???) <3700d04090629deddb436aa2d516c56d> /usr/lib/libxslt.1.dylib
0x92777000 - 0x92860fff libxml2.2.dylib ??? (???) <6f383df1e1e775be0158ba947784ae13> /usr/lib/libxml2.2.dylib
0x928aa000 - 0x928b9fff com.apple.DSObjCWrappers.Framework 1.2 (1.2) <2411674c821a8907449ac741ce6a40c3> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
0x92a17000 - 0x92afafeb libobjc.A.dylib ??? (???) <4a90e315bd1718c3f5ae09ee6c23e36c> /usr/lib/libobjc.A.dylib
0x92afb000 - 0x92bc9ff7 com.apple.CoreServices.OSServices 210.2 (210.2) <bad4943629f870d305f2bc7c6dfffe2d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x92bde000 - 0x92dbfffb com.apple.security 5.0.1 (32736) <15632bf9bbdb223194b3d79a2e48e02d> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x92e9a000 - 0x92ec5ff7 libauto.dylib ??? (???) <c1f2bd227817ad7c7bf29ec74729ac7c> /usr/lib/libauto.dylib
0x92ed2000 - 0x9306bfe3 libSystem.B.dylib ??? (???) <8a6cd873dfa7ada786efac188f95ed1b> /usr/lib/libSystem.B.dylib
0x931a7000 - 0x934a7ff3 com.apple.CoreServices.CarbonCore 783 (783) <fd2acaf23e95472f78b8a077fa039986> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x946f2000 - 0x9472afff com.apple.SystemConfiguration 1.9.0 (1.9.0) <d925dde7699e6231c88a41b0254a7591> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x94933000 - 0x9494eff3 com.apple.DirectoryService.Framework 3.5 (3.5) <3246a5d1c6a3d678798a90e8c5cd3677> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x9494f000 - 0x9494fffa com.apple.CoreServices 32 (32) <42b6dda539f7411606187335d9eae0c5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x94c68000 - 0x94c9dfff com.apple.AE 402 (402) <a4b92c8ac89cc774b85fb44c48b9d882> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x96831000 - 0x9683afff com.apple.DiskArbitration 2.2 (2.2) <9c8f8ade43fa25b32109ef9dcc0cb5d5> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x9683b000 - 0x968d1ff7 com.apple.LaunchServices 286 (286) <a3a0b2af862e9a8945072f8cb523678f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x969bc000 - 0x96c00ffb com.apple.Foundation 6.5.1 (677.1) <4152239382fb0f48abbcbf35bd04afa6> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0xfffec000 - 0xfffeffff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff8000 - 0xffff9703 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
Apparently the mdutil command didn't actually delete the Spotlight index file which is causing the problem, or at least didn't leave the indexing files in a consistent, empty state to start indexing over again. I may have to Erase this Time Machine disk and start over.
I should point out that except for Spotlight indexing this disk is otherwise working just fine. It passes Verify Disk with no errors and both new Time Machine backups and viewing and restoring via Time Machine and Finder work without problem.
Any suggestions before I just Erase the disk and start over with a new backup?
--Bob -
Encrypted Time Machine Drive not visible
Hi,
I have a Mac Mini (2.53 GHz Intel Core 2 Duo with 4GB 1067 MHz DDR3 Ram) running OS 10.8.4 and all other OS/application updates have been run. I have a Drobo (2nd Generation, the one with four drive bays & Firewire) with 3.69TB used and 1.72TB free. The Drobo has the most up-to-date firmware 1.4.2 as well as the latest Drobo Dashboard software (2.5.2).
I was using a different NAS to backup my data from the Mini but the housing failed and I'm waiting for Other World Computing to send a new one. In the mean time, I decided to backup the Mini to the Drobo and Encrypt it. I believe it went through one complete backup of the Mini (440GBs) overnight. I also use the Drobo as my main drive for my photos and iTunes library. I have about 2TBs of music/movies and about 1TBs of photos already stored on the Drobo. During the day yesterday, during a regularly scheduled Time Machine backup (I believe it backs up every hour), I was in the process of deleting photos off the Drobo and got the dreaded spinning beach ball. I waited for 1/2 hour but still after no changes, I turned off the Mini and after rebooting the Time Machine drive will not show on the desktop.
The Drobo is visable in the Drobo Dashboard app and of course it says there are no issues.
The Drobo shows up in Disk Utility as a Virtual Whole Disk (in red type) and when running Verify or Repair Disk, it states that "Error: This disk needs to be repaired. Click Repair Disk." I can do this till the cows come home but nothing changes. The only other info that shows up in red is "Invalid Disk Label @ 17591825289216: invalid field value. It repeats it four times, I'm assuming once for each drive. The last piece of info is "disk3s2 is not a CoreStorage volume.
I saw on another thread to run a Terminal command "diskutil cs list" and it came up with the below listed info.
Last login: Thu Jul 18 12:51:04 on console
skurkis:~ administrator$ diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 6E1361BB-CAF7-468D-9CD5-5A77ED37C763
=========================================================
Name: -none-
Status: Initializing
Size: 0 B (0 B)
Free Space: -none-
|
+-< Physical Volume 161162B5-ABCE-4540-BA90-A3EA9E2E956B
Index: 18446744073709551615
Disk: disk3s2
Status: Failed
Size: -none-
skurkis:~ administrator$
Any help to get my nearly 4TBs of music, movies, photos back would be awesome!
Thanks,
JeffAre there any utilities that can help "uncorrupt" the volume so I can rescue my data?
The only thing you can do is destroy the Core Storage logical volume, which will remove all data. If there is anything other than backup data on it, you're in a recovery situation, which is a job for professionals.
You should immediately start a new backup on another storage device. Don't do anything else with the computer until that's done. -
Time Machine drive files after data recovery.....permissions problem?
Client had a hard drive crash, and then turned out her Time Machine drive was bad. We ran a data recovery on the Time Machine drive, which produced about 40GB of disk images...12 in all. There is a very promising image which shows the user folders, and we can click on hers and see her folders. BUT...when we try to open Documents, we get a message that
"Item "Documents" is in use by Mac OS X and cannot be opened"
Would there be an override of permissions or some such available to take a peek inside and hopefully pull files?
Thanks to all in advance.A general look at backup files......
-
I made the darnest mistake when I tried cleaning up my time machine drive by deleting some of the "back-up" restore points.
Since then, the external drive does not appear anymore on my mac's desktop. Nor does it appear on my windows OS laptop.
I tried using DISK UTILITY on my Mac and the drive appears there. I was able to run Repair Disk, though No Errors appear. I "cannot eject" using the EJECT button at the top of the application as it prompts me with a message
"EJECT FAILED --
The disk “WD Ext HDD 1021 Media” could not be unmounted.
Make sure that all applications and files are closed on this disk."
Same goes when I try using a WINDOWS OS machine. It does not appear on Windows Explorer. Though when it does appear in the "eject list".
I assume that deleting some of the restore points (at random) was the cause of this.
How can I repair it? I have some sentimental and personal files (i.e. family pictures) that are also stored on the drive.
Thanks in advance.Other than the Disk Repair from the Disk Utility, I would suggest resetting the PRAM: http://support.apple.com/kb/PH11243.
Tha's kind of a last ditch effort though. Can you put it in another mac computer with the mac os? Does it show up there?
Maybe you are looking for
-
Native library working in Eclipse but not in command line ...
I was working on a Nutch project combing CMeCab with the analyzer. It uses: System.load('CMeCab'); where the problem occured. I have the file libCMeCab.so in /usr/lib/ and it was working fine inside eclipse. But when I complie with ant (by the way I'
-
The welcome screen always appears upon starting iTunes. (Win7 with newest iTunes update)
The only option to get past is to click either "Agree" or "No thanks" and then I can view my music. However, upon closing and re-opening, the same screen will show up. Very annoying.
-
Hi all I have a flatfile file January February March December Now while inserting the data through sql*loader, I want that it should enter 1 for january and 2 for february......12 for december. can we achieve this? if yes then How? Thanks Ajay Kumar
-
What is the function module which uploads excel file data into tcodes
Hi, i want to upload data in cs01 tcode. but data is excel sheet while i am trying to use gui_upload it is not being possible for me to upload data. can any one tell me what is the function module? can any send me the steps how to uplaod data if it i
-
The 3D dropdown tab is there but I can not actually set up the 3D system for whatever I wish to 3D (as the moment it is text) all the options are there but they aren't clickable. (Using Photoshop CC)