Jump to content

new version 6.1.138 does not work for me, going back to 126 and old drivers


Recommended Posts

new version does not work for on Apple superdrive (PIONEER DVD-RW DVR-106D FW:A606, OSX version 10.4.11):

 

* Retrospect version 6.1.138

+ Retrospect Driver Update, version 6.1.13.101

Trouble writing: “1-Backup Set G” (0), error 100 (device rejected command).

 

tried a newer old version:

* Retrospect version 6.1.126

+ Retrospect Driver Update, version 6.1.12.101

Trouble writing: “10-Backup Set F” (3407872000), error 100 (device rejected command).

 

going back in time ... found this works for me:

* Retrospect version 6.1.126

+ Retrospect Driver Update, version 6.1.5.102

Link to comment
Share on other sites

  • 3 weeks later...

I just discovered this as well, though I didn't find your post when I was searching. I had the same problem with OS X Server v10.4.8. I couldn't even install the previous version of Retrospect over the current version to get it working again. I had to resort to a bootable backup of the system BEFORE updating Retrospect to get it working again.

Link to comment
Share on other sites

Quote:

I couldn't even install the previous version of Retrospect over the current version to get it working again. I had to resort to a bootable backup of the system BEFORE updating Retrospect to get it working again.

 


 

With the exception of the File System Plugin that Retrospect uses to allow Members of a CD/DVD Backup Set to mount on the Finder Desktop, Retrospect contains nothing other then the items in the /Applications/Retrospect and /Library/Preferences/Retrospect/ folders.

 

Falling back to a previous server backup state probably was overkill.

 

 

Dave

Link to comment
Share on other sites

Quote:

With the exception of the File System Plugin that Retrospect uses to allow Members of a CD/DVD Backup Set to mount on the Finder Desktop, Retrospect contains nothing other then the items in the /Applications/Retrospect and /Library/Preferences/Retrospect/ folders.

 

Falling back to a previous server backup state probably was overkill.

 


This may be true. Yet I had backups that I needed to run, and this method worked, so I went with it.

 

Let's work under the premise that reverting to a previous server backup state wasn't necessary. What I did was install v6.1.126 over v6.1.138. As I understand what you typed above, this means that the contents of /Applications/Retrospect would have been overwritten, correct? So then either the files within /Library/Preferences/Retrospect were corrupted by the installation of v6.1.138, or the File System Plugin from v6.1.138 has issues.

 

Where would the File System Plugin be located? If that would not cause these issues, where else should someone like myself be looking?

Link to comment
Share on other sites

Quote:

As I understand what you typed above, this means that the contents of /Applications/Retrospect would have been overwritten, correct?

 


 

No.

 

If /Applications/Retrospect/ contains a "Retrospect 6.1 Driver Update" file, running the installer will _not_ delete it.

 

And if /Library/Preferences/Retrospect/ contains a custom optical drive configuration file, the installer will leave _that_ in place too.

 

So it's impossible, without knowing more about your unworking install _and_ your working install to know what components (Retrospect application package, Retrospect Device Update, Retrospect device configuration file) might be at fault.

Link to comment
Share on other sites

Quote:

You can use 6.1.138 with the older RDU, and that should work okay for you.

 


Thank you for providing that bit of information.

Quote:

The newest RDU doesn't work with all media types, resulting in error messages.

 


Is this a known issue that EMC is going to address in a future RDU release, or is this the way it is?

Link to comment
Share on other sites

Quote:

Quote:

As I understand what you typed above, this means that the contents of /Applications/Retrospect would have been overwritten, correct?

 


 

No.

 

If /Applications/Retrospect/ contains a "Retrospect 6.1 Driver Update" file, running the installer will _not_ delete it.

 


Then how does one explain the fact that the "Retrospect 6.1 Driver Update" file on the other hard drive in our server is not the same as the one that I had installed with v6.1.126? It appears to me that installing a later version of Retrospect overwrote this file, but that installing a prior version of Retrospect did NOT overwrite this file. Is that plausible?

Quote:

 

And if /Library/Preferences/Retrospect/ contains a custom optical drive configuration file, the installer will leave _that_ in place too.

 


This is good to know, even though we do not have a custom optical drive configuration file.

Quote:

So it's impossible, without knowing more about your unworking install _and_ your working install to know what components (Retrospect application package, Retrospect Device Update, Retrospect device configuration file) might be at fault.

 


The unworking install is v6.1.138 with a Retrospect 6.1 Driver Update v6.1.13.101. The working install is v6.1.126 with a Retrospect 6.1 Driver Update v6.1.9.102. Neither install has a custom Retrospect device configuration file.

Link to comment
Share on other sites

Quote:

Where would the File System Plugin be located?

 


/System/Library/Filesystems/retrospectcd.fs

(which is a folder containing a bunch of files, including a kext).

 

There is also a related link:

/sbin/mount_retrospectcd

to one of the files in /System/Library/Filesystems/retrospectcd.fs

 

Unless you do a custom install and say you don't want it, you get the file system plugin by default.

 

russ

Link to comment
Share on other sites

Quote:

Then how does one explain the fact that the "Retrospect 6.1 Driver Update" file on the other hard drive in our server is not the same as the one that I had installed with v6.1.126?

 


 

Because I was totally wrong when I suggested that the Retrospect Installer did not also install an RDU. It does. If I were old enough to drink, I'd slam back a couple of scotch rocks right about now to dull the pain...

 

> The unworking install is v6.1.138 with a Retrospect 6.1 Driver Update v6.1.13.101. The working

> install is v6.1.126 with a Retrospect 6.1 Driver Update v6.1.9.102

 

The best test would have been, when booted from the OS X install that did not work, to simply leave the 6.1.138 application alone and replace the RDU with the older 6.1.9.102.

 

Or, if you're interested, reinstalling 6.1.13.101 (a Custom Install of Application only) in your current OS X install and then replacing the newer RDU with a saved copy of the old RDU (you can do some temporary naming changes to the old file so that it doesn't get overwritten by the installer).

 

Robin said it first (and best) above:

"You can use 6.1.138 with the older RDU, and that should work okay for you."

Link to comment
Share on other sites

Just to chime in here...

 

RDU version 6.1.138 doesn't work for me either. I had to go back to rdu619102.dmg (6.1.9.102). When I put a DVD-R in the drive to do an incremental backup it told me the device or media was write-protected.

 

My configuration is: Dual 1GHz G4 PowerMac, Mac OS 10.4.11

The drive is:

PIONEER DVD-RW DVR-104:

 

Model: PIONEER DVD-RW DVR-104

Revision: A227

Serial Number: BFDL130158WL

Detachable Drive: No

Protocol: ATAPI

Unit Number: 0

Socket Type: Internal

Burn Support: Yes (Apple Shipped/Supported)

Cache: 2000 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, DVD-DAO

Media: No

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...