Keep getting "Error 84" - Related to SCSI issue? - Veritas Net Backup

This is a discussion on Keep getting "Error 84" - Related to SCSI issue? - Veritas Net Backup ; Hi all, We're running NetBackup BusinesServer v.3.3 on a Sun Box with Solaris 2.6. The box is connected via SCSI straight to a Qualstar TLS-4000 tape robot with an AIT-2 drive. We've been working with Veritas on fixing a number ...

+ Reply to Thread
Results 1 to 17 of 17

Thread: Keep getting "Error 84" - Related to SCSI issue?

  1. Keep getting "Error 84" - Related to SCSI issue?

    Hi all,

    We're running NetBackup BusinesServer v.3.3 on a Sun Box with Solaris 2.6.
    The box is connected via SCSI straight to a Qualstar TLS-4000 tape robot
    with an AIT-2 drive.

    We've been working with Veritas on fixing a number of issues regarding our
    setup, but now we are stumped on this one. We keep getting an 84 error
    sometimes when backups are run. A know it's not a problem with the tapes, as
    they have been replaced with brand new ones, and the drive has been cleaned.
    I'm thinking that this may be an SCSI issue, as in var/adm/messages, we keep
    getting the following ouput daily:

    Sep 17 11:02:45 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/st@1,0
    (st1):
    Sep 17 11:02:45 buster unix: SCSI transport failed: reason
    'unexpected_bus_free': giving up
    Sep 17 11:03:58 buster unix: fas: 1.0: cdb=[ 0x3 0x0 0x0 0x0 0xc 0x0 ]
    Sep 17 11:03:58 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000 (fas0):
    Sep 17 11:03:58 buster unix: Connected command timeout for Target 1.0
    Sep 17 11:03:58 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@3,0
    (sd3):
    Sep 17 11:03:58 buster unix: SCSI transport failed: reason 'reset':
    retrying command
    Sep 17 11:03:58 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@c,0
    (sd11):
    Sep 17 11:03:58 buster unix: SCSI transport failed: reason 'reset':
    retrying command

    Can anyone tell me if this is linked the the backup failures? The robot and
    drive are the only devices linked to the SCSI cable. Prehaps a bad cable?
    The cable is under the minimum length, and appears to have the correct
    terminators. Veritas are stumped by this one, so i'm hoping someone here
    will have some clues.


    Thanks in advance,
    --
    --
    Robert Chatfield



  2. Re: Keep getting "Error 84" - Related to SCSI issue?


    > Sep 17 11:02:45 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/st@1,0
    > (st1):
    > Sep 17 11:02:45 buster unix: SCSI transport failed: reason
    > 'unexpected_bus_free': giving up
    > Sep 17 11:03:58 buster unix: fas: 1.0: cdb=[ 0x3 0x0 0x0 0x0 0xc 0x0 ]
    > Sep 17 11:03:58 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000 (fas0):
    > Sep 17 11:03:58 buster unix: Connected command timeout for Target 1.0
    > Sep 17 11:03:58 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@3,0
    > (sd3):
    > Sep 17 11:03:58 buster unix: SCSI transport failed: reason 'reset':
    > retrying command
    > Sep 17 11:03:58 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@c,0
    > (sd11):
    > Sep 17 11:03:58 buster unix: SCSI transport failed: reason 'reset':
    > retrying command


    I do not know about sun architecture but tape drives and hard disk are
    encountering some scsi issue ("sd " and "st")
    are they attached to the same controller ?
    If you have a lot of devices on that SCSI bus, you may be getting too much
    contention when the bus is busy -
    this happens especially when several of the devices have different operating
    speeds (got any CD-ROMs on there?)
    If the disks seem to be OK, you can slow down the bus, which might solve
    your problem.
    What about testing the robot+tape and the cabling on another system to find
    out if the controller is in cause ?
    Or just changing the controller ?
    How many devices are attached to the same scsi bus ?





  3. Re: Keep getting "Error 84" - Related to SCSI issue?


    > Sep 17 11:02:45 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/st@1,0
    > (st1):
    > Sep 17 11:02:45 buster unix: SCSI transport failed: reason
    > 'unexpected_bus_free': giving up
    > Sep 17 11:03:58 buster unix: fas: 1.0: cdb=[ 0x3 0x0 0x0 0x0 0xc 0x0 ]
    > Sep 17 11:03:58 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000 (fas0):
    > Sep 17 11:03:58 buster unix: Connected command timeout for Target 1.0
    > Sep 17 11:03:58 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@3,0
    > (sd3):
    > Sep 17 11:03:58 buster unix: SCSI transport failed: reason 'reset':
    > retrying command
    > Sep 17 11:03:58 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@c,0
    > (sd11):
    > Sep 17 11:03:58 buster unix: SCSI transport failed: reason 'reset':
    > retrying command


    I do not know about sun architecture but tape drives and hard disk are
    encountering some scsi issue ("sd " and "st")
    are they attached to the same controller ?
    If you have a lot of devices on that SCSI bus, you may be getting too much
    contention when the bus is busy -
    this happens especially when several of the devices have different operating
    speeds (got any CD-ROMs on there?)
    If the disks seem to be OK, you can slow down the bus, which might solve
    your problem.
    What about testing the robot+tape and the cabling on another system to find
    out if the controller is in cause ?
    Or just changing the controller ?
    How many devices are attached to the same scsi bus ?





  4. Re: Keep getting "Error 84" - Related to SCSI issue?

    As far as I know, the tape robot/drive and the disks are the only devices on
    the SCSI bus, apart from possibly the internal cd drive on the box. I'm
    going to try and find a new SCSI cable to try and solve the issue. The only
    thing that concerns me is if this is indicative of a dodgy disk, which would
    not be good.
    "Zorro" wrote in message news:3bab7c21@hronntp01....
    >
    > > Sep 17 11:02:45 buster unix: WARNING:

    /sbus@3,0/SUNW,fas@3,8800000/st@1,0
    > > (st1):
    > > Sep 17 11:02:45 buster unix: SCSI transport failed: reason
    > > 'unexpected_bus_free': giving up
    > > Sep 17 11:03:58 buster unix: fas: 1.0: cdb=[ 0x3 0x0 0x0 0x0 0xc 0x0 ]
    > > Sep 17 11:03:58 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000

    (fas0):
    > > Sep 17 11:03:58 buster unix: Connected command timeout for Target 1.0
    > > Sep 17 11:03:58 buster unix: WARNING:

    /sbus@3,0/SUNW,fas@3,8800000/sd@3,0
    > > (sd3):
    > > Sep 17 11:03:58 buster unix: SCSI transport failed: reason 'reset':
    > > retrying command
    > > Sep 17 11:03:58 buster unix: WARNING:

    /sbus@3,0/SUNW,fas@3,8800000/sd@c,0
    > > (sd11):
    > > Sep 17 11:03:58 buster unix: SCSI transport failed: reason 'reset':
    > > retrying command

    >
    > I do not know about sun architecture but tape drives and hard disk are
    > encountering some scsi issue ("sd " and "st")
    > are they attached to the same controller ?
    > If you have a lot of devices on that SCSI bus, you may be getting too much
    > contention when the bus is busy -
    > this happens especially when several of the devices have different

    operating
    > speeds (got any CD-ROMs on there?)
    > If the disks seem to be OK, you can slow down the bus, which might solve
    > your problem.
    > What about testing the robot+tape and the cabling on another system to

    find
    > out if the controller is in cause ?
    > Or just changing the controller ?
    > How many devices are attached to the same scsi bus ?
    >
    >
    >
    >




  5. Re: Keep getting "Error 84" - Related to SCSI issue?

    As far as I know, the tape robot/drive and the disks are the only devices on
    the SCSI bus, apart from possibly the internal cd drive on the box. I'm
    going to try and find a new SCSI cable to try and solve the issue. The only
    thing that concerns me is if this is indicative of a dodgy disk, which would
    not be good.
    "Zorro" wrote in message news:3bab7c21@hronntp01....
    >
    > > Sep 17 11:02:45 buster unix: WARNING:

    /sbus@3,0/SUNW,fas@3,8800000/st@1,0
    > > (st1):
    > > Sep 17 11:02:45 buster unix: SCSI transport failed: reason
    > > 'unexpected_bus_free': giving up
    > > Sep 17 11:03:58 buster unix: fas: 1.0: cdb=[ 0x3 0x0 0x0 0x0 0xc 0x0 ]
    > > Sep 17 11:03:58 buster unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000

    (fas0):
    > > Sep 17 11:03:58 buster unix: Connected command timeout for Target 1.0
    > > Sep 17 11:03:58 buster unix: WARNING:

    /sbus@3,0/SUNW,fas@3,8800000/sd@3,0
    > > (sd3):
    > > Sep 17 11:03:58 buster unix: SCSI transport failed: reason 'reset':
    > > retrying command
    > > Sep 17 11:03:58 buster unix: WARNING:

    /sbus@3,0/SUNW,fas@3,8800000/sd@c,0
    > > (sd11):
    > > Sep 17 11:03:58 buster unix: SCSI transport failed: reason 'reset':
    > > retrying command

    >
    > I do not know about sun architecture but tape drives and hard disk are
    > encountering some scsi issue ("sd " and "st")
    > are they attached to the same controller ?
    > If you have a lot of devices on that SCSI bus, you may be getting too much
    > contention when the bus is busy -
    > this happens especially when several of the devices have different

    operating
    > speeds (got any CD-ROMs on there?)
    > If the disks seem to be OK, you can slow down the bus, which might solve
    > your problem.
    > What about testing the robot+tape and the cabling on another system to

    find
    > out if the controller is in cause ?
    > Or just changing the controller ?
    > How many devices are attached to the same scsi bus ?
    >
    >
    >
    >




  6. Re: Keep getting "Error 84" - Related to SCSI issue?


    "Robert Chatfield" wrote in message
    news:3baf60b9$1@hronntp01....
    > As far as I know, the tape robot/drive and the disks are the only devices

    on
    > the SCSI bus, apart from possibly the internal cd drive on the box. I'm
    > going to try and find a new SCSI cable to try and solve the issue. The

    only
    > thing that concerns me is if this is indicative of a dodgy disk, which

    would
    > not be good.


    /sbus@3,0/SUNW,fas@3,8800000/

    unfortunately I do not have my old solaris administrator exam guide which
    has an excellent chapter explaining how to interpret this common denominator
    but on top of my head to me it looks like st and sd devices fails on the
    same SCSI adapter (maybe not a cabling issue ) ...




  7. Re: Keep getting "Error 84" - Related to SCSI issue?


    "Robert Chatfield" wrote in message
    news:3baf60b9$1@hronntp01....
    > As far as I know, the tape robot/drive and the disks are the only devices

    on
    > the SCSI bus, apart from possibly the internal cd drive on the box. I'm
    > going to try and find a new SCSI cable to try and solve the issue. The

    only
    > thing that concerns me is if this is indicative of a dodgy disk, which

    would
    > not be good.


    /sbus@3,0/SUNW,fas@3,8800000/

    unfortunately I do not have my old solaris administrator exam guide which
    has an excellent chapter explaining how to interpret this common denominator
    but on top of my head to me it looks like st and sd devices fails on the
    same SCSI adapter (maybe not a cabling issue ) ...




  8. Re: Keep getting "Error 84" - Related to SCSI issue?

    I've run Sun Explorer, & I've sent the output on to my support contact. I
    guess hopefully they'll find out what the exact problem is. Thanks for the
    advice, it's helped close in on the cause. I'll post here when I find out
    more, in case anyone else is experiencing similar problems.

    Robert

    "Zorro" wrote in message news:3baf7511$1@hronntp01....
    >
    > "Robert Chatfield" wrote in message
    > news:3baf60b9$1@hronntp01....
    > > As far as I know, the tape robot/drive and the disks are the only

    devices
    > on
    > > the SCSI bus, apart from possibly the internal cd drive on the box. I'm
    > > going to try and find a new SCSI cable to try and solve the issue. The

    > only
    > > thing that concerns me is if this is indicative of a dodgy disk, which

    > would
    > > not be good.

    >
    > /sbus@3,0/SUNW,fas@3,8800000/
    >
    > unfortunately I do not have my old solaris administrator exam guide which
    > has an excellent chapter explaining how to interpret this common

    denominator
    > but on top of my head to me it looks like st and sd devices fails on the
    > same SCSI adapter (maybe not a cabling issue ) ...
    >
    >
    >




  9. Re: Keep getting "Error 84" - Related to SCSI issue?

    I've run Sun Explorer, & I've sent the output on to my support contact. I
    guess hopefully they'll find out what the exact problem is. Thanks for the
    advice, it's helped close in on the cause. I'll post here when I find out
    more, in case anyone else is experiencing similar problems.

    Robert

    "Zorro" wrote in message news:3baf7511$1@hronntp01....
    >
    > "Robert Chatfield" wrote in message
    > news:3baf60b9$1@hronntp01....
    > > As far as I know, the tape robot/drive and the disks are the only

    devices
    > on
    > > the SCSI bus, apart from possibly the internal cd drive on the box. I'm
    > > going to try and find a new SCSI cable to try and solve the issue. The

    > only
    > > thing that concerns me is if this is indicative of a dodgy disk, which

    > would
    > > not be good.

    >
    > /sbus@3,0/SUNW,fas@3,8800000/
    >
    > unfortunately I do not have my old solaris administrator exam guide which
    > has an excellent chapter explaining how to interpret this common

    denominator
    > but on top of my head to me it looks like st and sd devices fails on the
    > same SCSI adapter (maybe not a cabling issue ) ...
    >
    >
    >




  10. Re: Keep getting "Error 84" - I got it on FC/SAN too !!!

    I also noticed this error and 86 'media position' in a SAN configuration,
    using Dlt7K, 2 Crossroad routers, Brocade SW and Qlogic HBAs.. this has been
    going for a long time and the only indication we saw less and less media
    errors when we eliminated most of the 'frozen' tapes and replaced with New
    ones. nevertheless, I still suspect there's more to it than Bad media.. We
    tried using one router ( 4 drives group) at a time and we noticed a
    much-much better performance and NO Errors at all... I thought we had a bad
    router but, when switched to 2nd group - it ran just fine as well. As i
    write, we are still debugging this problem and for this reason I searched
    this group for ideas to share. If you find something worth sharing I would
    like to read it.
    Tnx, Eli.


    "Robert Chatfield" wrote in message
    news:3bb05569@hronntp01....
    > I've run Sun Explorer, & I've sent the output on to my support contact. I
    > guess hopefully they'll find out what the exact problem is. Thanks for the
    > advice, it's helped close in on the cause. I'll post here when I find out
    > more, in case anyone else is experiencing similar problems.
    >
    > Robert
    >
    > "Zorro" wrote in message

    news:3baf7511$1@hronntp01....
    > >
    > > "Robert Chatfield" wrote in message
    > > news:3baf60b9$1@hronntp01....
    > > > As far as I know, the tape robot/drive and the disks are the only

    > devices
    > > on
    > > > the SCSI bus, apart from possibly the internal cd drive on the box.

    I'm
    > > > going to try and find a new SCSI cable to try and solve the issue. The

    > > only
    > > > thing that concerns me is if this is indicative of a dodgy disk, which

    > > would
    > > > not be good.

    > >
    > > /sbus@3,0/SUNW,fas@3,8800000/
    > >
    > > unfortunately I do not have my old solaris administrator exam guide

    which
    > > has an excellent chapter explaining how to interpret this common

    > denominator
    > > but on top of my head to me it looks like st and sd devices fails on the
    > > same SCSI adapter (maybe not a cabling issue ) ...
    > >
    > >
    > >

    >
    >




  11. Re: Keep getting "Error 84" - I got it on FC/SAN too !!!

    I also noticed this error and 86 'media position' in a SAN configuration,
    using Dlt7K, 2 Crossroad routers, Brocade SW and Qlogic HBAs.. this has been
    going for a long time and the only indication we saw less and less media
    errors when we eliminated most of the 'frozen' tapes and replaced with New
    ones. nevertheless, I still suspect there's more to it than Bad media.. We
    tried using one router ( 4 drives group) at a time and we noticed a
    much-much better performance and NO Errors at all... I thought we had a bad
    router but, when switched to 2nd group - it ran just fine as well. As i
    write, we are still debugging this problem and for this reason I searched
    this group for ideas to share. If you find something worth sharing I would
    like to read it.
    Tnx, Eli.


    "Robert Chatfield" wrote in message
    news:3bb05569@hronntp01....
    > I've run Sun Explorer, & I've sent the output on to my support contact. I
    > guess hopefully they'll find out what the exact problem is. Thanks for the
    > advice, it's helped close in on the cause. I'll post here when I find out
    > more, in case anyone else is experiencing similar problems.
    >
    > Robert
    >
    > "Zorro" wrote in message

    news:3baf7511$1@hronntp01....
    > >
    > > "Robert Chatfield" wrote in message
    > > news:3baf60b9$1@hronntp01....
    > > > As far as I know, the tape robot/drive and the disks are the only

    > devices
    > > on
    > > > the SCSI bus, apart from possibly the internal cd drive on the box.

    I'm
    > > > going to try and find a new SCSI cable to try and solve the issue. The

    > > only
    > > > thing that concerns me is if this is indicative of a dodgy disk, which

    > > would
    > > > not be good.

    > >
    > > /sbus@3,0/SUNW,fas@3,8800000/
    > >
    > > unfortunately I do not have my old solaris administrator exam guide

    which
    > > has an excellent chapter explaining how to interpret this common

    > denominator
    > > but on top of my head to me it looks like st and sd devices fails on the
    > > same SCSI adapter (maybe not a cabling issue ) ...
    > >
    > >
    > >

    >
    >




  12. Re: Keep getting "Error 84" - I got it on FC/SAN too !!!

    Well, Sun sent out an engineer to replace the I/O board on the box, as they
    thought that this was the root of the errors, based on the Explorer output.
    That was last Friday, and since then, no 84 errors have arisen, all the
    backups have gone fine. The only problem is, the same error messages are
    still coming up in var/adm/messages regarding SCSI! At least the backups are
    working again, that's one thing. My advice to you would be to continue
    looking at the hardware as a cause of this problem; if we had followed the
    Veritas advice to replace every tape that threw up an 84, it could have got
    quite costly!

    Regards,

    Robert

    "EliD" wrote in message news:3bbbbf19$1@hronntp01....
    > I also noticed this error and 86 'media position' in a SAN configuration,
    > using Dlt7K, 2 Crossroad routers, Brocade SW and Qlogic HBAs.. this has

    been
    > going for a long time and the only indication we saw less and less media
    > errors when we eliminated most of the 'frozen' tapes and replaced with New
    > ones. nevertheless, I still suspect there's more to it than Bad media.. We
    > tried using one router ( 4 drives group) at a time and we noticed a
    > much-much better performance and NO Errors at all... I thought we had a

    bad
    > router but, when switched to 2nd group - it ran just fine as well. As i
    > write, we are still debugging this problem and for this reason I searched
    > this group for ideas to share. If you find something worth sharing I would
    > like to read it.
    > Tnx, Eli.
    >
    >
    > "Robert Chatfield" wrote in message
    > news:3bb05569@hronntp01....
    > > I've run Sun Explorer, & I've sent the output on to my support contact.

    I
    > > guess hopefully they'll find out what the exact problem is. Thanks for

    the
    > > advice, it's helped close in on the cause. I'll post here when I find

    out
    > > more, in case anyone else is experiencing similar problems.
    > >
    > > Robert
    > >
    > > "Zorro" wrote in message

    > news:3baf7511$1@hronntp01....
    > > >
    > > > "Robert Chatfield" wrote in message
    > > > news:3baf60b9$1@hronntp01....
    > > > > As far as I know, the tape robot/drive and the disks are the only

    > > devices
    > > > on
    > > > > the SCSI bus, apart from possibly the internal cd drive on the box.

    > I'm
    > > > > going to try and find a new SCSI cable to try and solve the issue.

    The
    > > > only
    > > > > thing that concerns me is if this is indicative of a dodgy disk,

    which
    > > > would
    > > > > not be good.
    > > >
    > > > /sbus@3,0/SUNW,fas@3,8800000/
    > > >
    > > > unfortunately I do not have my old solaris administrator exam guide

    > which
    > > > has an excellent chapter explaining how to interpret this common

    > > denominator
    > > > but on top of my head to me it looks like st and sd devices fails on

    the
    > > > same SCSI adapter (maybe not a cabling issue ) ...
    > > >
    > > >
    > > >

    > >
    > >

    >
    >




  13. Re: Keep getting "Error 84" - I got it on FC/SAN too !!!

    Well, Sun sent out an engineer to replace the I/O board on the box, as they
    thought that this was the root of the errors, based on the Explorer output.
    That was last Friday, and since then, no 84 errors have arisen, all the
    backups have gone fine. The only problem is, the same error messages are
    still coming up in var/adm/messages regarding SCSI! At least the backups are
    working again, that's one thing. My advice to you would be to continue
    looking at the hardware as a cause of this problem; if we had followed the
    Veritas advice to replace every tape that threw up an 84, it could have got
    quite costly!

    Regards,

    Robert

    "EliD" wrote in message news:3bbbbf19$1@hronntp01....
    > I also noticed this error and 86 'media position' in a SAN configuration,
    > using Dlt7K, 2 Crossroad routers, Brocade SW and Qlogic HBAs.. this has

    been
    > going for a long time and the only indication we saw less and less media
    > errors when we eliminated most of the 'frozen' tapes and replaced with New
    > ones. nevertheless, I still suspect there's more to it than Bad media.. We
    > tried using one router ( 4 drives group) at a time and we noticed a
    > much-much better performance and NO Errors at all... I thought we had a

    bad
    > router but, when switched to 2nd group - it ran just fine as well. As i
    > write, we are still debugging this problem and for this reason I searched
    > this group for ideas to share. If you find something worth sharing I would
    > like to read it.
    > Tnx, Eli.
    >
    >
    > "Robert Chatfield" wrote in message
    > news:3bb05569@hronntp01....
    > > I've run Sun Explorer, & I've sent the output on to my support contact.

    I
    > > guess hopefully they'll find out what the exact problem is. Thanks for

    the
    > > advice, it's helped close in on the cause. I'll post here when I find

    out
    > > more, in case anyone else is experiencing similar problems.
    > >
    > > Robert
    > >
    > > "Zorro" wrote in message

    > news:3baf7511$1@hronntp01....
    > > >
    > > > "Robert Chatfield" wrote in message
    > > > news:3baf60b9$1@hronntp01....
    > > > > As far as I know, the tape robot/drive and the disks are the only

    > > devices
    > > > on
    > > > > the SCSI bus, apart from possibly the internal cd drive on the box.

    > I'm
    > > > > going to try and find a new SCSI cable to try and solve the issue.

    The
    > > > only
    > > > > thing that concerns me is if this is indicative of a dodgy disk,

    which
    > > > would
    > > > > not be good.
    > > >
    > > > /sbus@3,0/SUNW,fas@3,8800000/
    > > >
    > > > unfortunately I do not have my old solaris administrator exam guide

    > which
    > > > has an excellent chapter explaining how to interpret this common

    > > denominator
    > > > but on top of my head to me it looks like st and sd devices fails on

    the
    > > > same SCSI adapter (maybe not a cabling issue ) ...
    > > >
    > > >
    > > >

    > >
    > >

    >
    >




  14. Re: Keep getting "Error 84" - I got it on FC/SAN too !!!

    thanks for the info. we are going to look into it as well the way you did.
    hopefully, this will fix the problem here too.
    Eli.
    "Robert Chatfield" wrote in message
    news:3bbc45dc@hronntp01....
    > Well, Sun sent out an engineer to replace the I/O board on the box, as

    they
    > thought that this was the root of the errors, based on the Explorer

    output.
    > That was last Friday, and since then, no 84 errors have arisen, all the
    > backups have gone fine. The only problem is, the same error messages are
    > still coming up in var/adm/messages regarding SCSI! At least the backups

    are
    > working again, that's one thing. My advice to you would be to continue
    > looking at the hardware as a cause of this problem; if we had followed the
    > Veritas advice to replace every tape that threw up an 84, it could have

    got
    > quite costly!
    >
    > Regards,
    >
    > Robert
    >
    > "EliD" wrote in message news:3bbbbf19$1@hronntp01....
    > > I also noticed this error and 86 'media position' in a SAN

    configuration,
    > > using Dlt7K, 2 Crossroad routers, Brocade SW and Qlogic HBAs.. this has

    > been
    > > going for a long time and the only indication we saw less and less media
    > > errors when we eliminated most of the 'frozen' tapes and replaced with

    New
    > > ones. nevertheless, I still suspect there's more to it than Bad media..

    We
    > > tried using one router ( 4 drives group) at a time and we noticed a
    > > much-much better performance and NO Errors at all... I thought we had a

    > bad
    > > router but, when switched to 2nd group - it ran just fine as well. As i
    > > write, we are still debugging this problem and for this reason I

    searched
    > > this group for ideas to share. If you find something worth sharing I

    would
    > > like to read it.
    > > Tnx, Eli.
    > >
    > >
    > > "Robert Chatfield" wrote in message
    > > news:3bb05569@hronntp01....
    > > > I've run Sun Explorer, & I've sent the output on to my support

    contact.
    > I
    > > > guess hopefully they'll find out what the exact problem is. Thanks for

    > the
    > > > advice, it's helped close in on the cause. I'll post here when I find

    > out
    > > > more, in case anyone else is experiencing similar problems.
    > > >
    > > > Robert
    > > >
    > > > "Zorro" wrote in message

    > > news:3baf7511$1@hronntp01....
    > > > >
    > > > > "Robert Chatfield" wrote in message
    > > > > news:3baf60b9$1@hronntp01....
    > > > > > As far as I know, the tape robot/drive and the disks are the only
    > > > devices
    > > > > on
    > > > > > the SCSI bus, apart from possibly the internal cd drive on the

    box.
    > > I'm
    > > > > > going to try and find a new SCSI cable to try and solve the issue.

    > The
    > > > > only
    > > > > > thing that concerns me is if this is indicative of a dodgy disk,

    > which
    > > > > would
    > > > > > not be good.
    > > > >
    > > > > /sbus@3,0/SUNW,fas@3,8800000/
    > > > >
    > > > > unfortunately I do not have my old solaris administrator exam guide

    > > which
    > > > > has an excellent chapter explaining how to interpret this common
    > > > denominator
    > > > > but on top of my head to me it looks like st and sd devices fails on

    > the
    > > > > same SCSI adapter (maybe not a cabling issue ) ...
    > > > >
    > > > >
    > > > >
    > > >
    > > >

    > >
    > >

    >
    >




  15. Re: Keep getting "Error 84" - I got it on FC/SAN too !!!

    thanks for the info. we are going to look into it as well the way you did.
    hopefully, this will fix the problem here too.
    Eli.
    "Robert Chatfield" wrote in message
    news:3bbc45dc@hronntp01....
    > Well, Sun sent out an engineer to replace the I/O board on the box, as

    they
    > thought that this was the root of the errors, based on the Explorer

    output.
    > That was last Friday, and since then, no 84 errors have arisen, all the
    > backups have gone fine. The only problem is, the same error messages are
    > still coming up in var/adm/messages regarding SCSI! At least the backups

    are
    > working again, that's one thing. My advice to you would be to continue
    > looking at the hardware as a cause of this problem; if we had followed the
    > Veritas advice to replace every tape that threw up an 84, it could have

    got
    > quite costly!
    >
    > Regards,
    >
    > Robert
    >
    > "EliD" wrote in message news:3bbbbf19$1@hronntp01....
    > > I also noticed this error and 86 'media position' in a SAN

    configuration,
    > > using Dlt7K, 2 Crossroad routers, Brocade SW and Qlogic HBAs.. this has

    > been
    > > going for a long time and the only indication we saw less and less media
    > > errors when we eliminated most of the 'frozen' tapes and replaced with

    New
    > > ones. nevertheless, I still suspect there's more to it than Bad media..

    We
    > > tried using one router ( 4 drives group) at a time and we noticed a
    > > much-much better performance and NO Errors at all... I thought we had a

    > bad
    > > router but, when switched to 2nd group - it ran just fine as well. As i
    > > write, we are still debugging this problem and for this reason I

    searched
    > > this group for ideas to share. If you find something worth sharing I

    would
    > > like to read it.
    > > Tnx, Eli.
    > >
    > >
    > > "Robert Chatfield" wrote in message
    > > news:3bb05569@hronntp01....
    > > > I've run Sun Explorer, & I've sent the output on to my support

    contact.
    > I
    > > > guess hopefully they'll find out what the exact problem is. Thanks for

    > the
    > > > advice, it's helped close in on the cause. I'll post here when I find

    > out
    > > > more, in case anyone else is experiencing similar problems.
    > > >
    > > > Robert
    > > >
    > > > "Zorro" wrote in message

    > > news:3baf7511$1@hronntp01....
    > > > >
    > > > > "Robert Chatfield" wrote in message
    > > > > news:3baf60b9$1@hronntp01....
    > > > > > As far as I know, the tape robot/drive and the disks are the only
    > > > devices
    > > > > on
    > > > > > the SCSI bus, apart from possibly the internal cd drive on the

    box.
    > > I'm
    > > > > > going to try and find a new SCSI cable to try and solve the issue.

    > The
    > > > > only
    > > > > > thing that concerns me is if this is indicative of a dodgy disk,

    > which
    > > > > would
    > > > > > not be good.
    > > > >
    > > > > /sbus@3,0/SUNW,fas@3,8800000/
    > > > >
    > > > > unfortunately I do not have my old solaris administrator exam guide

    > > which
    > > > > has an excellent chapter explaining how to interpret this common
    > > > denominator
    > > > > but on top of my head to me it looks like st and sd devices fails on

    > the
    > > > > same SCSI adapter (maybe not a cabling issue ) ...
    > > > >
    > > > >
    > > > >
    > > >
    > > >

    > >
    > >

    >
    >




  16. Re: Keep getting "Error 84" - I got it on FC/SAN too !!!

    We got lots of these errors too on our unit at one time. It related to
    the fiber interface to one of our Quantum/ATL robots. Changed fiber to
    no avail. Changed the interface and all is well. /var/adm/messages
    only knew about the fiber and not about drives or tapes, so reported
    problems as fiber. Vertias just sees tapes so reports tape issue. BTW,
    drives kept thinking they needed cleaning too as a result of it
    detecting "soft" errors.

    When I start getting lots of tape media errors, I head right to the
    interface. Start at the robot and work the way back through fiber,
    switches, and fiber I/F in host, etc.

    Quantum wanted me to replace all 326 DLT tapes in the robot saying they
    must be contaminated. Dodged that $16,300 bullet!


    Robert Chatfield wrote:
    >
    > Well, Sun sent out an engineer to replace the I/O board on the box, as they
    > thought that this was the root of the errors, based on the Explorer output.
    > That was last Friday, and since then, no 84 errors have arisen, all the
    > backups have gone fine. The only problem is, the same error messages are
    > still coming up in var/adm/messages regarding SCSI! At least the backups are
    > working again, that's one thing. My advice to you would be to continue
    > looking at the hardware as a cause of this problem; if we had followed the
    > Veritas advice to replace every tape that threw up an 84, it could have got
    > quite costly!
    >
    > Regards,
    >
    > Robert
    >
    > "EliD" wrote in message news:3bbbbf19$1@hronntp01....
    > > I also noticed this error and 86 'media position' in a SAN configuration,
    > > using Dlt7K, 2 Crossroad routers, Brocade SW and Qlogic HBAs.. this has

    > been
    > > going for a long time and the only indication we saw less and less media
    > > errors when we eliminated most of the 'frozen' tapes and replaced with New
    > > ones. nevertheless, I still suspect there's more to it than Bad media.. We
    > > tried using one router ( 4 drives group) at a time and we noticed a
    > > much-much better performance and NO Errors at all... I thought we had a

    > bad
    > > router but, when switched to 2nd group - it ran just fine as well. As i
    > > write, we are still debugging this problem and for this reason I searched
    > > this group for ideas to share. If you find something worth sharing I would
    > > like to read it.
    > > Tnx, Eli.
    > >
    > >
    > > "Robert Chatfield" wrote in message
    > > news:3bb05569@hronntp01....
    > > > I've run Sun Explorer, & I've sent the output on to my support contact.

    > I
    > > > guess hopefully they'll find out what the exact problem is. Thanks for

    > the
    > > > advice, it's helped close in on the cause. I'll post here when I find

    > out
    > > > more, in case anyone else is experiencing similar problems.
    > > >
    > > > Robert
    > > >
    > > > "Zorro" wrote in message

    > > news:3baf7511$1@hronntp01....
    > > > >
    > > > > "Robert Chatfield" wrote in message
    > > > > news:3baf60b9$1@hronntp01....
    > > > > > As far as I know, the tape robot/drive and the disks are the only
    > > > devices
    > > > > on
    > > > > > the SCSI bus, apart from possibly the internal cd drive on the box.

    > > I'm
    > > > > > going to try and find a new SCSI cable to try and solve the issue.

    > The
    > > > > only
    > > > > > thing that concerns me is if this is indicative of a dodgy disk,

    > which
    > > > > would
    > > > > > not be good.
    > > > >
    > > > > /sbus@3,0/SUNW,fas@3,8800000/
    > > > >
    > > > > unfortunately I do not have my old solaris administrator exam guide

    > > which
    > > > > has an excellent chapter explaining how to interpret this common
    > > > denominator
    > > > > but on top of my head to me it looks like st and sd devices fails on

    > the
    > > > > same SCSI adapter (maybe not a cabling issue ) ...
    > > > >
    > > > >
    > > > >
    > > >
    > > >

    > >
    > >


    --
    _____________________
    Craig Danyi
    The Weather Channel http://www.weather.com
    Information Services
    Atlanta, GA 30339
    770-226-2502

  17. Re: Keep getting "Error 84" - I got it on FC/SAN too !!!

    We got lots of these errors too on our unit at one time. It related to
    the fiber interface to one of our Quantum/ATL robots. Changed fiber to
    no avail. Changed the interface and all is well. /var/adm/messages
    only knew about the fiber and not about drives or tapes, so reported
    problems as fiber. Vertias just sees tapes so reports tape issue. BTW,
    drives kept thinking they needed cleaning too as a result of it
    detecting "soft" errors.

    When I start getting lots of tape media errors, I head right to the
    interface. Start at the robot and work the way back through fiber,
    switches, and fiber I/F in host, etc.

    Quantum wanted me to replace all 326 DLT tapes in the robot saying they
    must be contaminated. Dodged that $16,300 bullet!


    Robert Chatfield wrote:
    >
    > Well, Sun sent out an engineer to replace the I/O board on the box, as they
    > thought that this was the root of the errors, based on the Explorer output.
    > That was last Friday, and since then, no 84 errors have arisen, all the
    > backups have gone fine. The only problem is, the same error messages are
    > still coming up in var/adm/messages regarding SCSI! At least the backups are
    > working again, that's one thing. My advice to you would be to continue
    > looking at the hardware as a cause of this problem; if we had followed the
    > Veritas advice to replace every tape that threw up an 84, it could have got
    > quite costly!
    >
    > Regards,
    >
    > Robert
    >
    > "EliD" wrote in message news:3bbbbf19$1@hronntp01....
    > > I also noticed this error and 86 'media position' in a SAN configuration,
    > > using Dlt7K, 2 Crossroad routers, Brocade SW and Qlogic HBAs.. this has

    > been
    > > going for a long time and the only indication we saw less and less media
    > > errors when we eliminated most of the 'frozen' tapes and replaced with New
    > > ones. nevertheless, I still suspect there's more to it than Bad media.. We
    > > tried using one router ( 4 drives group) at a time and we noticed a
    > > much-much better performance and NO Errors at all... I thought we had a

    > bad
    > > router but, when switched to 2nd group - it ran just fine as well. As i
    > > write, we are still debugging this problem and for this reason I searched
    > > this group for ideas to share. If you find something worth sharing I would
    > > like to read it.
    > > Tnx, Eli.
    > >
    > >
    > > "Robert Chatfield" wrote in message
    > > news:3bb05569@hronntp01....
    > > > I've run Sun Explorer, & I've sent the output on to my support contact.

    > I
    > > > guess hopefully they'll find out what the exact problem is. Thanks for

    > the
    > > > advice, it's helped close in on the cause. I'll post here when I find

    > out
    > > > more, in case anyone else is experiencing similar problems.
    > > >
    > > > Robert
    > > >
    > > > "Zorro" wrote in message

    > > news:3baf7511$1@hronntp01....
    > > > >
    > > > > "Robert Chatfield" wrote in message
    > > > > news:3baf60b9$1@hronntp01....
    > > > > > As far as I know, the tape robot/drive and the disks are the only
    > > > devices
    > > > > on
    > > > > > the SCSI bus, apart from possibly the internal cd drive on the box.

    > > I'm
    > > > > > going to try and find a new SCSI cable to try and solve the issue.

    > The
    > > > > only
    > > > > > thing that concerns me is if this is indicative of a dodgy disk,

    > which
    > > > > would
    > > > > > not be good.
    > > > >
    > > > > /sbus@3,0/SUNW,fas@3,8800000/
    > > > >
    > > > > unfortunately I do not have my old solaris administrator exam guide

    > > which
    > > > > has an excellent chapter explaining how to interpret this common
    > > > denominator
    > > > > but on top of my head to me it looks like st and sd devices fails on

    > the
    > > > > same SCSI adapter (maybe not a cabling issue ) ...
    > > > >
    > > > >
    > > > >
    > > >
    > > >

    > >
    > >


    --
    _____________________
    Craig Danyi
    The Weather Channel http://www.weather.com
    Information Services
    Atlanta, GA 30339
    770-226-2502

+ Reply to Thread