Re: 3rd party disk in VS4000-90

• Previous message: John Laird: "Re: 3rd party disk in VS4000-90"
• In reply to: John Laird: "Re: 3rd party disk in VS4000-90"
• Next in thread: John Laird: "Re: 3rd party disk in VS4000-90"
• Reply: John Laird: "Re: 3rd party disk in VS4000-90"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Date: Thu, 29 May 2003 16:41:27 GMT

Thanks for answering ..

In message <vbccdv4ifffcd0kl8srqaj512jfa3ih6mf@4ax.com>
          John Laird <john@laird-towers.org.uk> wrote:

> On Thu, 29 May 2003 15:50:51 GMT, Michael Grunditz <migu@telia.com> wrote:
>
> >I have tried several scsi discs in my vaxstation but none of them shows up
> >with "sh dev".
> >
> >Is there some special magic needed ?
>
> "sh dev" at the console prompt (>>>) or at the DCL prompt ($) ?

At the console prompt.

>
> Disks don't usually need to spin-up for the electronics to respond to any
> SCSI queries (>>>sh dev), but it might be useful to know if they are indeed
> at that point "alive" ! You have set unique scsi ids on each disk
> presumably, none of which conflict with the host controller (usually 6,
> sometimes 7) ? It is rare to find any termination jumpers installed inside
> a processor box, but it might be worth checking all the drives (sometimes
> cdroms are delivered with termination present). You could try disconnecting
> all other devices to see if the console can then find your new disks, too.
>
> Once you have them at least visible to the console ROM, there is no
> guarantee that VMS will support them, but it is a start.
>
> What make and model of disks, out of interest ?

Its a IBM FRU PN 45G9467

/Michael

• Previous message: John Laird: "Re: 3rd party disk in VS4000-90"
• In reply to: John Laird: "Re: 3rd party disk in VS4000-90"
• Next in thread: John Laird: "Re: 3rd party disk in VS4000-90"
• Reply: John Laird: "Re: 3rd party disk in VS4000-90"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]