Jump to content

dvdramproblem

Members
  • Content count

    17
  • Joined

  • Last visited

  • Days Won

    5

dvdramproblem last won the day on September 22 2015

dvdramproblem had the most liked content!

Community Reputation

26 Excellent

About dvdramproblem

  • Rank
    Occasional Forum Poster
  1. Update: Mounted the XP in a Mac via NTFS-3G and accessed the files: again an eof error. Mounted it in Linux Mint and could copy them to the desktop, deleted the originals, and copied the copies to the original location. Now Retrospect has backed them up without complaint. Looks like everything is OK, but I am still a bit worried...
  2. Hello, Can you help me with the following problem: I get an end of file error ("-39") when backing up an xp partition through a Mac client. It's always the files perfc007.dat, perfc009.dat, perfh007.dat, and perfh009.dat. Running chkdsk on xp before retrying from the Mac didn't help. Virus scans found nothing (it's a freshly installed XP). Backup Machine: MacOS 10.5.8; Retrospect 6.1.230 with driver 6.1.16.100 Client Machine: MacOS 1.6.7; Retrospect Client 6.2.234. Is there a way to fix that? If not, are these files vital for XP? I understand they have to do with some performance measuring tool that I could survive without. Any ideas are greatly appreciated.
  3. Hello, Sorry for reposting this here, but the other forum seems not to be read by too many people.. I need to make a client running on Linux Mint remember the first access password between reboots. A check with "/usr/local/dantz/client/rcl status" returns "Retrospect client is not running". But "/usr/local/dantz/client/rcl start" exists in my "/etc/rc.local" file (last line before "exit 0", not commented out). Runing that command manually returns "First access password not set, use retroclient -setpass". After setting the password, backup works fine, but after every reboot it needs to be set again. The password had been set during install as well as manually several times. I tried a short one with only 9 letters (no numbers, umlauts, etc) -- no luck. A run of "/usr/local/dantz/client/rpm-post-install.sh" didn't fix it either. Retrospect client is v 7.6.100, runs on Linux Mint 9, Kernel 2.6.32-23-generic, GNOME 2.30.2 Now I am lost as to what to do to make this password stick. Being new to Linux, I might just overlook something very basic? Thanks for reading, d
  4. First Access Password Amnesia

    Hello, Please help to make the a client running on Linux Mint remember the first access password between reboots. A check with "/usr/local/dantz/client/rcl status" returns "Retrospect client is not running". But "/usr/local/dantz/client/rcl start" exists in my "/etc/rc.local" file (last line before "exit 0", not commented out). Runing that command manually it returns "First access password not set, use retroclient -setpass". After setting the password, backup works fine, but after a reboot it needs to be set again. The password had been set during install as well as manually several times. I tried a short one with only 9 letters (no numbers, umlauts, etc) -- no luck. A run of "/usr/local/dantz/client/rpm-post-install.sh" didn't fix it either. Retrospect client is v 7.6.100, runs on Linux Mint 9, Kernel 2.6.32-23-generic, GNOME 2.30.2 Now I am lost as to what to do to make this password stick. Being new to Linux, I might just overlook something very basic? Thanks for reading, d
  5. Ah, thanks for your explanations. I figured it had to do with Retrospect's own files and did some extended voodoo: ran uninstall from all installer versions in all languages that might have been installed on this particular machine, keeping all prefs etc, then reinstalled. A small test backup ran OK. BTW, the repaired catalog was needed because of a power out while it was in use for backup. Again, thanks for your explanations, I will keep them for reference. d.
  6. Hello, What is wrong with my Retrospect? During a manually started script backup, I got a message about a failed consistency check with error number "elem.c-928" and the script stopped. It was a normal Backup of the boot disk to a file on an external disk. Log says ... reading of file "..." not possible, error -43 ... ... Internal consistency check failed ... check at "elem.c-928" Software Mac OS X 10.5.8 (9L30) // Darwin 9.8.0 Retrospect Version: 6.1.230 Retrospect Driver Update, version 6.1.16.100 Hardware: PowerBook G4 17", PPC, 1.5 GHz, 2GB Backup to Seagate FreeAgent, directly connected through FireWire 800. Before Backup I had rebuilt the backup file and rebooted. Before that, backing up an OSX client to a different file on the same FW disk ran OK. All help will be greatly appreciated. d.
  7. Thank you for the fast reply! Sorry for answering so late, couldn't get to my mac earlier. It works fine now. Don't know how I came to think I had the latest Client update... d
  8. Hello, Please help! My Retrospect Client installs without complaining, but when I try to add it to the clients database it refuses the password and returns error 507. Testing its IP recognized the client with its correct name. Client: 6.1.130 on Mac OS 10.5.7 Intel. Retrospect: 6.1.230 on Mac OS 10.5.7 PPC. Both machines connect OK (afp, vnc in both directions) via Ethernet/Router. Both firewalls were set to allow all incoming. Observations: - Installing the client created a Firewall entry for ODSAgent (allow incoming) on the PPC, but not on the Intel machine. - Running Retrospect on the Intel displays the client without even testing, but not on the PPC machine. - The password of the PPC client is not accepted (error 507) on the Intel Retrospect either. How can I fix that? Thanx in advance. D
  9. Hello, my Retrospect behaves a little strange. It it set to do a daily backup at an early time, when the computer usually is still turned off. So it should catch up and run the script after startup, which it does. But -- twice! And the first time the backup is not successfull because of a "protected catalog", the second time it terminates OK. Other symptoms that might be related: - Once I caught 2 (!) Retrospect symbols in the cmd-tab (Applcation switcher) bar right after startup+login. - The RDU is listed 2 (!) times in the log, but only for the failed backup attempt. A typical log entry looks like this: Retrospect Version: 6.1.126 Gestartet am 08.10.2006 13:57 Uhr + Retrospect Driver Update, version 6.1.7.101 + Retrospect Driver Update, version 6.1.7.101 <-- twice! + Normales Backup mit XXXXX at 08.10.2006 13:58 Uhr Hinzufügen zum Backup-Set YYYYY nicht möglich: Der Katalog ist geschützt. <-- catalog protected?! 08.10.2006 13:58:30 Uhr: Ausführung unvollständig. <-- incomplete + Normales Backup mit XXXXX at 08.10.2006 13:58 Uhr nach Backup-Set YYYYY… - 08.10.2006 13:58:23 Uhr: Kopieren von ZZZZZ … <--copying, catalog now unprotected? Thisw happens on a PowerBook G4 17" with Mac OS X 10.4.7 (8J135). What is that for a phenomenon? Thank you for help and suggestions! Sam
  10. Me again -- another observation, may help to hunt down the problem: After a CD-RW backup, the CD-RW appears *twice* in Finder windows. Sam
  11. Hello, here is the missing data. Powerbook G4, 17", 1.5 GHz, 1 GB DDR SDRAM Panasonic/Matshita DVD-R UJ-825, Firmware DAM5 Greetings, Sam
  12. Hello, Retrospect refuses to do more than one backup per boot, or so it seems. After one backup is done, it hangs searching devices for about 5-7 minutes, then quits as it should do with that script. When it is restarted manually, it does not recognize a CD-RW disc that is already a member of the required backup set, and the "Eject" button only brings up a "Unloading" notification with no other effect. The hardware's eject key doesn't work either. After a reboot the disk is seen, the second backup works OK. MacOS 10.4.6 Powerbook G4 Retrospect Version: 6.1.126 Retrospect Driver Update, version 6.1.5.102 I am grateful for every help.
  13. Quote: Hey Sam, I believe that you need to go through the one time process of configuring your DVD Drive. In Retro, go to the Configure Tab and click on Devices. Select your drive and insert the media that you plan to use. [i'm not sure of this next step since I don't have a DVD in my drive at the monent but I think it's...] Then choose Format from the Devices Menu. Whatever the next step is it will be prety clear. The process can take some time but when it's completed you should be good to go. ReHey! Man, Clinton, you are quick! I had forgot to mention I had tried that, too, but from the dialogs I thought that configuring applies only to CDs and DVDs, not DVD-RAMs. Resulting error messages showed that Retrospect tried to treat the DVD-RAM as CD- or DVD-something. And the manual mentions configuring only with CDs and DVDs. As the manual says that removable media (like DVD-RAM) are to be formatted with the software/driver that came with the device, I tend to think now that the information in the device compatibility database is not complete: The statement saying the UJ-825 (Apple version) is fully supported omits the crucial information that Retrospect lacks the capacity to prepare the DVD-RAM discs it could use. But I may be wrong, the fact that a new blank came write protected could point to any stupidity on my side, something overlooked or so. Have a nice weekend! Sam
  14. Hello, Is here someone experienced in backing up an Apple Powerbook G4 to DVD-RAM thru the built-in “superdrive”? Somehow I can’t make it work although according to available Retrospect information it should be ok. I assume the error is the user but can’t find out what I’m doing wrong. Software: Used software is current versions (MacOS 10.4.5, Retrospect 6.1.126 with Driver Update 6.1.4.103). Burner: The backup device is a Panasonic/Matshita DVD-R UJ-825 with firmware DAM5. It works fine with CD or DVD media. The Retrospect device compatibility database says “qualified” and “Macintosh: This drive is supported with ... DVD-RAM media ...” Blanks: I tried blanks from three quality brands. A UDF formatted DVD-RAM blank can be mounted in the Finder, while apparently unformatted blanks (disk util shows only the burner, not the volume) can not. (This is normal behaviour, Apple does not allow its software to write to DVD-RAM.) Retrospect recognizes the UDF formatted blank as *write protected* (a fresh blank, how come?) and is unable to do anything with it. With the apparently unformatted blanks Retrospect does not find removable media at all. I assume Retrospect must be told to override the write protection (if it's real), or it must be enabled to erase the disks — but how do I do that? Grateful for help, Sam
  15. Hello, Natew and all, I have done some further testing, following Natews suggestions (Ignore Device ID, Removable Disk), on a clean system install (10.4.0) to exclude possible other causes. Of 3 blanks from different manufacturers, only the Panasonic blank gets mounted on the desktop. But in Restrospect it appears "write protected". It is the only one of the three showing a format (UDF) in Disk Util. Could it be that Retrospect *requires* pre-formatted UDF blanks? And that it has no own capacity to override a write protection? Or is the write protection caused by the missing DVD-RAM write capacity of the Finder -- why would a manufacturer sell blanks as write-protected? How would I enable Retrospect to write to and format a DVD-RAM? Still trying, Sam
×