how_to_clone_tru64_and_digital_unix
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
how_to_clone_tru64_and_digital_unix [2019/06/25 05:09] – sgriggs | how_to_clone_tru64_and_digital_unix [2021/06/01 19:26] – [Editing the Disklabel] sgriggs | ||
---|---|---|---|
Line 149: | Line 149: | ||
In general, if you are cloning a UFS based system, then be very careful that your disklabel is going to give you enough space for the **/** and **/usr** file systems. If you are using AdvFS make sure that the total slices you set aside can be used to add up to the sizes you need (ie.. remember that AdvFS can do concatination, | In general, if you are cloning a UFS based system, then be very careful that your disklabel is going to give you enough space for the **/** and **/usr** file systems. If you are using AdvFS make sure that the total slices you set aside can be used to add up to the sizes you need (ie.. remember that AdvFS can do concatination, | ||
+ | ==== Creating File Systems ==== | ||
+ | |||
+ | test | ||
==== File Copy Steps ==== | ==== File Copy Steps ==== | ||
Line 252: | Line 255: | ||
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' | + | - 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 __/ |
- You are using UFS and you forgot to fix the reference to the **/ | - You are using UFS and you forgot to fix the reference to the **/ | ||
- | - Make sure your copy method preserved all the permissions, | + | - Make sure your copy method preserved all the permissions, |
- | - 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 |
+ | - 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 __/ | ||
+ | |||
+ | ===== 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 **/ | ||
+ | - 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: 2023/09/08 23:04 by sgriggs