bala@synopsys.synopsys.com (Bala Vasireddi) (05/31/90)
We have a DN4500 with 2 disks attached to it. The 1st disk was running
Sr10.2 without any problems. Couple of days back we added a 2nd disk
so that we can put Sr10.1 on that disk. Our intention was to be able to
boot off either disk in Sr10.1 or Sr10.2 mode.
The SR10.1 installtion on the 2nd disk went fine and the System does boot up
in Sr10.1 mode but gives the following message during bootup:
"Boot device has no OS paging file.
See Installation procedures cxhapter in Release Documentation for more
information.
For now, the OS will not page, which may cause some performance
degradation"
So I checked the SR10.1 Release notes, but couldn't find anything related to
the above message.
I copied the 'sysboot' file from the 1st disk (SR10.2) onto the 2nd disk
using 'cpboot'. Still the problem persists.
After the System comes up whenever I try to access a file on another
Apollo ("kings") or cd to //kings this system suddenly freezes up for a
couple of minutes. During this time nothing else can be done, even locally.
Is this a direct result of the problem above?
Can anybody shed some light on this? Your help is much appreciated.
Thanks.
----
Bala Vasireddi, Phone: (415)962-5036
Synopsys, Inc. FAX: (415)965-8637
1098 Alta Ave DDN: bala@synopsys.com
Mountain View, CA 94043 UUCP: ..!fernwood.mpk.ca.us!synopsys!balakrowitz%richter@UMIX.CC.UMICH.EDU (David Krowitz) (05/31/90)
The OS paging file is created when you initialize the disk using INVOL. Since this is your second disk drive, you can run /com/invol rather than shutting down the node and using "ex invol". First, you must dismount the second disk (use /com/dmtvol), then use option 8 of invol to create the OS paging file. -- David Krowitz krowitz@richter.mit.edu (18.83.0.109) krowitz%richter.mit.edu@eddie.mit.edu krowitz%richter.mit.edu@mitvma.bitnet (in order of decreasing preference)