Dynix/ptx Installation Step-by-Step
shookry
asked me to run the machine (install the OS, connect to Internet, etc).
The problem is, I don't know how to start the installation. All I have
is CDs installation (DYNIX/ptx Base V4.2.4, EFS, etc) and the manual,
which I don't understand. Can anybody help me to run the machine step
by step? Thank you.
JP
news:1115103578....@l41g2000cwc.googlegroups.com...
What happens when you power the system up? Do you get a prompt? (-> or -->)
There really is a lot of information in the manuals though if you have to
load firmware it can be a little awkward to get it going.
You need to boot from CD `bh qc(0x500)` is all I can remember from memory,
let me know what prompt you get because you may need to set some other
variables in the boot menu to load the firmware from CD if it's not on the
system.
You won't be able to load EFS as that needs a license.
JP
--
There are 10 types of people in this world
Those that understand binary and those that don't
shookry
level B (-->) by boot from cd using command
->bs qc(0x500,0)ssw/fw/csm/lvlB
In which partition should I install the OS?
JP
Usually partition 0 of the first disk but you will need to make sure the
disk has a valid vtoc on it first.
Now that you have loaded the lvlb firmware you should be able to boot from
CD
something like (again from memory and I've not touched the systems for about
4 years so don't expect too much)
--> bh 2(qc0x500,0)sb8000_unix -r qd0s0 -s qd0s1
I think on 4.2.4 you will then be able to run `menu` and do a scratch
install on the disk.
There is usually step by step instructions in the manual, you want the Dynix
installation for S2000/S5000 systems section.
shookry
This I got:
# ls
# bin boot dev etc install lib lost+found mnt opt proc sbin share stand
tmp unix usr var
Yes, I'm able to run 'menu' too.
How do I want to install any additional software/file like TCP/IP,
cluster, LAN, etc. from (#) prompt?
jp
Nearly there then, I take it you've not actually done the install yet but
just booted from the install CD.
I think you just need to run menu and perform a software install.
If you get stuck, post the output from a "pr " command at the LevelB prompt
(-->)
J
shookry
5 second to boot, press any key to stop:
spinning up disks 0 1 2 3 4 5
image is not "a.out" executable
cannot boot "qd(0,2)ssw"
CSM Firmware (Level A) v1.5.0
I cannot enter the (#) prompt anymore. But I can access to the Level B
and menu by boot from the cd. What was happen? Are my installation not
complete yet?
These are the list when I "pr" command at the Level B:
Fan Monitor Task
pokeTask
power
margins=normal
testc
slic=
loop=1
date
monEntry
umon
fprog
mem
ileave=1
slic=255
errorReporti=0
deconfig
config
flags=0x0
slic=255
ctlrs
debug
scanmon
extutil
linePr
status=0xFF
lineStatus=0x0
type=0x8B
log
last=16
diary
disMem=no
disProc=no
serviceMode
pup
skipTests=no
testOnce=no
testAfterPup=yes
testAlways=no
doDump=no
enaxmem=no
noshutdownln=yes
fp1
msg
debug=0
ncr
debug=0
syncPeriod=52
remote
baud=19200
stop=1
size=8
parity=none
slow=hwflow
autoBaud=no
local
baud=9600
stop=1
size=8
parity=none
flow=xnoff
autoBaud=no
scsi
debug=0
reset
elc
zaq
zap
icu
irr=0x0
isr=0x0
imr=0x3D00
bx
flags=0x0
bh
osPath=0 qd(0,0)unix -r qd0s0 -s qd0s1
autoBoot=1
tmpPath=0 qd(0,0)unix -r qd0s0 -s qd0s1
auxPath=88 qd(0,0)stand/dump qd(0,1) 20000 /dev/rsdk/qd0s1
autoDump=1
loaderPath= qd(0,0) boot
errPath=1 qd(0,0)
skipMemClear=0
bo
VBADPath=qd(0,2)ssw/fw/ssm/lvlB
QCICPath=qd(0,2)ssw/fw/qcic/opflow
QCICFB=yes
bs
lvlBPath=qd(0,2)ssw
monAuto=1
diagAuto=0
lvlBTests=qd(0,2)ssw/fw/csm/
sysmodes
quit
opmode
customs=81
JP
> When I start my Sequent machine this morning, I got this message:
<snip>
> bh
> osPath=0 qd(0,0)unix -r qd0s0 -s qd0s1
> autoBoot=1
> tmpPath=0 qd(0,0)unix -r qd0s0 -s qd0s1
> auxPath=88 qd(0,0)stand/dump qd(0,1) 20000 /dev/rsdk/qd0s1
> autoDump=1
> loaderPath= qd(0,0) boot
> errPath=1 qd(0,0)
> skipMemClear=0
> bo
> VBADPath=qd(0,2)ssw/fw/ssm/lvlB
> QCICPath=qd(0,2)ssw/fw/qcic/opflow
> QCICFB=yes
> bs
> lvlBPath=qd(0,2)ssw
> monAuto=1
> diagAuto=0
> lvlBTests=qd(0,2)ssw/fw/csm/
> sysmodes
> quit
> opmode
> customs=81
>
OK, look at the bs settings (`pr bs`)
Your lvlBPath is not set, possibly because you have not done the install
yet.
Enter the following
-> bs lvlBPath=qc(0x500,0)ssw/fw/csm/lvlB
You may also need to change the entry below to use the CDROM
bo QCICPath=qd(0x500)ssw/fw/qcic/opflow
I think lvlBTests looks OK
Now boot from the CDROM again like you did before.
Once booted from CDROM you will need to install the operating system,
unfortunatley I can't find my old notes at the moment but will be back in
the office tomorrow and can post some more detail then if you still need it.
shookry
My current problem is:
i) I still need CD to go to the (#) prompt and menu. How I want to do
it without using CD (boot from the hard disk itself)?
ii) How I want to mount the CD at the (#) prompt? From the CD, how I
want to install it or copy the file?
Maybe I skipped my installation process or I wrongly installed in the
partition of the hard disk. Which partition in the hard disk should I
install?
jp
I'm going to have to find an old manual somewhere, the one I had in my main
office was for 4.4.2, I should be able to get my hands on 4.2.x in a couple
of days then I'll do a summary for you.
JP
shookry
JP
install by doing the following. I hope it's the same a 4.2.4!
This is likely to be a long waffling post, you will need to extract the
relevant parts yourself.
Note that I have included the default prompts, ---> = LVLB, # = shell.
Where I have just pressed enter I'll put <ENT>...
I've actually assumed that there is a vtoc on qd0 already, fortunately there
was on mine. If you do not have a vtoc you will need to create one, again
this is all in the manual. I think you will need to use CCSformat and create
the vtoc drivers before you can use mkvtoc but it's been years since I used
CCSformat. Where the installation prompts you to write a new vtoc, if you
say yes the installation will fail because the disk is in use (you're using
partition #1).
I have trimmed most of the output or this post would be even longer.
o Change the bootstrings if necessary.
---> bo QCICPath=qc(0x500,0)ssw/fw/qcic/opfw
---> bs lvlBPath=qc(0x500,0)ssw/fw/csm/lvlB
---> bh loaderPath=qc(0x500,0)stand/boot
o Start the copy utility to copy miniroot.
---> bh qc(0x500,0)stand/copy
Copy program
Input file?qc(0x500,0)stand/miniroot
Output file?qd(0,1)
Verify?y
Seek to Output block? <ENT>
Seek to Input block? <ENT>
Limit total transfer count? <ENT>
7332 blocks available (3.5 Meg)
Buffer by? <ENT>
>>> 7332 used
Count? <ENT>
>>> infinite count used
Last chance....continue? (default 'y') y
Pass 1, count "40000", checksum "8A9F", doing verify
Pass 2, count "40000", checksum "8A9F"
Done
--->
o Boot Miniroot...
---> bh 'qd(0,1)sb8000_unix -r qd0s1 -s qd0s1 -M'
INIT: Bad 'usrlimit' password, setting number of logins to 1
INIT: SINGLE USER MODE
su: WARNING: can't open /usr/adm/sulog
: No such file or directory
-sh: mail: not found
o Load the Operating system
# /loadcd 2>&1 | tee log
Do you want / or /usr filesystems to be an EFS filesystem ? [n/y]n
Remember, root partition and miniroot partition must be on the same disk
Enter root disk partition (e.g., qd0s0), use <cr> to abort installation:
qd0s0
You selected disk partition qd0s0 on disk type hpc2490 for the root
partition
Should a VTOC be written on the root disk qd0? [n/y]: n
Should the root filesystem support ACLs? [n/y]: n
Enter usr disk partition (e.g., qd0s2), use <cr> to abort installation:
qd0s2
You selected disk partition qd0s2 on disk type hpc2490 for the usr
partition
Should the usr filesystem support ACLs? [n/y]: n
root on qd0s0 disktype=hpc2490 VTOC=no ACL=no
usr on qd0s2 disktype=hpc2490 VTOC=NA ACL=no
About to overwrite information on disk(s), proceed? [n/y]: y
Building CD-ROM VTOC device /dev/rSA/rcdrom0
Mounting CD-ROM partition /dev/rSA/cdrom0
mount: warning: <> mounted as </cdmnt>
---------------------------------------------------------------
The installation will take about 30-40 minutes.
---------------------------------------------------------------
<rest of output trimmed>
o Now that the operating system is installed, boot single user...
---> bh '2qd(0,0)unix -r qd0s0 -s qd0s0'
o You will need to make sure that the lvlB firmware is installed from CD,
use the menu system to do this.
Once the firmware is installed you will need to change the bs, bo and bh
settings to point to your local disk.
o To get the system networked you will need to install the TCPIP software.
This is also done via the menu under System Administration / Software
Mamagement. Im not sure if the CDROM has to be mounted first, if it does,
try doing the following;
# dumpconf | grep cd
# cd devices 1 found 2 configured
cd 1 on qcic_scsi 0 unit 5 # located on qcic_scsi 0 unit 5
#
# devbuild vtoc /dev/rdsk/cd1
mount -r /dev/dsk/cd1s0 <mount-point>
HTH
shookry
tape to do the installation. I think I manage to install the OS and
right now I'm trying to change the bs, bo and bh settings to point to
local disk.
My problem is, how I want to know where the files located in my local
disk? Where the bootstrings (bo QCICPath, bs lvlBPath, bh loaderPath)
locate?
JP
From tape??! Bet that was slow!
If the files have been installed you should be able to see them in the
directory tree;
eg/
If I had lvlBPath=qd(0,2)ssw/fw/csm/lvlB
I would expect to find the lvlB file in /usr/ssw/fw/csm/
FYI, qd(0,2) is qd0s2 or usually the /usr partition, references to this in
boot strings are relative to the partition, if you did not have a separate
/usr partition on your system the paths would probably be something like
lvlBPath=qd(0,0)usr/ssw/fw/csm/lvlB.
If the files do not exist the boot will fail as it won't be able to find the
files. You must have installed them from the release media
shookry
to do it and where should I copy it?
shookry
boot from the hard disk. So, what should I do? When I 'pr':
bh
osPath=0 qd(0,0)unix -r qd0s0 -s qd0s1
autoBoot=1
tmpPath=0 qd(0,0)unix -r qd0s0 -s qd0s1
auxPath=88 qd(0,0)stand/dump qd(0,1)20000 /dev/rdsk/qd0s1
loaderPath=qd(0,0)stand/boot
errPath=1 qd(0,10)
skipMemClear=0
bo
VBADPath=qd(0,2)ssw/fw/lvlB
QCICPath=qd(0,2)ssw/fw/qcic/opfw
QCICFB=yes
bs
lvlBPath=qd(0,2)ssw
monAuto=1
diagPath=qd(0,2)ssw/diag/csm/exec
diagAuto=0
lvlBTests=qd(0,2)ssw/fw/csm/
Which command I should configure to boot from hard disk?
shookry
jp
>I installed the OS again using cd (Dynix/ptx 4.1.3) but still cannot
> boot from the hard disk. So, what should I do? When I 'pr':
>
> bh
> osPath=0 qd(0,0)unix -r qd0s0 -s qd0s1
> bo
> VBADPath=qd(0,2)ssw/fw/lvlB
> QCICPath=qd(0,2)ssw/fw/qcic/opfw
> bs
> lvlBPath=qd(0,2)ssw
> diagPath=qd(0,2)ssw/diag/csm/exec
> lvlBTests=qd(0,2)ssw/fw/csm/
> Which command I should configure to boot from hard disk?
Have you actually installed the OS or just loaded miniroot?
The 4.1.3 install should be the same as 4.2.3 what is written on the CD in
the CDROM drive?
LoaderPath looks wrong for 4.1.x, I thought that the boot loader for 4.1 was
off root, loaderPath=qd(0,0)boot, unfortunately I can't remember and I'm not
near a system this week to be able to check, it may even be in
qd(0,2)ssw/boot ??!
VBADPath doesn't look right but I don't think S5000 systems used a VBAD so
it shouldn't matter
lvlBPath is not complete, use the setting I used in a previous posting or
use the lvlB firmware from the CDROM.
Can you post the output for the `co` command in lvlB I have a funny feeling
that your QCIC firmware is likely to be out of date.
I suggest you email me off list ft00mch a t h o t m a i l d o t c o m,
access to the news feeds where I am is flaky at the moment, I'm caving to
connect to my home PC and use my normal account to do this and it's a bit of
a pain... I'll see if we can get this going...somehow...
JP
Doug Monroe
find the object.
VBADPath is only used if you have a VME bus adapter (stripped down
SSM2), so it doesn't matter.
If shookry did get miniroot loaded and did run "loadtape" or "loadcd",
the paths need to stay pointed to the cdrom or tape until the system is
booted from the hard drive with "bh 'qd(0,0)unix -r qd0s0 -s qd0s1'",
and the CSM and QCIC software is installed. After that, the paths can
be pointed to the hard drive.
Doug