Howdy folks,
I have just had my first taste of setting up the boot disk under LSM and
believe that things are not well??
I issued the following command to initialise the encapsulation process:
/usr/sbin/volencap re0
There were 2 free partition table entries a sshown by the output of
disklabel
# size offset fstype [File system]
a: 135168 0 4.2BSD /
b: 2097152 135168 unused swap
c: 4110336 0 unused
d: 282624 2232320 4.2BS /varD
e: 0 0 unused
f: 0 0 unused
g: 978944 2514944 4.2BSD /usr
h: 616448 3493888 4.2BSD /usr/local
I then rebooted system whereupon several error messages were displayed:
Nov 9 19:40:25 lpbpc0 vmunix: cam_logger: CAM_ERROR packet
Nov 9 19:40:25 lpbpc0 vmunix: cam_logger: bus 1 target 0 lun 0
Nov 9 19:40:25 lpbpc0 vmunix: ss_device_reset_done
Nov 9 19:40:25 lpbpc0 vmunix: Bus device reset has been performed
Nov 9 19:40:25 lpbpc0 vmunix: vm_swap_init: warning /sbin/swapdefault swap
device not found
Nov 9 19:40:25 lpbpc0 vmunix: vm_swap_init: in swap over commitment mode
Nov 9 19:40:25 lpbpc0 vmunix: Starting secondary cpu 1
Nov 9 19:40:25 lpbpc0 vmunix: xcr_logger: XCR_ERROR packet
Nov 9 19:40:25 lpbpc0 vmunix: xcr_logger: cntrl 0 unit 1
Nov 9 19:40:25 lpbpc0 vmunix: re_complete
Nov 9 19:40:25 lpbpc0 vmunix: I/O failed
Nov 9 19:40:25 lpbpc0 vmunix: Hard Error Detected
Nov 9 19:40:25 lpbpc0 vmunix: Active XCR_COM at time of error
Nov 9 19:40:25 lpbpc0 vmunix: Active Controller Working Set at time of
error
Nov 9 19:40:25 lpbpc0 vmunix: xcr_logger: XCR_ERROR packet
Nov 9 19:40:26 lpbpc0 vmunix: xcr_logger: cntrl 0 unit 1
Nov 9 19:40:26 lpbpc0 vmunix: re_complete
Nov 9 19:40:26 lpbpc0 vmunix: I/O failed
Nov 9 19:40:26 lpbpc0 vmunix: Hard Error Detected
Nov 9 19:40:26 lpbpc0 vmunix: Active XCR_COM at time of error
Nov 9 19:40:26 lpbpc0 vmunix: Active Controller Working Set at time of
error
Nov 9 19:40:26 lpbpc0 vmunix: xcr_logger: XCR_ERROR packet
Nov 9 19:40:26 lpbpc0 vmunix: xcr_logger: cntrl 0 unit 1
Nov 9 19:40:26 lpbpc0 vmunix: re_complete
Nov 9 19:40:26 lpbpc0 vmunix: I/O failed
Nov 9 19:40:26 lpbpc0 vmunix: Hard Error Detected
Nov 9 19:40:26 lpbpc0 vmunix: Active XCR_COM at time of error
Nov 9 19:40:26 lpbpc0 vmunix: Active Controller Working Set at time of
error
Nov 9 19:40:26 lpbpc0 vmunix: xcr_logger: XCR_ERROR packet
Nov 9 19:40:26 lpbpc0 vmunix: xcr_logger: cntrl 0 unit 1
Nov 9 19:40:26 lpbpc0 vmunix: re_complete
Nov 9 19:40:26 lpbpc0 vmunix: I/O failed
Nov 9 19:40:26 lpbpc0 vmunix: Hard Error Detected
Nov 9 19:40:26 lpbpc0 vmunix: Active XCR_COM at time of error
Nov 9 19:40:26 lpbpc0 vmunix: Active Controller Working Set at time of
error
Nov 9 19:40:27 lpbpc0 vmunix: xcr_logger: XCR_ERROR packet
Nov 9 19:40:27 lpbpc0 vmunix: xcr_logger: cntrl 0 unit 1
Nov 9 19:40:27 lpbpc0 vmunix: re_complete
Nov 9 19:40:27 lpbpc0 vmunix: I/O failed
Nov 9 19:40:27 lpbpc0 vmunix: Hard Error Detected
Nov 9 19:40:27 lpbpc0 vmunix: Active XCR_COM at time of error
Nov 9 19:40:27 lpbpc0 vmunix: Active Controller Working Set at time of
error
Nov 9 19:40:27 lpbpc0 vmunix: ADVFS: using 4662 buffers containing 36.42
megabytes of memory
A subsequent disklabel showed:
# size offset fstype
a: 135184 0 4.2BSD
b: 2096624 135696 swap
c: 4110336 0 unused
d: 282624 2232320 4.2BSD
e: 135168 16 LSMpubl
f: 512 135184 LSMpriv
g: 978944 2514944 4.2BSD
h: 616448 3493888 4.2BSD
The output from volprint -ht showed an enabled rootvol:
plex rootvol-01 rootvol ENABLED 135168
The docs gave examples of output and how to backout using "zapping" but
from the point of issuing the volencap command my system's output didn't
match docs.
QUESTIONS??????
Where is swapvol?
Has the encapsulation process worked?
What are my next steps if this process has failed?
---------------------------------------------------------------------
Drew Ibbotson, Unix Systems Administrator, BHP Information Technology
Address: PO Box 21, Whyalla, Australia 5600
Phone: +61 86 404596 Fax: +61 86 404760
Email: drewi_at_itwhy.bhp.com.au _or_ wwibbd_at_lpdwhy.bhp.com.au
Received on Sat Nov 09 1996 - 11:08:11 NZDT