It's going to take much more than a broken drive to get into this problem.
You can boot a system with a tape drive configured but not attached a the
ldev will still be associated with the drive.  The  problem here may be
deeper, as Jeff indicates.  Something removed it from the configuration
table at start up time, and that takes a bad configuration from sysgen or a
broken adapter or some such.

After you do the things Jeff suggested, you should go into sysgen and check
the configuration for that ldev.  Then you will need to reboot and on the
way up, you should check the hardware status with mapper(2).

Denys

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Jeff Kell
Sent: Tuesday, October 18, 2011 3:26 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Ldev 7 should be Tape but is assigned to network
session

On 10/18/2011 4:06 PM, Cornelia Sellitto wrote:
> Hello List,
> CFA's HP3000/A400 running 7.5 pp2, having problems with tape backup.
> Looks like the LDEV 7 which is defined as tape, has somehow been
> assigned to a session. They are reporting problems with losing the
> network connection, had to reset the NSCONTROL a few times. Any ideas?

The only time I've seen this happen is when there are boot-up errors with
the tape drive, and the device/path is unrecognized.  The ldev[s] associated
with the path are then removed from the startup configuration and become
available for the "non-nailed device pool" that is used by VTserver and
Telnet.

If you "showdev tape" does it list ldev 7?  (When the above condition
occurs, it won't show up in the expected classes either)

Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *