User Tools

Site Tools


how_to_clone_tru64_and_digital_unix

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
how_to_clone_tru64_and_digital_unix [2018/12/11 17:02]
sgriggs [Fix the Sysconfigtab]
how_to_clone_tru64_and_digital_unix [2019/06/25 06:40] (current)
sgriggs [It Boots but It's Horked Up]
Line 24: Line 24:
   - Do not try to eliminate the /usr file system for UFS __and__ AdvFS. Startup scripts in **/​sbin/​init.d** will force you to have it and freak out (stopping the boot process) if you don't. Don't try to consolidate those unless you plan on manually editing every single startup script and fixing them, which isn't worth it.    - Do not try to eliminate the /usr file system for UFS __and__ AdvFS. Startup scripts in **/​sbin/​init.d** will force you to have it and freak out (stopping the boot process) if you don't. Don't try to consolidate those unless you plan on manually editing every single startup script and fixing them, which isn't worth it. 
   - You might have read about **sysman** clone features. Forget that. That tool is garbage and will cause you much more pain than it saves you. Plan on doing it manually yourself or have an expert do it for you using this process. ​   - You might have read about **sysman** clone features. Forget that. That tool is garbage and will cause you much more pain than it saves you. Plan on doing it manually yourself or have an expert do it for you using this process. ​
-  - Do not plan on using the **dd** method unless you have completely identical disks. That has several major drawbacks otherwise. The worst include performance problems (due to bad geometry alignment on the disklabel) and loss of space if the target disk is larger (or loss of __data__ if the target disk is smaller). ​+  - Do not plan on using the **dd** method unless you have completely identical disks. That has several major drawbacks otherwise. The worst include performance problems (due to bad geometry alignment on the disklabel) and loss of space if the target disk is larger (or loss of __data__ if the target disk is smaller). ​However, just to say we shared the actual command if you cloned an identical dsk1 onto a dsk2 in tru64 5.x it'd be this command: **dd if=/​dev/​disk/​dsk1c of=/​dev/​disk/​dsk2c bs=1024k**
  
 ==== Take Inventory ==== ==== Take Inventory ====
Line 252: Line 252:
 Depends on why and where it hangs. The most common issues are these. ​ Depends on why and where it hangs. The most common issues are these. ​
  
-  - You forgot to edit out some kind of reference to the swap device. Check the post-copy steps again. One of the startup scripts probably tried to activate swap on a device that won'​t. ​+  - You forgot to edit out some kind of reference to the swap device. Check the post-copy steps again. One of the startup scripts probably tried to activate swap on a device that won't. Remember that you can use single user mode to fix these issues without doing a full re-install. References to swap could be in in the __/​etc/​fstab__ (usually on 4.x or older systems) and could also be inside of your __/​etc/​sysconfigtab__ which is usually the case on 5.x systems.
   - You are using UFS and you forgot to fix the reference to the **/​etc/​fstab** for one of the file systems. You might also have to edit any reference for swap, especially on Digital Unix 4.x. Also pay attention for any other filesystems that might have changed or gone away.    - You are using UFS and you forgot to fix the reference to the **/​etc/​fstab** for one of the file systems. You might also have to edit any reference for swap, especially on Digital Unix 4.x. Also pay attention for any other filesystems that might have changed or gone away. 
-  - Make sure your copy method preserved all the permissions,​ especially on **/sbin** and the scripts in **/​sbin/​init.d** which are critical.  +  - Make sure your copy method preserved all the permissions,​ especially on **/sbin** and the scripts in **/​sbin/​init.d** which are critical. Those scripts should be executable and owned by the __root__ or __bin__ users.  
-  - Do NOT try to eliminate one of the AdvFS file domains. As mentioned earlier, the startup scripts reference both **root_domain** and **usr_domain** and if you change their names or eliminate one of them the startup scripts will fail. +  - Do NOT try to eliminate one of the default ​AdvFS file domains ​(one for root and another for /usr). As mentioned earlier, the startup scripts reference both **root_domain** and **usr_domain** and if you change their names or eliminate one of them the startup scripts will fail.  
 +  - Make sure your SRM variables for __boot_file__ and or __boot_flags__ may be incorrect and have old VMS data in there or some other garbage. Your boot file should be your kernel, which is usually __/vmunix__ or __/​genvmunix__. Your boot flags should be **A** or **S** but not a number, if it's a number it came from VMS and it's wrong. People who re-use VMS systems for Tru64 will run into these problems often. ​  
 + 
 +===== It Boots but It's Horked Up ===== 
 + 
 +  - Double check your swap is pointing to the right place and working (swapon -s) 
 +  - Make sure your filesystems are not showing up with weird or generic names. Double check your source and destination device and make sure that your old device name isn't still leftover in a config file somewhere. Most commonly it's the **/​etc/​fstab** or bad disk-symlinks in **/​etc/​fdmns**. Also it's also worth perusing **/​etc/​sysconfigtab** on 5.x for mistakes or old device names. 
 +  - Make sure if you use a new system type that any kernel tuning you do makes sense. Ie.. if you take parameters from a system that has 4GB of RAM and try to use them on a big GS1280 with 64GB of RAM then you are almost certainly going to have some bad tuning in there. Double check your __sysctl__ settings with **sysctl -a**
  
 If you have problems beyond the ones documented, then consider contacting PARSEC for some consulting work to help you! If you have problems beyond the ones documented, then consider contacting PARSEC for some consulting work to help you!
how_to_clone_tru64_and_digital_unix.1544547760.txt.gz · Last modified: 2018/12/11 17:02 by sgriggs