bgrayjr Posted July 2, 2002 Report Share Posted July 2, 2002 I've applied all of the updates including 2.7 for macos. the vxa drive is not able to be found by the retrospect software. requires a restart of the vxa firewire device to see device again. one backup and the device is gone again. did not have these issues with the preview version. Link to comment Share on other sites More sharing options...
IrenaS Posted July 2, 2002 Report Share Posted July 2, 2002 Does the drive work under OS 9? Are there errors reported in the operations log? When the device is no longer visible, can the Apple System Profiler see the device? Have you done any device troubleshooting, such as trying a new cable or connecting the drive to a different port? If so and you get the same problem, please provide details on your configuration: Retrospect Version and build Computer Model and speed OS X version and build Device (from Retrospect's Configure > Devices > Device Status window) Device firmware (in the version column of the Device Status window) Device interface Media brand and size Other Devices Thanks, Irena Solomon Dantz Tech Support Link to comment Share on other sites More sharing options...
bgrayjr Posted July 11, 2002 Author Report Share Posted July 11, 2002 OS 9 is not an option, first of all. I'm running 10.1.4 OSX server. I am running Retrospect ver 5.0.205 with the update driver 2.7.102 The device is showing ID Firewire-A, Vendor Ecrix, Product VXA-1, Version 2959, Driver Ecrix VXA DC (5.01) The error is: Can't use server set A: Can't find any tape storage Devices.... Execution Incomplete. The device is only found after the firewire unit is powered off and on. However, it will dissapear before the next backup script runs. Ran in the preview version fine. Link to comment Share on other sites More sharing options...
IrenaS Posted July 11, 2002 Report Share Posted July 11, 2002 > When the device is no longer visible, can the Apple System Profiler see the device? > Have you done any device troubleshooting, such as trying a new cable or connecting the drive to a different port? Thanks, Irena Link to comment Share on other sites More sharing options...
bgrayjr Posted July 17, 2002 Author Report Share Posted July 17, 2002 apple system profiler shows the device as follows, but retrospect does not find the device. vxa-1 2959 vendor id D016 speed 200 mB/sec GUID 13637120d Vendor Name Ecrix Unit Version 66691 The retorspect version is 5.0.205 the update is 2.7.102 i've swapped cables and ports used. a firewire hard drive is now attached to the unit and functions properly on the same port the ecrix device was. Link to comment Share on other sites More sharing options...
shadowspawn Posted July 17, 2002 Report Share Posted July 17, 2002 What model of Macintosh? Does Retrospect crash at any point between when it can see the VXA unit and when it can't? Or report any other errors? (I have lost the VXA unit after a crash, but never lost the drive in the middle of a trouble free backup.) Does your VXA unit have native firewire, or are you using a SCSI-FireWire adaptor? If an adaptor, you are officially unsupported, but inquiring minds still want to know which one? Link to comment Share on other sites More sharing options...
ptoly Posted July 23, 2002 Report Share Posted July 23, 2002 I am pretty much the same problems with my VXA Firewire drive freezing Retrospect and the OS. The specs: Beige G3 running Retrospect 5.0.205, driver 2.7.102, OS X 10.1.5, 352 MB RAM, brand new VXA-1 unit with onboard firewire Retro starts up fine, runs a back up then seems to loose sight of the VXA drive and hangs with a beach ball. If I let the computer stay up running the whole system freezes. Tried changing firewire ports and cables, stil happens. No report in the Operation Log of crashing or loosing site of the VXA unit. Rebooting is the only way to get things back on track. OS 9 is also not an option with me. It appears that Retro is eating up all the CPU cycles trying to find the VXA unit. I have not been able to check out the firmware of the VXA because I have not figured out a way to do this on a firewire VXA. Anyone know? Thanks Link to comment Share on other sites More sharing options...
pjcoop Posted July 26, 2002 Report Share Posted July 26, 2002 Hi, This may be way off track but I had 205 errors on my Onstream FireWire drive. I fixed it by upgrading to the latest Driver Update and also I made sure that in Energy Saver everything was set to 'never'. I think that Energy Saver kicking in caused the loss of contact with the drive. Hope this helps a little Paul Link to comment Share on other sites More sharing options...
ChristianM Posted July 29, 2002 Report Share Posted July 29, 2002 You haven't happened to have been using this Mac to do Firewire development using Apple's Firewire SDK have you? One of the things the Firewire SDK has you do is to rename the file /System/Library/Extensions/IOFireWireSerialBusProtocolTransport.kext to .disable. This allows you to debug a device/driver that you are developing while keeping the operating system from grabbing your device. This also prevents Retrospect from finding VXA firewire drives. I know. I had that problem on a development machine. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.