Lost Metadata

I have a project that contains about 1500 photo files. Much of the metadata have been lost. In particular, Aperture seems to have forgotten which camera and lens took most of the pictures. Also, much of my geotag data are gone; the latitude and longitude are not there anymore. Has anyone else had this problem? Does anyone know a solution? Thanks.
Dave

What you describe sounds like when it hung it opened a virgin catalog file- ie., no edits nor metadata. Whatever, sorry it got florgerated on you, but it's quite unusual in my experience.
I always undo Edits in the History panel, and always make sure I have the right number of photos selected when I sync or undo. (Often one, or a whole folder)

Similar Messages

Lost metadata in file after attempt to Save RAW As JPG in PS CS3

Someone in other place in this Forum advised me that this will be probably more appropriate place to ask these questions, so I will give it a go. Below is a copy of my post on PS Windows thread (well, two posts really edited into one):
Hi,
I have just found out that after I open RAW pictures from my Canon 5D (but same happens with pictures from Canon 10D) in PS and than try to save them as JPGs, I loose majority of my metadata from the files (after right click on filename in. I can still Windows Explorer and clicking Properties or simply adding additional columns in Win XP Windows Explorer detailed view.
So same picture, without any editing at all, just opened as RAW file (which it is a CR2 or CRW file in Canons), and then saved as JPG, suddenly does not show the date of picture taken, focal length or exposure time are all gone. Does not matter if I try Properties in Win Explorer or say Properties in MS Office Picture Manager.
Was trying to look for any setting in PS that would set the ability to save or abandon saving of this type of information in JPG file but could not find anything of this kind.
What is interesting I went back to my pictures I have saved from RAW to JPG using same PS years ago, and I this was not a problem. Everything was saving OK.
So in summary:
1. This would not be a problem related to camera (it is unlikely that same problem would occur on two different models at the same time - even though both are Canons)
2. It must be a way to force the Photoshop to do that, I f I was able to do it successfully, almost without knowing, before.
Therefore, I would think that either:
1. There is some set of defaults somewhere in PS that I have accidently turned off causing my PS not to save this metadata properly or in full, or
2. That it came as some kind of bug with some of the updates to PS CS3 that I was getting over last year from Adobe.
Has any one else encountered similar problem? If yes, what did you do to resolve this issue?
I will be very grateful for any help, as I am not a frequent user of Adobe Photoshop and may just not be very familiar with the part that regulates that type of issues.
And I do not use the Save for Web option.
I just used (in PS CS3 running on Win XP Professional with SP3) the Save As from File menu.
What is also strange is that if I use File - Open command and get the first window with Open dialog box, where you have some basic options for opening/converting RAW format pictures (this window does not come up when I open JPG files) and I use existing there button to Save (which does not actually allow to do any editing of the picture before such way of saving) all Camera Properties, or that metadata, is actually saved into the newly created JPG quite correctly.
However if I use button Open in that conversion dialog box, and than save already opened RAW file as JPG, the majority of that data is gone (date picture taken, exposure time, aperture, focal length, exposure compensation steps etc).
I can see that RAW file has all this in the sections called EXIF and XMP (under File - File Information) but Save As does not add this info in the JPG files for some reason.

No, not really, because I ma not sure what it is for.
I just used (in PS CS3 running on Win XP Proffessional) the Save As from File menu.
What is also strange is that if I use Open command and get the first window with Open dialog box, where you have some basic options for opening/converting RAW format pictures (this window does not come up when I open JPG files) and I use existing there option to Save (which does not actually allow to do any editing of the picture before such way of saving) the all Camera Properties, or that metadata is actually saved into the newly created JPG.However if i use button Open in that conversion dialog box, and than save as JPG, the majority of that dtata is gone (date picture taken, exposure time, aperture, focal lenght, exposure compensation steps etc).
I can see that RAW file has all this in the sections called EXIF and XMP (under File - File Information) but Save As does not add this info in the JPG files for some reason.

Lost Metadata on re-imported files

Why am I losing my lens identity and copywrite status in the metadata? This seems to happen on each file sent out as a tif to a NIK software plugin. As far as I can tell, the remainder of the metadata is intact. The original NEF file is OK, only the re-imported tif is affected.

Not completely clear from your writing that we are talking about the same thing.
You keep saying that you do the stacking. "I set up Nik to send it back as a tif and stack it with original." I still think, as your title implies, that you are re-importing the edited TIF. In my worklfow, there is no re-importing, and Lightroom, not me, creates the stack.
If your external applications saves the edited file under the exact same name and folder location as the export from Lightroom (in other words, overwriting the export), then you should be able to close the file in the external application, and Lightroom will automatically recognize it, and the Library module should have the exact same metadata for this edited file as it had for the original. You don't have to re-import, or create a stack.

Lost Metadata Pool

I have a issue where for some unknown reason the drives initially set up as the metadata pool for my xSan are no longer visible to xSan Admin.
I have 3 xServes all running 10.4.9 and xSan 1.41. I have 4 Raids configured as follows:
Three Raids have all drives configured as Raid 5 with a "Hot Spare", and all are set up as data storage pools of 2.3 TB.
One Raid has the first two drives mirrored and originally identified as the MetaData Pool. Four of the remaining drives on this controller are in a Raid 5 Data Storage Pool configuration (one drive is reserved as a Hot Spare).
I was having problems mounting the xSan volume on one of the servers and after shutting it down and restarting, several times, the Metadata pool dropped from the storage pools and one of the other data storage pools has been identified as the Metadata pool. I can see the original mirrored drives that were set up as the Metadata Pool in Raid Admin as well as Disk Utility. I have not initialized anything since this problem occurred.
The question is whether I can "relink" the original metadata pool to the San volume? I can see it as /dev/disk1 via Disk Utility application. Since I have not initialized any of these devices, my hope is that I can get the SAN reconnected.
The interesting thing is that these mirrored drives are not showing up in the list of storage pools used for the san volume.
Thanks,
TC
PB 12 1Ghz Mac OS X (10.4.9)

What you describe sounds like when it hung it opened a virgin catalog file- ie., no edits nor metadata. Whatever, sorry it got florgerated on you, but it's quite unusual in my experience.
I always undo Edits in the History panel, and always make sure I have the right number of photos selected when I sync or undo. (Often one, or a whole folder)

Moving images from external HD to internal - lost metadata (mac)

got myself in a bit of a pickle here...
got a new imac - and upgraded from LR2 to LR4
all images are stored on an external hard drive - i *want* all of my pictures on the internal HD
so i copied the pictures folder to the internal HD - opened LR4, updated the catalog file (moved it from the extHD - pointed it to the new location on the internalHD)
apparently the lrcat file didn't get informed though - i had blank spaces in grid-view where there used to be pictures
so.. jiggered around with it until it found all the pictures (they appeared in grid view) - except, now there were alternating picture/blank-spaces
i discovered a way to "find" all the missing pictures - then "removed" them
unfortunately, when we checked our work, we found that the meta-data didn't come with the pictures that remained - so, no stars, tags, flags, etc.......
good thing is.. i still have the original files and LRCAT file on the extHD
can somebody help me right this ship??
(i think i want to just uninstall LR4 and start all over)

Obviously you can just use the Finder to copy the external iPhoto Library to your new Mac Pro. You should change the name of it first so you don't get the two mixed up or accidentally replace one with the other.
If you want the old and new photos in a single library you have a couple of choices. The free choice would be to import the "several images" from the MacPro's current library into the external library.
An easy way to merge two libraries is to use iPhoto Library Manager. It's available here: http://www.fatcatsoftware.com/iplm/
It has some functions in the free download version but more advanced functions require the US$19.95 shareware fee.

Have been lost, all the properties files in the CM repository (FSDB mode)

Hi,
I encountered the following problem: lost all descriptions to folders and files in the CM repository, which is connected to the FSDB mode. This happened as follows. At desired time connection to the server where the repository was broken, after some time the link was restored, but the repository was not available. After this portal has been restarted, and the repository to work, but lost all completed file properties, including the description.
How do I return all the description files?

Hi Stanislav,
Has this issue been resolved?
If not then the only way to restore this lost metadata would be a be restore, see sap notes 900571 and 737877 for more details.
Regards,
Lorcan.

Re-locating metadata after migration to Aperture 3 from ACDSee photo manager

Hi all,
Do you have experience from migrating a photo library from ACDSee Photo Manager 2009 (PC-software) to Aperture 3 with relevant metadata following each jpeg picture? Specifically, how to re-locate the metadata entered to ACDSee in Aperture 3 after importing the pictures to Aperture library?
ACDSee uses XMP to embed database information in each file (MGIF, JPG, DNG, PNG, and TIF file formats). Thus the database information (e.g. categories, keywords, descripitons etc) can be embedded inside the file ... and they should be usable when using other photo libraries... but apparently not. ACDSee Photomanager apparently does not copy the database information to IPTC fields but uses some other place in the files to store it. As a result I cannot re-locate the metadata once I've imported the pictures to Aperture.
Any advises on how to use Aperture to find the "lost" metadata is appreciated.
regards

I've faced the same problem too, and am making a little progress. The most important metadata for me is the rating (I'm still working on keywords etc) and I've managed to port that to Aperture by embedding it in an unused IPTC field in ACDSee and then searching for that field in Aperture, setting the rating as I go.
Would love to hear some suggestions for setting the keywords, especially ones that don't cause Aperture to crash.

Any way to find lost data from the xml file?

Is there any way I can retrieve lost metadata from my mp3’s? I have had 9 months worth deleted, the mps’s are still there but I’ve lost playlists and date added info etc. from the xml file. There are old restores from 9 months ago and now, (the iTunes librarys stored in history are from 9 months ago) the library I currently have has 5 songs ive added this week, and everything from over 9 months ago.
thanks,
guy

I have experienced the EXACT same problem... can't find a solution but am searching madly. Please post what you discover, if anything.

Intensify as external editor: how, and how well, does it work?

Intensify from developer macphun I have assigned as an image editor in iPhoto Preferences/Advanced. In iPhoto when i click on Edit the image opens in Intensity and can be edited. Unfortunately, saving after editing the image presents a standard file dialog offering to save the edited image in Documents. Getting the edited image back into iPhoto requires importing. Afterwards other data, such as Places, Faces and notes, are gone, although the original unedited photo remains in iPhoto and still has the data.
To edit with Intensify seems to require exporting, editing, then re-importing the photo. Is this how all iPhoto external editors work? I had thought that an external editor would substitute for iPhoto's editor and edit the existing photo while it remained in the iPhoto library I see on the MacPhun web site that Intensify Pro can be run "...as either a standalone app or as a plug-in to Adobe Photoshop, Adobe Photoshop Elements, Adobe Photoshop Lightroom and Apple Aperture." Does iPhoto need a plug-in version to simply replace its internal editor?
In past versions OS X allowed applications to provide services to one another. I have not kept up with how services are implemented, but I think I expected iPhoto to essentially use its services when an editing program was selected.
Can someone more familiar with OS X services, iPhoto's use of external editors in general and/or Intensity in particular, help me understand this?

Terrence,
Thanks for the comments. I appreciate the help. Sounds like you have considerable expertise in what I need to learn. Some of what you said I do not understand. If you could clarify these points it would help me more.
You say "No it's not like this with any editor used as an external editor in iPhoto." I assume you mean an external editor would edit the photo while the photo remains within the iPhoto database, so export to edit followed by import to return the edited photo to iPhoto would not be needed. Is this correct?
You say "... Intensify isn't an editor, it's a non-destructive database-based application." In my very limited reading and experience, it seems Intensity modifies single image files. How is an application intended to modify image files to change their appearance not an editor? How is an application intended to work with single files a database-based application?
While posting here I also asked MacPhun support a similar question. They replied "This editing procedure is fine, you can send the edited image from Intensify to iPhoto as shown at the screenshot attached."
The menu choice shown does allow saving in iPhoto after pressing in Intensity. However, the edited image imported into iPhoto has lost metadata such as found faces, places and comments associated with the original, and it is placed in a new Event. That MacPhun support refers to the product of what Intensity does as "the edited image" shows why I referred to Intensity as an image editor.
You say "In essence, you cannot use a non-destructive processor as an editor" yet "With Aperture I have used it as a plug-in." To me this sounds like one can use Intensity as a non-destructive processor if Intensity's function is accessed as a plug-in. That is, the necessity to export images from iPhoto to "process" (what I would call edit) them in Intensity results from how Intensity and iPhoto access the image files, not from the type of processing involved.
You say "This has nothing to do with services ..." Agreed. I mentioned services because I thought one application modifying data for another seemed like a service.
On further consideration I realize that non-destructive, eh, processing of an image requires storing the original plus the processing steps which have been implemented. This seems similar to what iPhoto's built-in editing functions do. However, I suspect Intensity's more complex processing of the image requires a more complex file structure, which iPhoto cannot read or write.
Supporting this idea of different file structures, I see my originals in iPhoto are typically JPGs of size 800 KB - 5 MB. After processing by Intensity, "-edit" is append to the file name, the format changed to tiff, and the file size increase by a factor of 8. The format conversion and consequent increase in file size I have not seen mentioned in Intensity's literature, but may be of significance to other potential users.
You say "There is no plug-in for iPhoto - perhaps you should ask the developers to make one." Agreed. Not for iPhoto, which is being terminated, but for its replacement Photos.

Move photos from iphoto7 to 6

I have photos to move (maybe 100) in a newer MB with iphoto7 to a MB with iP 6. I need to move some of the photos only. I did this once before (with great pain as I lost metadata the first try). I used FW and target mode, but I cannot recall how to do it.
I downloaded iphotomanager, but it did not let me copy from ip7 to ip6. SO that did not help.
Can someone refreash my memory on how I did this last time?
Can't someone (apple) publish this as a key item in support - there are many small interations of this asked.
Thanks in advance

To move photos from v7 to v6: there’s only one way: Export the pics from iPhoto 7 using the File -> Export command. In the resulting window be sure to set the Kind: to Jepg and tick the box at Title and Keywords. This will get the metadata. Then copy the exported files to the other machine and import them.
As this is a User-to-User forum and Apple don‘t promise to monitor or read anything here use:
iPhoto menu -> Provide iPhoto Feedback
To ask questions or request improvements from Apple.
For comments on iPhoto Library Manager contact the makers of that app.
Regards
TD

Managed or Referenced?

1St time user of Aperture here, coming from a Windows environment. I am a bit lost at the moment wit Aperture and how it works and why it does certain things. Firstly, managed or referenced. Which is best? I want to import my camera pics and keep them in one place. Referenced?

rwboyer wrote:
This is a fabulous idea. NOT!
Why the heck wouldn't you just round trip your image using something like say.... Edit with? Why the heck are you even using something like Aperture with this philosophy? I would suggest you just stick with PS and Bridge.
Wow, did you just wake up on the wrong side of the bed or something
Because round trip creates duplicate tif/psd file that's ~3x the size of raw file. With Ap v2, at least it save is in the same folder as where the referenced master file resides. It used to be completely useless because Ap would store the new tif into ApLib, even if the master was referenced.
As a matter of fact, I do use PS from time-to-time, along with CaptureNX for things that simply cannot be done within Aperture. I am not a pixel peeper so I really don't use PS other than to integrate text or create layer-based multiple images that ends up in other applications like Powerpoint, Keynote slides.
Doing what you suggest is the best possible way to wreak havoc with your workflow. Even if you are using LR that has no capability to do anything but referenced images this is not a good idea. Let me see I have like 300,000 images. I really love to remember where they are or look up a physical location and then go there with another tool and screw with the master image so that I wreak havoc on any nondestructive adjustments that Aperture/LR understands. Possibly screw up my metadata. Oh no wait I'll just redo things I have already done in a different tool and then save a copy somewhere and reimport that copy and add a bunch of metadata again. Yea that's good, that's way better and easier than just using "edit with". <----Sarcasm End Rant.
</div>
Diverse ideas are good thing. Really, not being sarcastic or argumentative.
There are more than one way to do things, as you know. While doing what I suggest may not make any sense to you, it makes sense to me and possibly others.
What is implicit in you basis is that if one let Aperture manage the masters, there is no need for disciplined file structure to store and backup the images by the user - other than let Vault/TM do it. And by using round-trip "edit with", Ap will manage that too. Since disk space is cheap, who cares. Its simple. I appreciate the argument for it. It just not for me. I find the option for easy direct access to master files more valuable than to have Ap manage my files.
Btw, I've never lost metadata by direct access of the files. They do get destroyed in PS with layers and fusing images and text but those really don't matter in this context.

File extension problem

Hello there everyone... My company is equipped with mac's an pc's and a pc server using windows 2000 server. The server 'died' and we bought a new one with windows sbs 2008, our files that were created by our mac computers were stored on the old server so we copied them back to the new one. The problem is that now when we try to access them some files that don't have extensions we can not open them as we don't know what they are, i.e in the same folder I had files that were tiff,jpeg,quark,pdf when I try to access them there are no extensions so I don't know with what program to open each file. These files are grey or black and are reffered to as Unix Executable File. Is there a way to get the mac systems to re-read the files correctly??? Our mac os is 10.4 and 10.5 and our server uses Windows SBS 2008!

I'd be worried about these files. You may have lost metadata as BD suggests.
Maybe your server administrator should look at copying mac file data or how to turn on the serving of Mac files. ( I'd guess it was an option in windows 2000. )
Can't you take a guess from the name what the application would have been?
Start the appropriate application & use file > open.
There is also the Terminal file command which will look inside a file & take a best guess at the contents of the file. Many files have an identifier in the first four characters of the file telling what type of data the file contains.
Macintosh-HD -> Applications -> Utilities -> Terminal
mac $ file /Users/mac/Desktop/ciruit.rtf
/Users/mac/Desktop/ciruit.rtf: Rich Text Format data, version 1, Apple Macintosh
mac $ file /Users/mac/Desktop/Lunch\ picture.JPG
/Users/mac/Desktop/Lunch picture.JPG: JPEG image data, EXIF standard
mac $
what you do is type file followed by a space. No need to type out the file path &name. Drop the file you wish to identify onto the terminal window. Press return after the drop.
you can also list the entire contents of a folder by the command:
file *
What you would do in this case is to use the cd command to move to the folder you want:
cd
then drag the folder you want to see & drop it on the terminal window. Press return after the drop.
Here is an overview of the terminal commands. Lets assume that your account has a short user name of mac.
Macintosh-HD -> Applications -> Utilities -> Terminal
#How to list all of your disks.
# The ls command is for list
mac $ ls /Volumes/
Audio CD Macintosh-HD Spotless Tiger-ext
mac $
# Let's say your flash drive is named Spotless
# cd is change directory
mac $ cd /Volumes/Spotless
# pwd is print working directory
mac $ pwd
/Volumes/Spotless
mac $
# The ls command is for list
# l is long
# F is type of file where / is directory
mac $ ls -lF
total 134704
-rw-r--r-- 1 mac staff 64560 Mar 3 2009 A-picture-of-Youpi-key.png
drwxr-xr-x 83 mac staff 2822 Nov 7 14:52 Applescript files/
drwxrwxrwx 12 mac staff 408 Dec 13 2008 Christmas Cards/
drwxr-xr-x 9 mac staff 306 Dec 21 17:39 Christmas Cards 2009/
... trimmed ...
What does all this mean?
drwxrwxrwx
d = directory
r = read
w = write
x = executeable program
drwxrwxrwx
| | |
| | all other users not in first two types
| |
| group
|
owner
# l is long
# a is all to show hidden files & folders
mac $ ls -lFa
total 134736
drwxr-xr-x 41 mac staff 1496 Dec 22 17:11 .
drwxrwxrwt 8 root admin 272 Dec 24 13:55 ..
-rwxrwxrwx 1 mac staff 15364 Dec 23 12:52 .DS_Store*
drwx------ 4 mac staff 136 Jan 22 2009 .Spotlight-V100
drwxrwxrwt 5 mac staff 170 Sep 14 16:36 .TemporaryItems
d-wx-wx-wx 4 mac staff 136 Dec 31 1969 .Trashes
-rw-r--r-- 1 mac staff 64560 Mar 3 2009 A-picture-of-Youpi-key.png
drwxr-xr-x 83 mac staff 2822 Nov 7 14:52 Applescript files
drwxrwxrwx 12 mac staff 408 Dec 13 2008 Christmas Cards
drwxr-xr-x 9 mac staff 306 Dec 21 17:39 Christmas Cards 2009
... trimmed ...
# mv is move or rename
mv -i the-name the-new-name
# You can just rename the file back to what it was with mv command.
mv -i old-name new-name
Here is what these commands mean:
cd is change directory
pwd is a print working directory
ls is list
sudo is Super user do
mv is move or rename
For cryptic comments, you can always uses the manual command which is man. For example:
man mv
# Type the letter q to quit.
I noticed that you had spaces in your filenames or directories. You need to escape them. See examples:
mac $ ls -l ~/"see it"
-rw-r--r-- 1 mac staff 3171 Oct 26 23:38 /Users/mac/see it
mac $
mac $ cd /Users/mac/Desktop/ttt\ html\ copy/
Do you know about tabing? Type in a few letters of a name then press the tab key. The computer will type out the rest of the name if it is unique.
Robert

Aperture skipping import of similar file names?

I discovered this this other day and raised the question in a "top 10 Aperture Suggestions" post. I've done more investigating since then without coming up with a solution. So I'm going to post it as it's own question here.
Up to now my workflow has included aquiring images from either a negative scanner (which creates a TIFF), or a Nikon D100 digital camera (which creates an NEF). From there I open up the original in Photoshop, make any manipulations I need to and save the new file as a psd in the SAME folder as the original. I can easily keep track of images I have manipulated because I can see the psd right next to the original TIFF or NEF.
I end up with images called something like photo01.TIFF and photo01.psd. They are completely different files, the TIFF being the original and the psd being the cleaned up, manipulated version - both in the same folder.
Here's the problem. Aperture doesn't recognize that there are two different files there. Perhaps because the file names before the extension are the same, it ignores the second one during the import process.
During my latest experiment I took an original TIFF scan of a negative called 129_20.TIFF, opened it in photoshop, did some color correction, and saved it back to the same folder, calling it 129_20.psd. I also created a smaller websized jpg of the same image and called it 129_20.jpg. Now even though there are three files in the folder with admittedly similar file names, anyone would be able to tell that they are actually different files, the original TIFF, the modified psd, and the jpg for the web.
When I try to import those images into Aperture using either the Import>Folders into a Project command, or the Import>Images command, Aperture only sees the original TIFF and only imports that TIFF instead of the three that are in the folder. If I take the TIFF out of the folder and try again, now Aperture sees the jpg file and I can import that, but not the psd. If I take both the TIFF and the jpg out of the folder and try again, of course only now does it see the psd.
Once the images are imported into Aperture, I notice that file name extensions are not visible under the images, so unless I click on one and use the Info window or ToolTips to show the meta data, I cannot easily see which version of the image I'm looking at in Aperture because it doesn't display the .TIFF, .psd, or .jpg extensions.
This is troubling to me and I hope I've simply not come across some setting somewhere that will help Aperture "see" my different versions of the same image. There doesn't seem to be anything on the boards or the Aperture manual directly about this. I've stopped importing because after 14,000 images, I've realized I'm "missing" all of my Photoshop corrected ones. Before I continue importing, I'd like to figure out if there is a work-around, if it's operator error, or if Aperture doesn't can't tell the difference between similar files names with different extentions.
Sorry about the length of this, but I'm trying to be thorough.
G5 Dual 2GB Mac OS X (10.4.3) 2GB RAM
G5 Dual 2GB Mac OS X (10.4.3) 2GB RAM

Yes I discovered exactly the same thing whilst trying to overcome another problem - that aperture lost metadata on tiffs saved with IBM PC bytes rather than Mac bytes ( in this case out of house scans done on a PC ). I tried saving my files as tiff Mac, psd and jpg in the same folder but with the same name apart from the extension. As you say Aperture only sees them as one file ( although it adds up their combined file size according to the image information dialogue box window ). On import it only imports one file. If you use the 'Import Folders into a project' option from the file menu it sees the three files in the navigation section OK but again only imports one. I then experimented with doing major changes in image size and adjustments and of course that made no difference.
I did find that I could import the files individually by dragging them one by one into a project but of course that is no help if you have thousands to import.
After some thought I decided that perhaps that was in tune with the idea behind Aperture being that you have only one master file which you then repurpose and export as required. My conclusion about Aperture at the moment is that it would be great if we were all starting from scratch but that it is struggling to cope with the admittedly enormous task of dealing with photographers who have massive libraries of existing images created, processed, keyworded and stored in all sorts of programs. Clearly we all need access to these and the info they contain as well as dealing with our future work.
Sorry not to be more help.
Best wishes
Jonathan
Imac G5/ Dual 2 Ghz Power PC G5 Mac OS X (10.4.3)

Time machine couldn't back up seagate backup plus, Not Detected...

I just bought the Seagate backup plus in December when my overly fragile macbook air screen cracked & I had to have it repaired...Anyway, of course I wanted a backup before sending it for repair.
I had nothing but trouble setting it up & getting it to make a backup, right out of the box & had to email, then call tech support. It had been working fine, until I updated whatever the latest version of Maverick's or whatever update came out. It has not backed up since April 16th. The light comes on for the backup plus. I googled & found something about firmware, so I went through that download process & it said the backup plus was up to date. I plug it into the USB & still nothing. It's just an error message saying "Backup delayed", then I click on Back Up Now & get an error saying Time Machine couldn't complete the backup to "Seagate Backup Plus Drive". The backup disk could not be found. Make sure the backup disk is connected or select a different backup disk. How wonderful. I also went to the Seagate website and found a troubleshooting guide, which was also worthless. The only thing it said was that it might be set to "sleep" and going through all this firmware and disconnecting and re-connecting and rebooting was supposed to fix this issue. I am so frustrated now, I can't even stand it. It is Finals week, I am in the Nursing program, which believe me is not an easy curriculum & now this! god forbid my life ever be without frustration and challenges, I feel like I am never ever going to be happy or have a good life, something is always wrong, I hate technology, I spend hours and hours and hours trying to figure things out, & then they just get messed up with an update and never work the same again.

It had been working fine, until I updated whatever the latest version of Maverick's or whatever update came out.
Yes, know the issue. Did you EVER install any (utterly worthless) hard drive control software that came bundled with that ext. USB hard drive?
OR especially software from a Western Digital drive?
If so youve got a serious issue of data loss (which is why you NEVER ever have a single external backup of data).
You can read all about it here on the last 20 pages:
https://discussions.apple.com/thread/5475136?start=1365&tstart=0
If you installed (which you should NEVER do) any HD control software, then youve got a serious issue where all your metadata is lost
Metadata is the data about the data on the HD, meaning not total loss, but almost the same as.
Run Etrecheck and post the results:
use this FREE little test APP to verify (most people here use it for diagnostics)
http://www.etresoft.com/etrecheck
EtreCheck is a simple little app to display the important details of your system configuration and allow you to copy that information to the Clipboard. It is meant to be used with Apple Support Communities to help people help you with your Mac. EtreCheck automatically removes any personally identifiable information from the output.

Moved home movies, now they have wrong dates!!!

My Mac was running out of space so I went into an Apple store and an associate suggested that I move my videos to an external drive, which I did. Now all my movies show the incorrect dates! Can I recover the lost metadata?

Video files have no date metadata except the file data. That can easily change when a file is moved, edited and do on. Unlike photos, where the date and time of the shot is tracked in the Exif metadata. So basically, never rely on the file date for a video - it's just not reliable.
One workaround is to name the file with the date - So, London, 1-5-2011 as a filename will sort the problem out for you.
Rather than cut and paste, try doing it the supported way: File -> Export and set the Kind to Original. That will probably preserve the file date, but it's only temporary. Sooner or later you're going to have this problem.

Lost Metadata

Similar Messages

Maybe you are looking for