SEO

Greetings,

I recently rebuilt an HP-UX 10.20 system from a Recovery tape. All of the
system data resides across three disk other than the root/boot disk. So the
Recovery strategy employed was to use Ignite to rebuild the root disk only,
then use vgimport / vgchange -a y / mount x to add the disk with existing
file systems (data) back into the system.

First step: (after Recovery completed)

vgscan -v

Second step:

mkdir /dev/vg01
mkdir /dev/vg02
mkdir /dev/vg03

Third step:

mknod /dev/vg01/group c 64 0x010000
mknod /dev/vg02/group c 64 0x020000
mknod /dev/vg03/group c 64 0x030000

Fourth step:

vgimport /dev/vg01 /dev/dsk/c0t1d0
vgimport /dev/vg02 /dev/dsk/c0t2d0
vgimport /dev/vg03 /dev/dsk/c0t3d0

Fifth step:

vgchange -a y /dev/vg01
vgchange -a y /dev/vg02
vgchange -a y /dev/vg03

Sixth step:

vgcfgbackup /dev/vg01
vgcfgbackup /dev/vg02
vgcfgbackup /dev/vg03

Seventh step:

Added these three lines to /etc/fstab:

/dev/vg01/lvol1 /u vxfs rw,suid,delaylog,datainlog 0 2
/dev/vg02/lvol1 /v vxfs rw,suid,delaylog,datainlog 0 2
/dev/vg03/lvol1 /w vxfs rw,suid,delaylog,datainlog 0 2

And finally:

mount /u
mount /v
mount /w

And my problem is that very last step. When I typed "mount /w", the system
complained "no such directory" or "directory not found". The first two
mount points, /u and /v mounted successfully. And the first seven steps as
outlined above all completed successfully, too.

Any ideas as to why /w will not mount?

Thanks,

Stew Weis

> Any ideas as to why /w will not mount?
>
Well, does /w exists? I mean if you do a "ls -l /", do you see /w as a
directory not as a file or a link?
Did you try to mount on a different mount point /x for example?
What does a fsck /dev/vg03/lvol1 say?

Paul