Hello Managers,
I didn't receive any answers or suggestions from the list, but Compaq's
support was able to solve the problem.
We have a link /tmp -> /var/tmp on most of our machines, to avoid the /
filesystem running out of space when some user or some program fills up
/tmp.
However, when LSM starts in boot mode to encapsulate the root disk, it
wants to write something into /tmp. In our case, /tmp is not available,
because /var is not mounted yet. Once I restored the original /tmp,
everything went fine.
We also learned from this, that a "serial" console is more practical
than a "graphics" one, because one can see all the start-up messages,
not just the last ones. In our case, we couldn't learn something from
the message in my original posting, but
starting LSM
/sbin/lsm-startup: /tmp/sh630: cannot create
was the important message.
Best regards,
Ralf
PS: My original posting was:
Hi Managers,
we bought a DS20E running Tru64 Unix 5.1 (PK3) recently. We ordered an
additional hard drive and a LSM license to do root disk mirroring.
I checked, that the LSM software is installed, that the license is
active, that LSM is present in the kernel (via devswmgr), and I made a
backup of the root disk via vdump and vrestore.
volencap and volreconfig ran successfully. However, the machine doesn't
reboot, it can't mount the filesystems, and the following error message
appears (I'm able to read it, when I boot into single user mode):
Starting LSM in boot mode
lsm:volio:Cannot open disk dsk0a: kernel error 16lsm:vold: WARNING Disk
root01 in group rootdg: Device not found.
The /etc/fdmns directory looks like this:
root_domain/rootdg.rootvol -> /dev/vol/rootdg/rootvol
usr_domain/rootdg.vol-dsk0g -> /dev/vol/rootdg/vol-dsk0g
var_domain/rootdg.vol-dsk0h -> /dev/vol/rootdg/vol-dsk0h
and the disklabel of dsk0 looks ok, with an AdvFS dsk0a, swap dsk0b,
LSMsimp dsk0e, and LSMnoprv dsk0h,f,g.
When I do a "grep lsm /etc/sysconfigtab" in this state, then I get:
lsm:
lsm_rootdev_is_volume = 2
which is strange, as it should be either 0 or 1, but not 2.
Fortunately, I was able to edit /etc/sysconfigtab, to edit the disklabel
of dsk0, and to restore the links in /etc/fdmns, and now the machine is
online again.
Any help is greatly appreciated.
Best regards,
Ralf Eichmann
--
Adr.: Universitaet Marburg Fachbereich Physik, AG HL(Theorie)
Renthof 5 D-35032 Marburg
Tel.: +49 (0)6421 28 24240 Fax: +49 (0)6421 28 27076
Received on Thu Nov 15 2001 - 14:46:40 NZDT