T.R | Title | User | Personal Name | Date | Lines |
---|
646.1 | Feedback from VMS | MAY30::CUMMINS | | Tue Jun 03 1997 17:03 | 21 |
| From: STAR::KFOLLIEN "Ken Follien 381-2632 OpenVMS Systems Group" 3-JUN-1997 15:34:48.89
To: MAY30::CUMMINS
CC: JHUBER,KFOLLIEN
Subj: RE: Any ideas on this one?
Reference- 'startup_p1' set to 'min'
-----------------------------------
From the SYSGEN Help file :
STARTUP_P1 specifies the type of system boot the system-
independent startup procedure is to perform. If STARTUP_P1 is
blank, "FULL" is used as parameter 1; "MIN" indicates a minimum
boot that starts only what is absolutely necessary for the
operating system to run.
Bill, in this case all you would see is the booted system disk and OPA0
If you are going to do an upgrade, boot the cdrom... This is all in the
VMS Doc Set... Ken
|
646.2 | Seems odd. | USPS::FPRUSS | Frank Pruss, 202-232-7347 | Tue Jun 03 1997 19:51 | 6 |
| SYSMAN> IO AUTOCONFIGURE
should have found the CD after a minimum boot. This should be
investigated.
But .1 is right, to do an upgrade, boot off the CD.
|
646.3 | Use /LOG/FULL | STAR::jacobi.zko.dec.com::jacobi | Paul A. Jacobi - OpenVMS Systems Group | Wed Jun 04 1997 14:10 | 8 |
| I suggest you post the output of the following SYSMAN command which
generates additional informational messages:
SYSMAN>IO AUTOCONFIGURE/FULL/LOG
-Paul
|
646.4 | Update: Found workaround by booting of cdrom | TROOA::HANDY | L. Handy, MCSE DTN 626-3210 | Wed Jun 04 1997 14:41 | 14 |
| Thanks for the feedback. Yes, I did execute sysman IO autoconfigure
with no change. I understand the implications of 'startup_p1 = "min"',
but the io autoconfigure was my problem.
My workaround was to boot directly from the OpenVMS 7.1 cdrom, then
select 'preserve' then 'upgrade' in order to upgrade my system disk. I
believe that this is a great feature built into VMS. When I used this
method, all devices were then recognized on the system from this point
on.
(Never did get a chance to perform io autoconfigure/full/log- sorry.
Lyndon
|