Thank You for the fast responses and many helpful suggestions.
I received step-by-step directions on booting the system and
cleaning up the file space.
also information on mailing lists and documentation. I've forwarded
this information to my friend.
Thanks to:
Leonid Kolytchev <LKolytch_at_cuedatawest.com>
Bob Grandle <GRANDLE_at_acodbob.larc.nasa.gov>
"Thomas P. Blinn" <tpb_at_doctor.zk3.dec.com>
Joe Fletcher <joe_at_meng.ucl.ac.uk>
Alex Gorbachev <alex_at_iss-integration.com>
Chuck Taylor <Chuck.Taylor_at_Vishay.com>
Below are the instructions and suggestions i received.
Thanks again
Valerie Gray
########
GRANDLE_at_acodbob.larc.nasa.gov on 02/15/2000 03:30:04 PM
Please respond to r.e.grandle_at_larc.nasa.gov
Valerie:
If you have not halted the machine do so.
1. at boot prompt type b/1
machine will come up to a sysboot> prompt
type set startup_p1 "min"
then type continue
The machine should then come all the way up in
a minimum configuration. You must be at the
console to do this. You can log in from the
console as system. I would then do the following command
:
purge [*...]*.*/keep=2
This will purge all files
version on the machine, except the two highest
ones. This normally frees up enough disk space
to allow the machine to boot in normal mode.
You can add a /log if you want to see what it is
purging. After the purge is done, do
show /dev d
to see if enough space has be freed. If not you
will have to selectively delete files until you have
enough space. Typically the machine only needs about
a 1000 block free to come up in normal mode.
Then type mcr sysgen
you will get a sysgen> prompt
type
set startup_p1 " "
write current
write active
exit
This will reset the startup_p1 parameter to allow normal
booting.
Then
_at_sys$system:shutdown
and answer the prompts correctly( ie. you can tell it
to reboot here) or halt and reboot the machine in the
normal manner.
Bob Grandle
NASA Langley Research Center
################
Chuck Taylor <Chuck.Taylor_at_Vishay.com>
Your friend will have to boot the VMS system in minimum mode to get to the
disk so that it can be cleaned up.
I believe that you would do the following at the >>> prompt:
>>> BOOT -FLAG 0,1
That should take you to a new prompt level (SYSGEN>)
There you should enter these commands
SYSGEN> SET STARTUP_P1 "MIN"
SYSGEN> CONTINUE
The system will then boot up without starting anything - much like a single
user session on Tru64. Only the system disk will be mounted. Then you
should be able to use the normal methods available under VMS to clean up the
disk.
Then before the system is rebooted you must set STARTUP_P1 back to blank.
at the system prompt (usually $)
$ MC SYSGEN
SYSGEN> USE CURRENT
SYSGEN> SET STARTUP_P1 ""
SYSGEN> WRITE CURRENT
SYSGEN> EXIT
Then reboot and the system should come back up normally. This is pretty
standard stuff for a VMS Sys Admin. If you have more problems give me a
call.
Good Luck,
Chuck Taylor
Senior Infrastructure Developer
Vishay - Siliconix
2201 Laurelwood Road
Santa Clara, CA 95054-1595
(408) 970-5381 Phone
(408) 567-8967 Fax
chuck.taylor_at_vishay.com
#################
From: Leonid Kolytchev <LKolytch_at_cuedatawest.com>
Hi Valerie,
I would check SYS$MANAGER directory for new LOG files as a first step.
$ DIR SYS$MANAGER:*.LOG /DATE/SIZE
more likely they have a number of OPERATOR.LOG;* files there and other log
files. All of them text format files and they may check them before to
remove or move somewhere else.
Second step, each time VMS system boots it creates STARTUP.LOG file in
SYS$SYSTEM. They may check those.
$ DIR SYS$SYSTEM:*.LOG /DATE/SIZE
Actually, they may check whole SYS$SYSDEVICE for new files to see what was
created recently.
$DIR SYS$SYSDEVICE:[000000...]*.* /DATE/SIZE/SINCE=12-FEB-2000
I would move off SYS$SYSDEVICE PAGEFILE.SYS, SWAPFILE.SYS and SYSUAF.DAT
files, but it is different topic.
If they have UCX running on the node, they may be interesting to check UCX
LOG and SPOOL directories.
Hopefully this help.
Do they really have Open VMS v.1.4 or 1.5 ? :^)
Regards,
Leonid
#######
"Thomas P. Blinn" <tpb_at_doctor.zk3.dec.com> on 02/15/2000 02:04:00 PM
http://www.ornl.gov/cts/archives/mailing-lists/
A European web archive is also available:
http://www.xray.mpe.mpg.de/mailing-lists/tru64-unix-managers/ |
15. Similar lists for non-Tru64 UNIX platforms are:
Vendor List Name How to Subscribe
====== ========= ================
Cray unicos-l ask unicos-l-request_at_cug.org
(CUG members only)
DEC AlphaNT send "subscribe" to
AlphaNT-request_at_listserv.mfg.mke.ab.com
DEC decstation-managers send "subscribe decstation-managers"
to majordomo_at_ornl.gov
HP hpux-admin send "subscribe hpux-admin" to
majordomo_at_dutchworks.nl
IBM AIX-L send "subscribe aix-l your name" to
listserv_at_pucc.princeton.edu
RedHat axp-list send "subscribe" to
axp-list-request_at_redhat.com
SGI info-iris ask info-iris-request_at_arl.mil
(high volume: duplicates
comp.sys.sgi.* newsgroups)
Sun sun-managers send "subscribe sun-managers" to
majordomo_at_sunmanagers.ececs.uc.edu
16. Other forums that relate to DEC Alpha systems:
Newsgroups:
comp.sys.dec includes all DEC hardware and software
comp.unix.osf.osf1 OSF/1 on Alpha and other platforms
comp.os.vms VMS issues for VAX and Alpha platforms
vmsnet.alpha VMS on Alpha platforms
From: Joe Fletcher <joe_at_meng.ucl.ac.uk>
Hi Valerie,
They will need to do a conversational bootstrap to get the system up in
a sort of single user mode. On a DEC3000 the command from the console is
boot -fl 1
if I recall correctly (it's been a while).
This should enable them to clear out whatever needs deleting.
Cheers
Joe
########
From: Alex Gorbachev <alex_at_iss-integration.com>
Your friend needs to boot from a CD, mount the root FS and clean it
up. Some docs that may help with that task are in:
http://www.unix.digital.com/faqs/publications/pub_page/doc_list.html
HTH,
Alex Gorbachev
Intelligent Systems Services Inc.
www.iss-integration.com
#######
Original Request:
>I have a friend who's group is using
>a Dec 3000 running Open VMS version 1.4 or 1.5.
>they have very little in the way of documentation.
>
>here's the problem, the boot disk has run out of
>space and they are unable to start up a terminal
>session so they can clean up the drive.
>
>Can anyone give me detailed instructions on the
>best way to resolve this problem. I'm a Solaris
>Administrator, and not familiar with the Dec 3000.
>
>I not a regular subscriber to your list, please reply to
>
>vgray2_at_telcordia.com
>
>Thank You
>
>Valerie Gray
Received on Tue Feb 15 2000 - 22:34:13 NZDT