> 
> Hello Group,
> 
> I just recently 'edlabeled' and 'copied' miniroot V1.1 to my VaxServer 3500
> When I booted I got a message that said it found my RF71 at UDA0.  Then it
> goes on to try to probe UDA1. This yields 'Controller hung'.  I think I have
> the partial answer.  When I do a 'show UQSSP' at the monitor prompt it
> also reports RF71 at target 0, but then it goes on to targets 1,2,3,4 and 5
> each one with a time-out of about a minute.  Without knowing the inner
> workings, it seems like BSD is smarter in knowing when to quit.  
> 
The meaning of 'Controller hung' is that the controller fails to jump
into the init state, and just hangs. This may happen if there are 
no disks on a controller.

> Later in the boot sequence after 4 iterations of 'Controller Hung ...
> then finally 'Changing root device to ra0a' I get a message
> 'UDA1: Init step 3 failed...'  This device does not exist!  Is there some
> jumper fiddling that I need to do or what?
> 
This sounds like a disease that (I hope) is gone in post-1.2; i.e.
with the new MSCP code. Try a new version of the miniroot.

-- Ragge