[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

549.0. "1000A, V6.2-1H3, can't see disks or network" by EPS::LOVELUCK () Tue Apr 29 1997 19:09

    also posted in wrksys::mikasa
    
    AlphaServer 1000a 5/400
    VMS V6.2-1H3
    SRM  v4.8-74
    ARC  v5.28
    vms pall code v5.28
    memory 512Mb
    bus_probe_algorith "new"
    5 disks (rz28s and rz26s) in a BA350 conected to the scsi connector pka0
    
    We have two of these  (straight from manufacturing) that
    exhibit the same problem. (different VMS systems, same version)
    
    From the console prompt, I can see all my disks and the ethernet card,
    and the TLZ, but when I boot VMS, it can not see anything other than 
    the system disk.  Show device shows dka0 (my system disk), pka0 and 
    opa0 only.
    
    Apart from not being able to start the network, or access any disks,
    VMS seems quite happy. I do get subsequent BUGCHECKS when I start
    LATACP, or a UCX feature whose name escapes me. I assume that those
    problems are just symptoms, but I checked my LATACP dump with CANASTA 
    anyway and did not get a match.
    
    I have tried sysman io auto, I have rerun the ecu, with no luck.
    
    NET$CONFIGURE and UCX$CONFIG agree that there is no ethernet adapter on
    the system.
    
    If I move my disks around and boot from dka100, VMS sees DKA100, but
    nothing else.
    
    The system configuration works fine on an alphaserver 2100 if I just
    move the SCSI cable. 
    
    Does anyone have any ideas?
    
    Dave

T.R	Title	User	Personal Name	Date	Lines
549.1		EVMS::MORONEY	vi vi vi - Editor of the Beast	`Tue Apr 29 1997 19:24`	4
	What happens when you execute SYSMAN> IO AUTOCONFIGURE/LOG ? You may just have the sysgen parameter that controls autoconfiguration upon boot (forget its name) set wrong.
549.2		AUSS::GARSON	DECcharity Program Office	`Wed Apr 30 1997 00:05`	12
	re .1 Param is NOAUTOCONFIG. It's "special" so shouldn't have been set to 1 but who knows... re .0 Also check whether SYS$MANAGER:SYCONFIG.COM executes the line $ STARTUP$AUTOCONFIGURE_ALL == 0 Normally this line is present but commented out.
549.3	AUTOGEN might do the trick...	BACHUS::VERCAMMEN	You never walk alone...	`Wed Apr 30 1997 08:08`	6
	Execute AUTOGEN. This should do the trick. Regards, \Jan
549.4	Things To Try, Then Call For HW Service...	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Wed Apr 30 1997 10:09`	9
	Do any errors show up on system bootstrap? Do the self-tests error? Check SCSI_POLL variable, and PK*_DISCONNECT. (I don't think these would cause the Ethernet adapter to "go missing".) The full AUTOGEN pass (recommended earlier) will update VMSIMAGES.DAT, which should bring any missing ICBM modules online, and allow various supported devices to be configured.
549.5	AUTOGEN FIXED IT - THANKS	EPS::LOVELUCK		`Wed Apr 30 1997 11:33`	1