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 [2019/06/25 06:30]
sgriggs [It Hangs During Boot]
how_to_clone_tru64_and_digital_unix [2019/06/25 06:40]
sgriggs [It Boots but It's Horked Up]
Line 257: Line 257:
   - 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.    - 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.  ​   - 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.txt ยท Last modified: 2019/06/25 06:40 by sgriggs