hhoover Posted April 13, 2006 Report Share Posted April 13, 2006 I'm trying to (re) verify a backup to DVD. Every time I try, I get an assert failure at "elem.c-918". It never asserts during the verify phase of a backup. I have also gotten that assert failure when doing a verify on a tape (DAT4). Has anyone else seen this? Any workarounds? I haven't yet tried to restore from >these< backup media, although I've done successful restores before. Still, doesn't give me much confidence in the backup, eh? Hugh Hoover Link to comment Share on other sites More sharing options...
hhoover Posted April 13, 2006 Author Report Share Posted April 13, 2006 I checked the various logs and find that it appears to be related to a read failure - if that's the case, this is pretty unacceptable! Note that the error doesn't occur in the same place - it doesn't appear to be a hard read failure on the disk. Or at least Retrospect doesn't fail fatally on the error every time. from operations log: + Executing $[24]Verify$[25] at 4/13/2006 10:48 To backup set $[*!s319,,14,+3]NotOnTape<C9> $[40] Trouble reading: <D2>8-NotOnTape<D3> (2982), error 206 (drive reported a failure: dirty heads, bad media , etc.). Internal consistency check failed: Assertion check at "elem.c-918" Additional error information for device "PIONEER DVD+R - RDI" [1:0], Sense > f0 00 03 00 18 14 c0 0e 00 00 00 00 11 05 00 00 00 00 (PIONEER |DVD-RW DVR-111D|1.02) 4/13/2006 12:32:12: Execution incomplete. Remaining: 120101 files, 35.2 GB Completed: 78121 files, 32.6 GB Performance: 371.2 MB/minute Duration: 01:43:37 (00:13:44 idle/loading/preparing) Quit at 4/13/2006 12:32 From the error log (Retrospect.error.log.c063f548): Retrospect detected a failure: This report documents an unusual condition detected by Retrospect<D5>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 EMC<D5>s website: http://www.emcdantz.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: 4/13/2006 12:32 version: 6.1.126 Internal consistency check failed: Assertion check at "elem.c-918" Stack Crawl... DATA_0000 +50a38 DATA_0000 +12e8fc DATA_0000 +2cc14 DATA_0000 +1dfc0 DATA_0000 +65efc DATA_0000 +34344 DATA_0000 +1aea28 DATA_0000 +1add74 DATA_0000 +34344 DATA_0000 +19a790 DATA_0000 +59ed4 DATA_0000 +5a0d0 DATA_0000 +19ab68 DATA_0000 +59ed4 DATA_0000 +34458 DATA_0000 +5a154 DATA_0000 +19abf0 DATA_0000 +34344 DATA_0000 +101c7c DATA_0000 +34344 DATA_0000 +10d3a4 DATA_0000 +59ed4 DATA_0000 +5a0d0 DATA_0000 +59ed4 DATA_0000 +5a0d0 DATA_0000 +10d468 DATA_0000 +59ed4 DATA_0000 +5a0d0 DATA_0000 +2ce60 DATA_0000 +59ed4 DATA_0000 +5a0d0 DATA_0000 +2cf58 DATA_0000 +2d0c4 oh yeah - hardware: Hardware Overview: Machine Name: Power Mac G4 Machine Model: PowerMac3,5 CPU Type: PowerPC G4 (2.1) Number Of CPUs: 2 CPU Speed: 1 GHz L2 Cache (per CPU): 256 KB L3 Cache (per CPU): 2 MB Memory: 1.5 GB Bus Speed: 133 MHz Boot ROM Version: 4.3.3f2 ATA Bus: PIONEER DVD-RW DVR-111D: Capacity: 4.38 GB Model: PIONEER DVD-RW DVR-111D Revision: 1.02 Removable Media: Yes Detachable Drive: No BSD Name: disk2 Protocol: ATAPI Unit Number: 0 Socket Type: Internal OS9 Drivers: No S.M.A.R.T. status: Not Supported SCSI Parallel Domain 0: Initiator Identifier: 7 SCSI Target Device @ 0: Manufacturer: SEAGATE Model: ST336605LW Revision: 3700 SCSI Target Identifier: 0 SCSI Device Features: Wide, Sync, DT SCSI Initiator/Target Features: Wide, Sync, DT Peripheral Device Type: 0 SCSI Logical Unit @ 0: Capacity: 34.18 GB Manufacturer: SEAGATE Model: ST336605LW Revision: 3700 Removable Media: Yes Detachable Drive: No BSD Name: disk0 OS9 Drivers: Yes SCSI Logical Unit Identifier: 0 S.M.A.R.T. status: Not Supported Volumes: gurney: Capacity: 34.18 GB Available: 3.28 GB Writable: Yes File System: Journaled HFS+ BSD Name: disk0s9 Mount Point: /Volumes/gurney SCSI Target Device @ 1: Manufacturer: SEAGATE Model: ST373405LW Revision: 0003 SCSI Target Identifier: 1 SCSI Device Features: Wide, Sync, DT SCSI Initiator/Target Features: Wide, Sync, DT Peripheral Device Type: 0 SCSI Logical Unit @ 0: Capacity: 68.37 GB Manufacturer: SEAGATE Model: ST373405LW Revision: 0003 Removable Media: Yes Detachable Drive: No BSD Name: disk1 OS9 Drivers: No SCSI Logical Unit Identifier: 0 S.M.A.R.T. status: Not Supported Volumes: stilgar: Capacity: 28.06 GB Available: 3.04 GB Writable: Yes File System: Journaled HFS+ BSD Name: disk1s2 Mount Point: / sandbox: Capacity: 40.3 GB Available: 16.44 GB Writable: Yes File System: UFS BSD Name: disk1s3 Mount Point: /Volumes/sandbox System Software Overview: System Version: Mac OS X 10.4.6 (8I127) Kernel Version: Darwin 8.6.0 Boot Volume: stilgar Computer Name: stilgar Link to comment Share on other sites More sharing options...
RonaldL Posted April 18, 2006 Report Share Posted April 18, 2006 Hi Hugh, An RDU was just released which addresses an elem.c-918 assert. I don't know if it's the exact same assert you are seeing though as this seemed to happen when searching pre-Retrospect 6.x backup sets. Here's the forum thread on it: http://forums.dantz.com/ubbthreads/showflat.php?Cat=0&Number=69422&page=0&view=collapsed&sb=5&o=&fpart=1 Please give the driver update a try and let us know how it goes: http://kb.dantz.com/article.asp?article=8136&p=2 Link to comment Share on other sites More sharing options...
lindseystock Posted June 9, 2006 Report Share Posted June 9, 2006 Hello, I have the same problem and have tried the driver update twice, just having done it again. Because of having lots and lots and lots of problems with Retrospect and writing to dvds recently, I even bought a new driver for my applemac, and it is a supported one, so that cannot possibly be the problem. I have installed it (two days ago) and have burnt disks successfully. My os is 10.4.6. So when I suddenly started yet again to have trouble burning to dvd, I decided to do a check backup as it is quite new and therefore not to big to check. And now I find I have an "Internal consistency check failed: Assertion check at "elem.c-918". This is again after reinstalling the driver update. My driver is the Pioneer 111D. The disks I am currently using are Titanium Datawrite DVD+R. PLEASE can someone suggest something. Clearly, having bought a new driver, I have few other options. Retrospect used to be so stable and now I am really frustrated as I am unsure whether I can trust that my backups of my work, which are vital, are safe or not. Link to comment Share on other sites More sharing options...
CallMeDave Posted June 9, 2006 Report Share Posted June 9, 2006 Quote: My driver is the Pioneer 111D. The disks I am currently using are Titanium Datawrite DVD+R And the rest of your hardware/software configuration is... ? Link to comment Share on other sites More sharing options...
lindseystock Posted June 9, 2006 Report Share Posted June 9, 2006 Hello, is this what you mean: Machine Name: Power Mac G5 Machine Model: PowerMac7,3 CPU Type: PowerPC G5 (2.2) Number Of CPUs: 2 CPU Speed: 1.8 GHz L2 Cache (per CPU): 512 KB Memory: 1.5 GB Bus Speed: 900 MHz Boot ROM Version: 5.1.8f7 PIONEER DVD-RW DVR-111D: Firmware Revision: 1.19 Interconnect: ATAPI Burn Support: Yes (Unsupported) Profile Path: None Cache: 0 KB Reads DVD: Yes CD-Write: -R, -RW DVD-Write: -R, -RW Burn Underrun Protection CD: Yes Burn Underrun Protection DVD: Yes Write Strategies: CD-TAO, CD-SAO, CD-Raw, DVD-DAO Media: No Retrospect 6.1.126 with latest driver as suggested before in this thread. thanks Link to comment Share on other sites More sharing options...
lindseystock Posted June 9, 2006 Report Share Posted June 9, 2006 oh, please note that 111D does read/write DVD + and well as -. apparantly, this happens a lots on macs, the file info changes for some reason sometimes. thanks stockshoots. Link to comment Share on other sites More sharing options...
lindseystock Posted June 12, 2006 Report Share Posted June 12, 2006 any help would be grateful as Retrospect will not help me. After this, Retrospect crashed my disk so badly that it would not start again. I had to reinstall my OS. Why can they not help me then? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.