Thanks to
<BAISLEY_at_vssaxp.fnal.gov>
<alan_at_nabeth.cxo.dec.com>
The short answer to my question is - Yes there is a simple way ;-)
Their answers and my original question attached.
--------------------------------------------------------------
From: Alan
Since around V3.2 or V3.0 you haven't needed to rebuild the kernel
to add new disks at all. The device scanning code may not look
for it, but the SCSI driver will. You can verify what the SCSI
driver has found by using scu(8) and the "show edt" command. You
do have to add configuration lines for new disk controllers, but
not disks. Use the GENERIC configuration for samples what lines
need to be added, if you want to avoid going through genvmunix.
-----------------------------------------------------------
From: Wayne
I have added disks to my Alpha systems with no downtime.
The new drive will be rz9, being SCSI ID 1 on the second SCSI bus.
I'd do this:
cd /dev
./MAKEDEV rz9
Then, to make sure you can talk to the drive:
/sbin/scu -f /dev/rrz9a show device
After that, you're off to te races.
-----------------------------------------------------
My original question
Hi,
On my Alpha (running 3.2d-1), I'd slapped in a RZ29B-VA a
few weeks ago. Now I need to use it without booting genvmunix and
rebuilding the kernel using doconfig -c HOSTNAME.
The last disk active I added was the first disk on the second controller
DKB0. This new disk shows up as DKB100.
The entry in the config for the last disk looks like this -
device disk rz8 at scsi1 drive 64
Is it safe to assume that the new disk would be rz9 ? and if so does
the following entry look right -
device disk rz9 at scsi1 drive 72
If I add the above line and rebuild my kernel, would it be OK ? I want
to mimimize my downtime and reduce the number of stages (i.e avoid
booting genvmunix etc..)
Thanks in advance.
Anil Khullar
Graduate School & University Center
CUNY,
33 W 42nd Street,
New York NY 10036
Received on Thu Feb 20 1997 - 19:06:46 NZDT