Clonning TRU64 OS disk

[adam yeong]

I had already clone an OS TRU64 disk using "disklabel -R -r -t advfs" command. I had also change the root, usr & var domain link as well as swap disk. When I try to boot up, it came out a lot of error, especially can't access to sbin.
Can anyone give some advice?

Thks

[Vladimir Fabecic]

More details are needed.
Can you describe exactly what you did?
"disklabel -R -r -t advfs" is just a first step. What else did you do?

[Mark Poeschl_2]

As Vladimir said, more info is needed, but one of the first places that comes to mind would be to look at the /etc/fstab file on the cloned disk. The fstab entries on the clone must match the cloned configuration, not the original.

[adam yeong]

Firstly, i create a tmproot, tmpusr & tmpvar mount point. Then i manually mount it. After that, i use vdump & vrestore to the new clone disk. After the process end, i clone the source disklabel to the target disk. Then I manually mount the tmproot, tmpvar & tmpusr again. After that I change the root_domain & usr_domain (var share usr domain)link to the new target disk through /tmproot/etc/fdmns. I had also change the swap disk to the new target disk partition. Finally, I shutdown the system to SRM and remove the original OS disk and try to bootup with new cloned disk but it bootup with a lot error, especially can't access sbin.

thks

Adam

[Vladimir Fabecic]

Try this (for version 5.x):
Lets say that your new disk should be dsk7 and you did disklabel command properly.
# mkfdmn /dev/disk/dsk7a root1_domain
# mkfset root1_domain root
# mkfdmn /dev/disk/dsk7g usr1_domain
and so on for all partitions
Then manually mount new root, usr and var to temporary mount point.
Then do vdump-vrestore to temp mouunt points.
After that edit /etc/fstab in /tmproot to match new definitions.
DO NOT change /etc/fdmns links!
This should work because I use this procedure to make spare boot disks. I did it many times.
If you need more specific procedure, ask for it.

[adam yeong]

Inside the /etc/fstab, what need to edit ?
For the /etc/fdmns, if not changing the link how the root1_domain work as root_domain?
After all the step you had provided, can it be bootup separately?

Pls advice.

[Vladimir Fabecic]

First, what is your OS version?
For version 5.x:
Replace
root_domain#root / advfs rw 0 1
with
root1_domain#root / advfs rw 0 1
and so on.
Device name of disk should stay unchanged.
You problem is disk device name. That is why I said not to change /etc/fdmns links.
You can also try this to find more details:

>>> boot -flag 0 DKXXXX
# mountroot

[adam yeong]

MY OS version is Tru64 5.1B with patch kit 6

[Vladimir Fabecic]

So you have 5.1B.
Good! Now reread my posts.
My procedure would be like:
1. "disklabel -R -r -t advfs" some disk (for example dsk7). This step you did well.
2. Make partitions for advfs and swap. You did it.
3. Make advfs domains:
# mkfdmn /dev/disk/dsk7a root1_domain
# mkfset root1_domain root
and so on for all file systems
4. Mount newly created file systems to their temporary mount points
# mount -t advfs root1_domain#root /tmproot
and so on for every file system
5. Do vdump-vrestore to new file systems
6. Now edit /tmproot/etc/fstab
to be like
root1_domain#root / advfs rw 0 1
(i.e. replace old file systems with new)
usr1_domain#usr advfs rw 01
and so on
7. Edit /tmproot/etc/sysconfigtab
replace
swapdevice=/dev/disk/dsk0b
with
swapdevice=/dev/disk/dsk7b
8. umount all temporary file systems
DO NOT change /etc/fdmns entries !!!

When you boot from new system disk, it will be dsk7!
Once you boot normally you can change domain names if you want.

I use this procedure to create spare boot disk and did it many times. It works for sure.
Please post did you make it.

[adam yeong]

I had go through the step u had provide me, it still having error when i try to bootup for the new disk. The error messages as below:
INIT:Command is respawning too rapidly.
Check for possible errors.
id:esmd "/usr/sbin/esmd
/dev/null2 >&1"

INIT:Command is respawning too rapidly.
Check for possible errors.
id:cons "/usr/sbin/getty console console
vt100"

Pls advice.
thks

Yeong.

[Vladimir Fabecic]

esmd is Essential Services Monitor daemon and it it started by /etc/inittab.
Not sure why you have problem with that.
Can you describe step by step how you did the cloning?
Can you boot to single user mode?
Can you do "# mount -a" after that without errors?

[Vladimir Fabecic]

By the way,
you can also clone boot disk using bttape.
See "# man bttape".