lsm has done its own thing when I tried to change boot disks.

From: MacDonell, Dennis (DennisMacDonell@auslig.gov.au)
Date: Tue Jul 15 2003 - 02:21:19 EDT

Next message: Bona Craig: "Tru64 Copy Problem"
Previous message: Wayne Blom - Systems Specialist: "[SUMMARY] Printing queue order, what determines the order."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi,

I have just installed 5.1B over lsm on a compaq workstation, which
previously was running 5.1 from another lsm boot disk. In preparation for
the install, I partitioned my 9gb disk, and then did the install. After the
install, I noticed from "volprint -A" that the new installation had picked
up the private partition from the previous installation. Now I can't seem to
get lsm to let the disk go.

disklabel dsk1 returns
  a: 1053463 0 unused 0 0 # 0 -
207*
  b: 4129573 1053463 unused 0 0 # 207*-
1020*
  c: 35565080 0 unused 0 0 # 0 -
7000
  d: 4129573 5183036 unused 0 0 # 1020*-
1833*
  e: 16994060 1576960 unused 0 0 # 310*-
3655*
  f: 16994060 18571020 unused 0 0 # 3655*-
7000
  g: 26210146 9312609 4.2BSD 1024 8192 16 # 1833*-
6992*
  h: 42325 35522755 LSMsimp # 6992*-
7000

volprint -A returns
Disk group: rootdg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0
PUTIL0
dg rootdg rootdg - - - - - -

dm disk2g dsk2g - 7705556 - - - -
dm dsk1h dsk1h - 38229 - - - -
dm dsk2h dsk2h - 98304 - - - -
dm root01 dsk2a - 524288 - - - -
dm swap01 dsk2b - 6291456 - - - -
dm usr01 dsk2f - 3145728 - - - -

As you can see the offending partition is dsk1h

I have tried
(a) disklabel -z dsk1 (that appears to work, then)
     disklabel -wr dsk1 (which returns the message)
     disklabel: ioctl DIOCSDINFO: Open partition would move or shrink
    Use alternate partition

(b) voldisk rm dsk1h
lsm:voldisk: ERROR: Device dsk1h: Device is in use

My thinking is that
(a) need to get all the information off of dsk1h and onto dsk2h,
(b) need to remove dsk1h from lsm
(c) then I should be able to setup a new label for dsk1

At the moment I feel that if I force a new label onto dsk1, then lsm might
break.

The other approach might be to shutdown the machine, disconnect dsk1, go
through a new install, at least up to the point where it fixes up lsm's
tables.

Thanks
Dennis

######################################
Dennis Macdonell
Systems Administrator
National Mapping Division, Geoscience Australia
######################################

Next message: Bona Craig: "Tru64 Copy Problem"
Previous message: Wayne Blom - Systems Specialist: "[SUMMARY] Printing queue order, what determines the order."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:27 EDT