Wow! This seemed to do the trick. I wonder if that'll make the drives on my
VS4000/60 work too, with the controller support added recently. I was getting
the exact same condition. I'll have to give that a try.

Thanks, Chuck, you're a lifesaver!

 -J. Buck Caldwell

Chuck McManis wrote:

> Interestingly, I had this exact same symptom and the "fix" was to specify
> 4.2BSD when I used disklabel -i. This didn't seem to be a requirement,
> however when I did that, suddenly the disks were found and all was cool.
> I'm guessing that newfs has been changed to look at the disklabel to find
> the "default" FS type but I've not tracked it down. I'm in the process of
> getting a second "test" M76 up and running and that will be able to verify
> there.
>
> --Chuck
>
> At 06:56 PM 3/21/00 -0600, J. Buck Caldwell wrote:
> >So I've got these VS3100/m38s, and I experienced the notorious RZ23
> >problem. I managed to disklabel it, but newfs responds with Device Not
> >Configured. I did manage to newfs the RZ25 in the same machine, on the
> >same channel. So I moved on to my next VS3100, which has a RZ24 in it. I
> >figured out a disklabel, wrote it, and tried to newfs - and I get Device
> >Not Configured. I can reboot the machines, and read the disklabel that I
> >wrote, so it is actually writing it (plus, I use the -r liberally), but
> >newfs just don't cut it. Disklabel -B also works (well, apears to).
> >
> >At this point, I don't even know where to begin looking. Any help would
> >be appreciated.
> >
> >--
> > -Buckaroo
> >
> >

--
 -Buckaroo