Subject: Re: VS2k install woes: disk problems!
To: Chuck McManis <cmcmanis@mcmanis.com>
From: Brian D Chase <bdc@world.std.com>
List: port-vax
Date: 04/09/1999 14:53:27
Are MSCP drives supported currently on the VAXstation 2000?  I know
support for them left for a period of time, I wasn't aware of it having
been brought back into the fold.  Ragge?

As for the SCSI support, you won't be able to boot directly from the SCSI
disk as the VS2000 doesn't directly support SCSI devices as boot devices.
It should be feasible to boot into the NetBSD/vax kernel from either the
RD32, a floppy drive (RX33), or tape drive and then still use the SCSI
drive as your system disk.  I've not tried this yet, but it is on my list
of things to eventually attempt to do.

-brian.

On Fri, 9 Apr 1999, Chuck McManis wrote:

> A bit more information is needed. When the system is booting it probes for
> devices, can you tell us what it found? Some devices are not as they
> appear, for example I have a Viking QTO scsi tape controller in my UVax but
> it reports itself as an MSCP TK50. Similarly with my RQD11 ESDI controller
> which claims it is like a UDA50 MSCP disk controller.
> 
> As for recognizing the disk, it won't see it until you label it. So if saw
> the disk in the probe sequence you can use disklabel to write a label to
> it, then the device will configure the next time you boot.
> 
> --Chuck
> 
> At 04:30 PM 4/9/99 -0400, jsturges@gmri.com wrote:
> >Hi,
> >I've successfully netbooted my VS2k into 'sysinst' from the 12/98 snapshot.
> >However, I'm having major disk problems.
> >
> >The machine has an internal RD32, as well as an external SCSI disk.  The 
> >SCSI is
> >an IBM WDS-3160, which is a 3.5" 160Mb. SCSI-2 drive.  It does *not* do Fast
> >SCSI-2, however, and is limited to 5MB/sec.
> >
> >When the kernel/sysinst initializes, it does not even see the RD32.  However,
> >the RD32 spins up, and can be formatted successfully by the ROM formatter.
> >Aren't the VS2k internal disks supported??  Or is mine broken?
> >
> >Secondly, the SCSI disk *is* recognized at boot time but cannot be accessed.
> >Any attempt to write the disklabel or anything results in the drive resetting
> >itself (so my ears tell me) and the operation fails with an error.
> >
> >Can someone provide guidance on this?  I'd really like to get the OS installed
> >locally, as opposed to running it diskless/dataless.
> >
> >TIA,
> >Jonathan
> >
> >
> 

---
Brian "JARAI" Chase | http://world.std.com/~bdc/ | VAXZilla LIVES!!!