Thank you OSF managers. My question was answered very quickly by 5
out of 8 respondents. The information does appear to be in the release
notes, I had a copy for a day from another unit on campus (we only get
one copy to share for the campus) I had perused the notes quickly and
though I saw references to another section with a listing of "advanced"
ENVARS, I never did find it. Seeing that the information was there
all the time, my supervisor and I have decided to spend the additional
bucks for our own copies of TFM and media.
The correct answers follow, the question is at the end.
----------------------------------------------------------------------
From: REPOND_at_elsic.epfl.ch (Nicolas Repond)
Your problem is described on the Release Notes of the Loadable Firmware Update
Utility and User Guide and Release Notes for the AlphaServer 2100 Model 4/200.
Here is:
1.2.3 OSF/1 Specific Anomalies
The following is a list of known anomalies and workarounds
specific to the OSF/1 operating system:
o The environment variable, bus_probe_algorithm, has been
included in this release for use with OSF/1 version
V3.0B or later. This environment variable must be set
to new and the system must be power cycled, reset or
initialized.
P00>>>set bus_probe_algorithm new
reset the system
After that, you have to change your BOOTDEF_DEV variable to the correct device
that you can see whith the command "show dev".
----------------------------------------------------------------------
From: aman_at_jerry.alf.dec.com (Janet)
Try these steps -
>>> set bus_probe_algorithm new
>>> init
>>> sh bootdef_dev
(make sure it jives with what 'sh dev' says. should be something like
dra0.0.0.1007.0)
>>> boot
----------------------------------------------------------------------
From: Leonard Vaughn <vaughn_at_rust.zso.dec.com>
1) Are you running firmware 3.8 or later? (Seems like 3.9 is on that CD.)
check at console,
>>>show version
2) Did you set the bus_probe_algorithm console variable to "new"?
>>> set bus_probe_algorithm "new"
This should be noted somewhere in the release notes and/or the Firmware
installation notes. From your note, I suspect this.
----------------------------------------------------------------------
From: Aidan Williams <aidan_at_huon.cse.unsw.EDU.AU>
>>> set bus_probe_algorithm new
In the ``Release Notes and Installation Instructions for Version 3.0B''
you can find this in section 5.1.6.4. I would hope that such
----------------------------------------------------------------------
From: Dave Cherkus <cherkus_at_UniMaster.COM>
Did you read the 3.2 release notes?
There are some console firmware issues. You need the
proper firmware load, and you need to set a certain
console variable. I think the answer is to set
bus_probe_algorithm to new, but this is a guess.
Please look at the release notes.
PS: I'm not *positive* that the raid controller is
supported for boot media. Check the release notes.
I'd consider putting the boot device on the internal
controller anyway...
----------------------------------------------------------------------
Also thanks to these folks who offered some good suggestions:
Simon <censjg_at_caledonia.hw.ac.uk>
Hellebo Knut <bgk1142_at_bggfu2.nho.hydro.com>
Bill Kirk <bilkirk_at_usa.net>
----------------------------------------------------------------------
The question that started it all...
>Hello managers,
>
>We acquired a used AlphaServer 2100 with a SWXCR-EB (3 channel) RAID
>controller. My first job was to remove all instances of Windows NT,
>which was what it was running. My second job is to install OSF/1 3.2.
>
>I am unable to complete an install on the RAID device. After installation
>of the basic system from CD, and a reboot using the RAID device, the system
>finds the boot code, starts loading the kernel until the swapper looks
>for a swap device, then it halts. The messages are:
>
>xcr0 at eisa0
>re0 at xcr0 unit 0 (unit status = ONLINE, raid level = 0)
>lvm0: configured.
>lvm1: configured.
>lvm2: configured.
>bootdevice_parser: unknown protocol name 'RAID'
>setconf: Bootdevice parser failed to translate bootdevice RAID 1 7 0 0 0 0 0.
>boom, crash, tinkle...
>-------------------------------------------
>
>Here is what I have done so far:
>
>I have upgraded the AXP firmware (to whatever comes with 3.2)
>
>Using the ARC (MS-DOS?) firmware I have set the default boot to OSF
>
>I have run the ECU to configure the EISA bus
>
>I have run the RCU to configure the RAID (raid level should be 1)
> The desired boot device is on channel 1, (0 is unused), with disks 0
> and 1 as members of the raid level 1 group. (although the message above
> implies that this is not working!)
>
>I suspect I'm missing another step or two. Any suggestions would be appreciated.
>Thanks.
---------------------------------------------------------------------------
Ted Asocks tra_at_lick.ucsc.edu
Systems Administrator VOICE: (408)459-4020
UCO/Lick Observatory FAX: (408)454-9863
Received on Wed Apr 05 1995 - 12:23:45 NZST