Dear Tru64 Inmates,
It would appear that the 5.1 install read my bootdef_dev
variable, which was pointing to a disk "other" (old v4.x OS) than
the one I was using to perform the full installation, and then
used that to find some configuration data (good or bad) and apply
to my new install.
I would recommend setting the bootdef_dev variable to "", before
performing a full installation of 5.1. Especially if you are
keeping an old v4.x boot disk around on the system.
Thanks to Dr. Tom who seemed to pinpoint the cause and to others
who offered helpful suggestions.
Regards,
....Sean
The original question follows:
Sean McInerney wrote:
>
> Somewhat of a follow up to last weeks v4.x and v5.x differences
> and LSM question.
>
> Turbolaser was upgraded to v5.1 using Full Installation. I used
> the volsave command to backup the LSM configuration prior. After
> a successful 5.1 install, I ran the volrestore command to bring
> back my LSM config:
>
> *******************
> # volrestore -d /tmp/v5save
>
> Using LSM configuration from /tmp/v5save
> Created at Mon Feb 5 14:04:08 EST 2001 on HOST xxxxx
>
> Would you like to continue ? [y,n,q,?] (default: n) y
>
>
>
> /etc/vol/volboot does not exist. To restart LSM this
> file is required.
>
> Restore saved copy of /etc/vol/volboot? [y,n,q,?] (default: y) y
>
> Working...
>
> Restoring rootdg
>
> vol01 in diskgroup rootdg already exists. (Skipping ..)
> ********************
>
> Why does it skip this volume?
>
> # mount /dev/vol/rootdg/vol01 /mnt
> Error: partition /dev/vol/rootdg/vol01 is marked 'unused'.
>
> However volprint shows the volume as active and enabled.
>
> TIA,
> ....Sean
>
--
Sean P. McInerney, Staff SA
Sybase Inc.
561 Virginia Road
Concord, MA 01742
seanm_at_sybase.com
978-287-1668(voice) (978)815-5989(cell) (978)287-2504(fax)
Received on Tue Feb 13 2001 - 16:18:28 NZDT