Have you turned off Virtual Memory and checked the amount of Ram allocated
to the retrospect app?
Dan.
----------
>From: Adrian Smith <[EMAIL PROTECTED]>
>To: "retro-talk" <[EMAIL PROTECTED]>
>Subject: SCSI Voodoo strikes...(continued)
>Date: Mon, Nov 13, 2000, 3:48 PM
>
> Hi,
> I posted the email below last Friday. Since then we have been
> trying to chase up some alternative cables and terminators but
> haven't got any yet...
>
> However, we have been able to get Retrospect to talk to the drive and
> perform a backup if we restart the computer and run Retrospect
> immediately. If we leave the computer running and wait for
> Restrospect to start automatically at 2am then we get the same 102
> error.
>
> So, is it possible the 102 error could be software related? Or is it
> still likely to be SCSI? Could there be some other problem with the
> computer?
>
> Any suggestions most welcome,
>
> Adrian Smith
>
> ******************************************************
> Adrian Smith (PhD Student) T CELL BIOLOGY GROUP
> Centenary Institute of Cancer Medicine & Cell Biology
> Locked Bag No.6 Newtown, NSW 2042
> AUSTRALIA.
> Ph: (02) 9565-6198 Fax: (02)-9565-6103
> ******************************************************
>
>
>>Hi all,
>> We have just set up a system consisting of a Sony DDS-4 tape
>>drive attached to 7300 with an AdvanSys UltraWide SCSI card in order
>>to back up the Macs in our lab. It has been working perfectly for
>>the last week, then suddenly last night Retrospect gave us a 102
>>error (trouble communicating) after copying 12 out 13 files on the
>>first volume in the script. Retrospect can still see the drive (as
>>can SCSIProbe etc) and recognise which tape is in it but gives a 102
>>error whenever we try to read or write to it...
>>
>>We have the list of things to try (ie cables, terminators, etc) but
>>this will take us a while as we don't have easy access to any other
>>cables or terminators.
>>
>>What I was actually interested in is why this problem might have
>>just happened in the middle of a backup (which was in the middle of
>>the night)? Is this normal for SCSI to just die like this? I would
>>have thought it would be more likely to occur after a shutdown or
>>something else changing?
>>
>>Any experiences, observations or suggestions welcome...
>>
>>Adrian Smith
>>
>>
>>
>>--
>>----------------------------------------------------------
>>To subscribe: [EMAIL PROTECTED]
>>To unsubscribe: [EMAIL PROTECTED]
>>Archives: <http://list.working-dogs.com/lists/retro-talk/>
>>
>>For urgent issues, please contact Dantz technical support directly at
>>[EMAIL PROTECTED] or 925.253.3050.
>
>
>
> --
> ----------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives: <http://list.working-dogs.com/lists/retro-talk/>
>
> For urgent issues, please contact Dantz technical support directly at
> [EMAIL PROTECTED] or 925.253.3050.
>
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://list.working-dogs.com/lists/retro-talk/>
For urgent issues, please contact Dantz technical support directly at
[EMAIL PROTECTED] or 925.253.3050.
