Ted

I don't think your problems are with the OS, so fake Wintel devices
won't do it for you. jbconfig is interrogating your Dell directly.

Here are your options as I see them (and I assume thee are reasons why
the first two aren't immediately possible) :

* Replace the faulty drives asap
* Pull the faulty drives out and replace them with the blanking sleds
that I expect came with your Dell136T, or otherwise complete the SCSI
chain termination
* Pull the faulty drives and reorder your drives so that the two good
ones come up as elements 254 & 255, and the faulty ones as 256 & 257.
This lets jbconfig include the faulty units but you can then disable
them in Networker and carry on. I ran an IBM3583 with a couple of dead
drives OK like this for its last six months, saved repairing an
end-of-life unit in these cash-strapped times ...

Regards

Jock Howie

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Reed, Ted G [IT]
Sent: Saturday, 12 December 2009 10:46 a.m.
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Creating fake \\.\TapeX devices in Wintel

I have a Windows 2000 server instance providing Networker 7.2.1 master
service, attached to a Dell136T with LTO1 drives.  However, the last
powercycle of the Dell came up with only 2 of the 4 drives online.  The
other 2 report hard errors on the library console/LCD.  Thing is, I can
survive just fine on two drives....the environment has been shrinking.
But the Wintel + Dell reboot also re-ordered the drives, so I can't
simply down the 2 broken and leave the other 2 online...I have to
rebuild the jukebox.

This is where my problem comes in.  JBCONFIG of autodetected SCSI of the
136T tries to force me to enter values for elements 254, 255, 256, and
257.  And only 256/257 are working devices.  No matter what I try,
jbconfig will only accept \\.\Tape0 and \\.\Tape1 (discovered)...and I
can't repeat them then disable either.  But what about the other 2
elements?  Can I create a spoof or fake \\.\Tape2 and \\.\Tape3 so that
I can put the broken drive elements as the spoofed values, and the
working drive elements with their proper discovered device path?

Any other ideas are welcome....I had not anticipated being forced to
enter 4 different \\.\TapeX values when I only have 2 recognized by the
OS.  Thanks.
--Ted


This e-mail may contain Sprint Nextel Company proprietary information
intended for the sole use of the recipient(s). Any use by others is
prohibited. If you are not the intended recipient, please contact the
sender and delete all copies of the message.

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER 
This email with any attachments is confidential and may be subject to legal 
privilege.  
If it is not intended for you please reply immediately, destroy it and do not 
copy, disclose or use it in any way. 

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER