Hi,
Can anyone help me ?
I got following problem when trying to encapsulate existing data.
I started it from both "voldiskadm" and "volencap" command. Parameter
used included partition info e.g. "rz28d".
Problem occurs during the reboot when 2 files in /tmp directory cannot
be found. Unfortunately the messages pass very quickly on the console
and do not seem to be logged anywhere.
The LSM disk is created and imported into the correct diskgroup but the
volume is not created. The "/etc/fstab" file is not changed either, and
the file system is not mounted because of "device busy" because LSM now
holds the disk.
Remedy to regain the disk (get it out of LSM):
voldg -g <groupname> rmdisk <diskname>
voldiks rm <diskname>
I then isued the commands to manually encapsulate the disk:
voldisk -f init <diskname> type=nopriv
voldg -g <diskgroup> adddisk <diskname>
volassist -g <diskgroup> make <volume> <size-in-sectors>s <diskname>
This worked.
Now all my data disks are entered into LSM with success.
I also want to add my system disk (root and swap) but according to the
documentation this can only be done with the "volencap" command.
I do not wish to try this now because it does not seem to work correctly
on my system.
My system is an Alpha 4100 running DU3.2G.
Thank you for your assistance.
Received on Mon Mar 24 1997 - 12:34:43 NZST