From: Andrew Raine (Andrew.Raine@mrc-dunn.cam.ac.uk)
Date: Wed Oct 16 2002 - 11:29:33 EDT
Dear Managers,
I had useful advice on hwmgr from Terry Horsnell (in the next building
from me!) and Pat O'Brian. However, I solved the NEO Overland changer
problem by closing one of the cartridge doors (!) The system sensibly
won't do anything else until it can re-run its internal inventory after
any event that might change what is in its cartridges.....
I managed to get time to do a reboot today, and that has apparently
cured the DLT problem as well. While I'm happy to have a functioning
driva again, I'm still uneasy that I don't know what went wrong.
Still, since I got my other changer working as well, I do have
backup-backup again...
My original question:
> Dear Managers,
>
> Having understood my vdump problems (see my earlier message today) I
> now find that I have problems with my DLT/SDLT drives and
> changers!
>
> In my TL891 changer, the changer itself seems fine:
>
> beta # robot show robot /dev/changer/mc0
>
> Robot Name: /dev/changer/mc0 Type: SCSI
>
> Media Robot Identifier: DEC TL800 (C) DEC0519
>
> Slots: 10
> Drives: 2
> Inports: 0
> Outports: 0
> Transports: 1
>
> but I can no-longer get the first DLT drive to
> respond:
>
> beta # mt -f /dev/ntape/tape0 status
> /dev/ntape/tape0: No such device or address
>
> The second DLT drive seems fine though:
>
> beta # mt -f /dev/ntape/tape1 status
>
> DEVIOGET ELEMENT CONTENTS
> ---------------- --------
> category DEV_TAPE
> bus DEV_SCSI
> interface SCSI
> device DLT8000
> <etc........>
>
> Conversely, in my NEO Overland changer, the SDLT Drive is fine:
>
> beta # mt -f /dev/ntape/tape3 status
>
> DEVIOGET ELEMENT CONTENTS
> ---------------- --------
> category DEV_TAPE
> bus DEV_SCSI
> interface SCSI
> device SuperDLT
> <etc......>
>
> but the changer itself doesn't respond:
>
> beta # robot show robot /dev/changer/mc2
> <just hangs>
>
> "scu show edt" shows all these devices present:
>
> beta # scu show edt
>
> CAM Equipment Device Table (EDT) Information:
>
> Bus/Target/Lun Device Type ANSI Vendor ID Product ID Revision N/W
> -------------- ----------- ------ --------- ---------------- -------- ---
> 2 0 0 Changer SCSI-2 DEC TL800 (C) DEC 0519 W
> 2 1 0 Sequential SCSI-2 QUANTUM SuperDLT1 2A2A W
> 2 4 0 Sequential SCSI-2 COMPAQ DLT8000 022B W
> 2 5 0 Sequential SCSI-2 COMPAQ DLT8000 022B W
> 2 6 0 Changer SCSI-2 OVERLAND NEO Series 0320 W
>
> and a "scu scan edt" makes no difference.
>
> As all these devices are on the same bus, might the problems be
> related? Can anyone suggest any further diagnosis that I might do to
> establish what is going wrong?
>
> Its a production system, but I think I'll have to close it down and
> reboot to see if that makes any difference.....
>
> The system is a 4-proc ES40, 5.1, pk3 as part of a 2-node cluster.
>
> Many thanks,
Andrew
-- Dr. Andrew Raine, Head of IT, MRC Dunn Human Nutrition Unit, Wellcome Trust/MRC Building, Hills Road, Cambridge, CB2 2XY, UK phone: +44 (0)1223 252830 fax: +44 (0)1223 252835 web: www.mrc-dunn.cam.ac.uk email: Andrew.Raine@mrc-dunn.cam.ac.uk
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:56 EDT