SUMMARY: can't open osf boot after moving root_domain

From: Cohen, Andy (Andy.Cohen@cognex.com)
Date: Fri Jun 14 2002 - 17:19:37 EDT


Thanks again everybody!! It seems that either my understanding of
diskconfig or diskconfig's capabilities (or lack thereof) caused this to
happen. Basically, it seems that there was no boot block put on the drive
when I used diskconfig.

The solution was to:

1: disklabel -r dsk3 > disklabel.dsk3.out
2: disklabel -z dsk3
3: disklabel -R -r -t advfs disklabel.dsk3.out

step 1 - save current disklabel since I had changed the disklabel partion
sizes
step 2 - zero out the disklabel on dsk3
step 3 - this wrote a boot block of type advfs (-t advfs) using the
disklabel I had just saved

I am now able to boot the machine.

Thanks again so much!!

Andy

ORIGINAL QUESTION
===============
Hi,

I want to move the root_domain (on a 4100 5.1A PK2) to a different device so
I followed the instructions in 5.3.3 and 5.3.4 in the AdvFS Administration
guide:
http://www.tru64unix.compaq.com/docs/base_doc/DOCUMENTATION/V51A_HTML/ARH96C
TE/TOC.HTM#CHPTRTRB
and now when the machine starts to boot it gets a cpu exception at (I think)
'cant open osf boot'.

Here's what I did:

used diskconfig to partition an RZ29B (AdvFS on partition a)
backup / (root) and /usr

boot from CD
mkfdmn -r /dev/disk/dsk3a root_domain
mkfset root_domain root
mount root_domain#root /mnt

mkdir /etc/fdmns/TMP_BACKUP
nkdir /var/tmp_backup
mkfset TMP_BACKUP tmp_backup
mount TMP_BACKUP#tmp_backup /var/tmp_backup

cd /var/tmp_backup
tar -xv #get backup off tape
vrestore -x -f thor.51A.PK2.root.vdump -D /mnt #restore root_domain to new
device

cd /mnt/etc/fdmns/root_domain
ln -s /dev/disk/dsk3a dsk3a
rm -e dsk4a # previous root partition

shutdown -h now
set bootdef_dev dkb400
boot

it gets to 'jumping to bootstrap code' then produces the 'cant open osf
boot' error.

Anybody have any idea what I've done wrong? What if I, in the first 2 steps
above, I did a backup (vdump) first then ran diskconfig for dsk3 -- would
the vrestore overwrite what the diskconfig had done? Should I disklabel
dsk3 again?



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:44 EDT