Many fine answers, looks like the problems last year were from not
using the '-t advfs' option to disklabel. For the archives I'll
include the responses. Thanks to all!
----- Forwarded message from "David J. DeWolfe" <sxdjd_at_java.sois.alaska.edu> -----
If the intended boot device lives behind an HSZ controller, the device
needs to be a LUN 0 device. Other than that, make sure you use the "-t
advfs" parameter on the disklabel. See "man disklabel" for details. you
should then be able to boot the device.
----- Forwarded message from "Degerness, Mandell ISTA:EX" <Mandell.Degerness_at_gems2.gov.bc.ca> -----
First, re1a needs to be made a "root" advfs domain (mkfdmn -r).
Then, you will need to ensure that /etc/fdmns (on re1a) has the domains
pointing to the correct devices.
Finally, if the hardware for your DRP test is not identical to your
production hardware, you will probably need to boot genvmunix and rebuild
the kernel as part of the exercise.
----- Forwarded message from alan_at_nabeth.cxo.dec.com -----
When you create the file system on the target drive you
need to:
A. Not use the option of the disklabel command that
tell it not to write the boot blocks. The default
is to write boot blocks.
B. Do use the option to indicate the file system type,
if it isn't UFS. UFS is the default.
So, if your root is going to be AdvFS, you need to label
the target disk with:
# disklabel -wr -t advfs re1 swxcr
If the offsite system vendor, is providing these disks
and/or file system for you, you need to make sure they
have sufficient information to correctly pre-create
anything you need. By the same token, if they didn't
have a clue what was needed, but were expected to have
a clue, then maybe a different vendor is in order.
----- Forwarded message from Robert Honore <robert_at_digi-data.com> -----
To make a disk bootable, you would need to use the disklabel command in the
following manner.
disklabel -rw /dev/rre1a /mdec/reboot.advfs /mdec/bootre.advfs
where "-rw" is to write the label onto the physical disk
"/dev/rre1a" is the character special device file for the physical disk
"/mdec/reboot.advfs" is the Primary Boot parameter (the boot block)
"/mdec/bootre.advfs" is the Secondary Boot parameter (the secondary boot block)
After this, just make the requisite filesets and copy the data and you are all
set.
----- Forwarded message from "Dr. Tom Blinn, 603-884-0646" <tpb_at_doctor.zk3.dec.com> -----
When you write the new disklabel onto re1, make sure you specify "-t advfs"
or you'll get a UFS boot block by default. That should be all it takes.
Of course, "re1a" must be at the beginning of the volume..
--
Daniel Monjar (mailto:dmonjar_at_orgtek.com)
"If your attack is going really well, it's an ambush."
Received on Mon Dec 04 2000 - 18:45:54 NZDT