Retospect 6.0.204 Mac OSX Tiger error "elem.c-821"

[bjryan 0]

Hi, Can anyone tell me what this error is or where i can go to look it Up?

' Trouble in Retrospect:

Internal consistency check failed:

Assertiion check at "elem.c-821" '

 

Regards Bj.

[CallMeDave 7]

Have you read the Dantz statement regarding using OS X 10.4?

 

http://www.dantz.com/en/products/tiger.dtml

 

I quote the relevant portion, regarding an update due this week:

 

 

"Prior releases of Retrospect must not be used on Mac OS X Tiger. "

[bjryan 0]

Thanks Dave, I came across that revalation after i had posted.

Regards Bj.

[bjryan 0]

Well added new update repaired permissions an when i run easy script this the result

 

+ New Media backup using EasyScript Backup at 4/5/2005 9:56 AM

To backup set G4 Backup Set A…

4/5/2005 9:56:43 AM: New Media backup: The backup set replaced with G4 Backup Set A [001]

- 4/5/2005 9:56:43 AM: Copying G4 Boot…

* Separating file backup set:

Data file name: G4 Backup Set A [001]

Catalog file name: G4 Backup Set A [001].cat

Internal consistency check failed:

Assertion check at "elem.c-821"

4/5/2005 11:46:49 AM: Execution incomplete.

Remaining: 225793 files, 14.3 GB

Completed: 158938 files, 10.6 GB, with 14% compression

Performance: 150.9 MB/minute

Duration: 01:50:06 (00:38:42 idle/loading/preparing)

Quit at 4/5/2005 11:46 AM

? Retrospect version 6.0.212

launched at 4/5/2005 11:47 AM

+ Retrospect Driver Update, version 6.3.102

any Ideas?

Regards Bj

[CallMeDave 7]

Now would be a good time to provide details about your hardware configurations, as well as any other information you can come up with regarding the history of this and what you've alredy tried (such as searches of the Forum for similar problems from others).

 

Dave

[bjryan 0]

Well I can add this to it now as well

 

? Retrospect version 6.0.212

launched at 4/5/2005 11:47 AM

+ Retrospect Driver Update, version 6.3.102

 

+ Normal backup using EasyScript Backup at 4/5/2005 12:10 PM

To backup set G4 Backup Set A [001]…

 

- 4/5/2005 12:10:53 PM: Copying G4 Boot…

Can't read file “4278369e4e54a”, error -43 (file/folder not found), path: “G4 Boot/private/var/tmp/4278369e4e54a”.

Internal consistency check failed:

Assertion check at "tree.c-3444"

4/5/2005 3:05:38 PM: Execution incomplete.

Remaining: 28585 files, 1.2 GB

Completed: 197287 files, 13.3 GB, with 9% compression

Performance: 133.2 MB/minute

Duration: 02:54:45 (01:13:13 idle/loading/preparing)

 

Quit at 4/5/2005 3:05 PM

 

 

No History did backup once after update to 10.4

wrote to this forum?

Saw reply at the same time, as saw do not use, waited for update ran update and tried another back up got 10gb in and crash tried 2nd backup in normal mode and second error occured with 1GB of 14Gb left. Saw your reply wrote this.

 

Any Suggestions Regards Bj.

 

 

400 Mhz G4 Power PC AGP Graphics

2GB Ram, 120GB Boot Drive, 120GB Internal Data Drive that i backup to.

What else would you like to know?

[DrewM 0]

I'm running the Tiger version just downloaded today, and I'm getting that same error.

 

(Power Mac G5 Dual 2.0, 512MB, 10.4)

[bjryan 0]

If this update was suppose to be able to save metadata it's notworking!

 

? Retrospect version 6.0.212

launched at 4/5/2005 9:14 PM

+ Retrospect Driver Update, version 6.3.102

 

+ Normal backup using EasyScript Backup at 4/5/2005 9:26 PM

To backup set G4 Backup Set A [001]…

 

- 4/5/2005 9:26:39 PM: Copying G4 Boot…

Can't read file “03225A759-5386-11D8-963F-0030657”, error -43 (file/folder not found), path: “G4 Boot/Users/barryryan/Library/Caches/Metadata/Safari/03225A759-5386-11D8-963F-0030657”.

4/5/2005 11:43:33 PM: 1 execution errors.

Remaining: 1 files, zero KB

Completed: 226023 files, 14.4 GB, with 10% compression

Performance: 148.6 MB/minute

Duration: 02:16:54 (00:37:53 idle/loading/preparing)

 

What now?

[CallMeDave 7]

Quote:

---

If this update was suppose to be able to save metadata it's notworking!

 

---

 

It's not supposed to be able to save (new, Tiger) metadata. Nor ACL data. That's clearly stated in the release announcement.

 

Dave

[bjryan 0]

Well what supposes to be wrong with the errors that i am getting?

 

 

 

and what does this mean?

 

 

 

'EMC will further enhance Retrospect by supporting two new file system-related features of Mac OS X Tiger: Extended Metadata and Access Control Lists. This future release of Retrospect will also be at no charge to all Retrospect 6.0 customers.'

 

 

 

In light of the error from the log.

[CallMeDave 7]

"This future release" is not the update that came out yesterday. It'll come out "in the future."

[bjryan 0]

CallMeDave this still dosen't fix my computer backup problem?

 

Any suggestions?

[bjryan 0]

So can anyone tell what these errors mean? Other than file not found.

[CallMeDave 7]

Quote:

---

this still dosen't fix my computer backup problem?

 

---

 

Which problem?

 

The -43 error is probably just a cache file that was present when Retrospect initially scanned the drive, but had been deleted (by the system) when Retrospect attempt to copy it. If Retrospect is currently blind to the files in this directory, you'd have gotten a File Not Found error on all of them (on my machene there are over 2,000 files in this directory).

 

The assert is another matter, and it's cause may be more difficult to track down..

 

You give no history of Retrospect on this machine; can we assume that you just got Retrospect, and have never tried backing up before now?

 

There's a long thread here on the Forum about 821 error that might yield some answers for you (although the main poster continued to insist that his hardware upgraded legacy configuration wasn't contributing to the instability he was experiencing, when it clearly is).

 

http://forums.dantz.com/ubbthreads/showflat.php?Cat=&Number=39145&page=&view=&sb=5&o=&fpart=all&vc=1

 

It's obvious your G4 AGP didn't ship from Apple with 4 Gigs of RAM; the first thing I'd suspect is the quality of the memory.

 

Dave

[bontfaen 0]

I get the same 'elem.c-821' error reported by many others including bjryan (usung the 6.0.212). So is version 6.0.212 the one that is supposed to enable Retrospect 6 to work in Tiger? If we're to wait for some other free update (solving metadata and so on) when is this being issued by Dantz? The only update I've seen so far is 6.0.212.

 

If 6.0.212 isn't reliable why did Dantz release it?

 

Meanwhile there must be a lot of people like me that are risking losing a lot of data!

 

Mike

[CallMeDave 7]

Quote:

---

I get the same 'elem.c-821' error reported by many others including bjryan

 

---

 

As Mayoff from Dantz wrote in the thread I referenced above, these errors can be caused by different things on different machines.

 

But if you don't provide specific information about your individal setup there's no opportunity for others in the community to make suggestions as to cause.

 

Dantz can't do QA tests on every Macintosh in the field, only on the machines they have access to. If it's crashing on your machine, you can either call them and open a support incident (where they'll ask you to describe your hardware/software in detail), or you can post that information here where a common factor might be revealed.

 

Dave

[sungoddt 0]

same error here

 

I have just installed the updated version of Retrospect on a latest model powerbook 17" running tiger

 

immediately before the powerbook being upgraded with tiger the earlier version of Retrospect performed a successful backup

 

attempting to perform a backup from tiger with 6.0.212 results in an internal Retrospect error, repeating the process results in exactly the same failure

 

the backup was to an external lacie d2 firewire drive, with latest firmware, which passes disk test (as does the internal drive being backed up

 

creating a *new* backup set on a *different* external disk (lacie, latest firmware) and attempting a backup results in *exactly* the same failure

 

so at present I cannot perform backups, sigh

 

reported to Dantz support yesterday, no acknowledgement so far

 

extract from the Retrospect log showing the failures...

 

∆ Retrospect version 6.0.212

launched at 5/5/2005 22:37

+ Retrospect Driver Update, version 6.3.102

 

+ Executing Immediate Backup at 5/5/2005 22:44

To backup set Backup Set A…

5/5/2005 22:44:36: Recycle backup: The backup set was reset

 

- 5/5/2005 22:44:36: Copying osx100…

Internal consistency check failed:

Assertion check at "elem.c-821"

5/5/2005 22:50:51: Execution incomplete.

Remaining: 297048 files, 58.9 GB

Completed: 21550 files, 1.6 GB

Performance: 257.2 MB/minute

Duration: 00:06:15 (00:00:15 idle/loading/preparing)

 

Quit at 5/5/2005 22:50

 

 

∆ Retrospect version 6.0.212

launched at 5/5/2005 22:51

+ Retrospect Driver Update, version 6.3.102

 

+ Executing Immediate Backup at 5/5/2005 22:57

To backup set Backup Set A…

5/5/2005 22:57:37: Recycle backup: The backup set was reset

 

- 5/5/2005 22:57:37: Copying osx100…

Internal consistency check failed:

Assertion check at "elem.c-821"

5/5/2005 23:03:43: Execution incomplete.

Remaining: 297050 files, 58.9 GB

Completed: 21550 files, 1.6 GB

Performance: 263.8 MB/minute

Duration: 00:06:06 (00:00:15 idle/loading/preparing)

 

Quit at 5/5/2005 23:03

[Guest]

I too am having the same hour, after 2 hours of intensely slow backup. Error stops the backup. 17" powerbook, backup worked fine before Tiger, am running the update, no idea how/what to fix...

 

J

[CallMeDave 7]

Quote:

---

reported to Dantz support yesterday, no acknowledgement so far

 

---

 

An assert in Retrospect will generate a special log file in /Library/Preferences/Retrospect/

 

But unfortunatly, the Mac version of Retrospect ships with all debug code removed, and the assert log won't contain the information that would be needed to track this down.

 

Dantz tech support has been known (in the past) to provide the commented version of the program, which will generate an error log chock full of developer-helpful information.

 

Since you're paying for the tech support you should ask that they allow you to provide them with a helpful assert log in order to help track down your problem. They should then respond by directing you to a place to download the debug version of the program to use, and to recreate the error with it.

 

Or, maybe, since this version was just released, they've had a bunch of reports and they don't need another log. No way to know without them telling us.

 

Dave

[slidie 0]

I just want to echo others - using RS 6.0.212 on Tiger I have yet to have a backup complete - they always fail with "an internal consistency" error....

[sungoddt 0]

to be honest my patience with dantz has expired

 

at present i'm testing alternative backup software, the prospective vendor has responded inside an hour with the *resolution* of a technical issue with their software

 

dantz no longer gives that level of service

[jlimpert 0]

Similar errors here. It worked properly before I upgraded my system to Tiger and the latest version of Retrospect.

 

? Retrospect version 6.0.212

launched at 5/3/2005 19:08

+ Retrospect Driver Update, version 6.3.102

 

+ Executing Immediate Backup at 5/3/2005 19:38

To backup set Zim 20040911…

 

- 5/3/2005 19:38:28: Copying Macintosh HD…

Internal consistency check failed:

Assertion check at "elem.c-821"

5/3/2005 20:24:48: Execution incomplete.

Remaining: 176026 files, 4.5 GB

Completed: 114506 files, 1.6 GB

Performance: 37.6 MB/minute

Duration: 00:46:20 (00:04:17 idle/loading/preparing)

 

Quit at 5/3/2005 20:24

 

 

? Retrospect version 6.0.212

launched at 5/3/2005 20:25

+ Retrospect Driver Update, version 6.3.102

 

+ Executing Immediate Backup at 5/3/2005 20:54

To backup set Zim 20040911…

 

- 5/3/2005 20:54:34: Copying Macintosh HD…

Internal consistency check failed:

Assertion check at "elem.c-816"

5/3/2005 21:48:31: Execution incomplete.

Completed: 175018 files, 4.6 GB

Performance: 88.4 MB/minute

Duration: 00:53:57 (00:01:42 idle/loading/preparing)

 

Quit at 5/3/2005 21:49

[mjbolzan 0]

I am seeing this error too via the client on my son's mac.

 

did an archive and install of tiger on his mac. uninstalled the retrospect client. installed the new retrospect client. the master client on another machine running os 10.3.9 is 6.0.204. (it looks to me like i'm not supposed to upgrade the retrospect app on the main machine until that machine converts to tiger.).

 

son's file backup set is on a firewire drive and was manually recycled so his backup last night was new. got the error which is reported in the title. below is the relevant portion of the retrospect log. following that is the assertion error log.

 

-------- operations log

 

 

+ 5/7/2005 12:19 AM: Backup Server started

 

+ Normal backup using BS-BackC at 5/7/2005 12:20 AM

To backup set BK-FBack01C…

 

- 5/7/2005 12:20:09 AM: Copying MacOSX on Matthew eMac…

5/7/2005 12:20:09 AM: Connected to Matthew eMac

Can't read file “mess.htm”, error 1 (unknown), path: “MacOSX/Applications (Mac OS 9)/Netscape Communicator™ Folder/NetHelp/Netscape/Messengr/mess.htm”.

Can't read file “1084896336840_Dcp02538.jpg”, error 1 (unknown), path: “MacOSX/GP-01/1084896336840_Dcp02538.jpg”.

Can't read file “gundam_msia-turna-box.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundam_msia-turna-box.jpg”.

Can't read file “gundam_msia-turna1.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundam_msia-turna1.jpg”.

Can't read file “gundam_msia-turna2.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundam_msia-turna2.jpg”.

Can't read file “gundam_msia-turna3.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundam_msia-turna3.jpg”.

Can't read file “gundam_msia-turna4.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundam_msia-turna4.jpg”.

Can't read file “gundam_msia-turna5.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundam_msia-turna5.jpg”.

Can't read file “gundam_msia-turna6.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundam_msia-turna6.jpg”.

Can't read file “gundamgp01.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundamgp01.jpg”.

Can't read file “gundamgpaf.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundamgpaf.jpg”.

Can't read file “gundamgpaf2.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundamgpaf2.jpg”.

Can't read file “gundamgpaf3.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundamgpaf3.jpg”.

Can't read file “gundamgpaf4.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundamgpaf4.jpg”.

Can't read file “gundamgpaf5.jpg”, error 1 (unknown), path: “MacOSX/GP-01/gundamgpaf5.jpg”.

Can't read file “MSIAgp012.jpg”, error 1 (unknown), path: “MacOSX/GP-01/MSIAgp012.jpg”.

Can't read file “MSIAgp015.jpg”, error 1 (unknown), path: “MacOSX/GP-01/MSIAgp015.jpg”.

Can't read file “Video Snapshot 1.tiff”, error 1 (unknown), path: “MacOSX/GP-01/Video Snapshot 1.tiff”.

Can't read file “Video Snapshot 2.tiff”, error 1 (unknown), path: “MacOSX/GP-01/Video Snapshot 2.tiff”.

Can't read file “Video Snapshot 3.tiff”, error 1 (unknown), path: “MacOSX/GP-01/Video Snapshot 3.tiff”.

Can't read file “Video Snapshot 4.tiff”, error 1 (unknown), path: “MacOSX/GP-01/Video Snapshot 4.tiff”.

Can't read file “Video Snapshot 5.tiff”, error 1 (unknown), path: “MacOSX/GP-01/Video Snapshot 5.tiff”.

Can't read file “Video Snapshot 6.tiff”, error 1 (unknown), path: “MacOSX/GP-01/Video Snapshot 6.tiff”.

Can't read file “Video Snapshot 7.tiff”, error 1 (unknown), path: “MacOSX/GP-01/Video Snapshot 7.tiff”.

Can't read file “Video Snapshot 8.tiff”, error 1 (unknown), path: “MacOSX/GP-01/Video Snapshot 8.tiff”.

Can't read file “Video Snapshot 9.tiff”, error 1 (unknown), path: “MacOSX/GP-01/Video Snapshot 9.tiff”.

Can't read file “Acknowledgements.rtf”, error 1 (unknown), path: “MacOSX/Library/Documentation/Acknowledgements.rtf”.

Internal consistency check failed:

Assertion check at "elem.c-821"

5/7/2005 6:29:52 AM: Execution incomplete.

Remaining: 112286 files, 3.7 GB

Completed: 102406 files, 10.2 GB, with 9% compression

Performance: 28.6 MB/minute

Duration: 06:09:43 (00:08:06 idle/loading/preparing)

 

- 5/7/2005 6:29 AM: Backup Server stopped, general error

Quit at 5/7/2005 6:29 AM

 

----------- asserttion log

 

Retrospect detected a failure:

 

This report documents an unusual condition detected by Retrospect’s

internal integrity checking. This might be caused by a software bug,

but can also be the result of an incompatibility, hardware malfunction,

damaged system software, or other problems. Details on possible causes

can be found on Dantz’s website:

 

http://www.dantz.com/support

 

For further assistance, call us at (888) 777-5664 or (925) 948-9050.

Please be prepared to provide us a brief description of the steps

that led to this failure along with the assert log.

 

 

---

Retrospect Problem Report

date: 5/7/2005 6:28 AM

version: 6.0.204

 

Internal consistency check failed:

Assertion check at "elem.c-821"

 

Stack Crawl...

DATA_0000 +508e8

DATA_0000 +12aa7c

DATA_0000 +2cab0

DATA_0000 +1e004

DATA_0000 +66930

DATA_0000 +341f4

DATA_0000 +19a998

DATA_0000 +341f4

DATA_0000 +18dbe4

DATA_0000 +59d84

DATA_0000 +34308

DATA_0000 +5a004

DATA_0000 +18e34c

DATA_0000 +59d84

DATA_0000 +34308

DATA_0000 +5a004

DATA_0000 +18e770

DATA_0000 +341f4

DATA_0000 +101da8

DATA_0000 +341f4

DATA_0000 +1093d4

DATA_0000 +59d84

DATA_0000 +59f80

DATA_0000 +1094bc

DATA_0000 +59d84

DATA_0000 +59f80

DATA_0000 +106ce0

DATA_0000 +341f4

DATA_0000 +1093d4

DATA_0000 +59d84

DATA_0000 +59f80

DATA_0000 +59d84

DATA_0000 +59f80

DATA_0000 +109498

DATA_0000 +59d84

DATA_0000 +59f80

DATA_0000 +2cd00

DATA_0000 +59d84

DATA_0000 +59f80

DATA_0000 +2cdf8

DATA_0000 +2cf54

 

---

[bjryan 0]

CallMeDave.

The which problem is the fact that Retrospect 6.0.212 will not do a complete backup which fails because of an Assertion check at "elem.c-821" and the application quits. Myself and every body else that is having the same problem would like to know what we can do about it. Seeing that the only reason that we are have this problem has been the move to Mac 10.4 and the latest Update from Retrospect has not fix it.

Regards Bj.

[CallMeDave 7]

Given the reports in this thread (of which some are just "me too" and not very helpful, but others contain the sort of information that's necessary to know that it's not user error or hardware defects), it seems reasonable to surmise that there's something with 10.4 and Retrospect 6.0.214 that's not working as it should.

 

The stack crawl posted above is not helpful, as it doesn't have the debug code needed to point out where the fault is happening.

 

If Dantz has reproduced this in-house, they won't need logs posted. If they haven't seen the crash themselves, they'll need to get a debug log from a customer. And if they get multiple calls on their tech support line, they'll put the issue higher up on their priority list.

 

Note also that historically, tech support fees that are the results of bugs in the software have been refunded to customers who ask (and I'd suggest that asking politely is always a good idea).

 

Dave