Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 23 views

    Cloned Machine Does Not Boot Up Properly: Environment

    Uploaded by

    albie103
    - The document discusses issues that can occur when cloning a virtual or physical machine, such as the filesystems or network not being found on boot up. - This is because persistent device names cause the network and storage devices to be assigned different names than expected. - To resolve the issue, persistent device names must be disabled before cloning or changing hardware, such as by clearing configuration files for network and storage devices.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd

    Cloned Machine Does Not Boot Up Properly: Environment

    Uploaded by

    albie103
    23 views3 pages
    - The document discusses issues that can occur when cloning a virtual or physical machine, such as the filesystems or network not being found on boot up. - This is because persistent device names cause the network and storage devices to be assigned different names than expected. - To resolve the issue, persistent device names must be disabled before cloning or changing hardware, such as by clearing configuration files for network and storage devices.

    Original Title

    Linux Fix Nic Issue

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    - The document discusses issues that can occur when cloning a virtual or physical machine, such as the filesystems or network not being found on boot up. - This is because persistent device names cause the network and storage devices to be assigned different names than expected. - To resolve the issue, persistent device names must be disabled before cloning or changing hardware, such as by clearing configuration files for network and storage devices.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    23 views3 pages

    Cloned Machine Does Not Boot Up Properly: Environment

    Uploaded by

    albie103
    - The document discusses issues that can occur when cloning a virtual or physical machine, such as the filesystems or network not being found on boot up. - This is because persistent device names cause the network and storage devices to be assigned different names than expected. - To resolve the issue, persistent device names must be disabled before cloning or changing hardware, such as by clearing configuration files for network and storage devices.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3

    Cloned machine does not boot up properly

    This document (3048119) is provided subject to the disclaimer at the end of this document.

    Environment
    SUSE Linux Enterprise Server 11 SUSE Linux Enterprise Server 10 SUSE Linux Enterprise Server 9 Novell Open Enterprise Server (Linux based) Novell Open Enterprise Server 1 (OES1) Support Pack 2 Linux Novell Open Enterprise Server 1 (OES1) Support Pack 1 Linux Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 2 Novell SUSE Linux Enterprise Desktop 10 Novell Linux Desktop 9

    Situation

    A virtual machine has been cloned, or a physical machine has been cloned onto identical hardware, or hardware (storage controller and/or network device) has been exchanged on a physical machine, or VMware tools have been installed into a VMware virtual machine. When trying to boot the clone (or changed system), it does not come up properly: the root filesystem or other filesystems are not being found, or the network does not come up, or the network device names have changed.

    Resolution
    Disable the use of persistent network device names and of persistent storage device names prior to cloning or hardware change, or adjust device and interface names afterward.

    Additional Information
    Background: persistent device names Please refer to the product documentation for in-depth background on persistent device names. In short, persistent device names provide stable names for network and storage devices, regardless of the order of recognition or the connection used for the device.

    Related documentation TID 3580082 - New default in SLES/SLED 10 SP1: mount "by Device ID" Persistant Storage Device Names, OpenSUSE wiki article. Disabling the use of persistent network device names (CODE11 products) On CODE11 products like SUSE Linux Enterprise Server 11, the use of persistent network device names is disabled by clearing the /etc/udev/rules.d/70-persistent-net.rules file. Clear the udev configuration for the network devices as follows: cat< /dev/null > /etc/udev/rules.d/70-persistent-net.rules Disabling the use of persistent network device names (CODE10 products) On CODE10 products like SUSE Linux Enterprise Server 10, the use of persistent network device names is disabled in three steps.

    Clear the udev configuration for the network devices. Clear the udev configuration for the network devices as follows: cat< /dev/null > /etc/udev/rules.d/30-net_persistent_names.rules Rename the Ethernet configuration files In order for the Ethernet configuration to come up on boot, the Ethernet configuration has to be renamed. 1. 2. 3. Go to /etc/sysconfig/network Find the ifcfg-eth... file for each Ethernet device (the trailing identifier is the MAC address for the device), for example: ifcfg-eth-id-00:AA:BB:11:22:33 Rename the file to ifcfg-ethX. For example, to have the configuration for eth0 the name would be: ifcfg-eth0

    Change network configuration to not use udev 1. 2. 3. 4. Open /etc/sysconfig/network/config for editing Find the line reading: FORCE_PERSISTENT_NAMES="yes" Change it to: FORCE_PERSISTENT_NAMES="no" Save

    5. Reboot Disabling the use of persistent network device names (CODE9 products) On CODE9 products like SUSE Linux Enterprise Server 9, udev is not used, and is not as involved as in SLE 10. All that needs to be done is to rename the Ethernet configuration file. Rename Ethernet configuration files In order for the Ethernet configuration to come up on boot, the Ethernet configuration has to be renamed. 1. 2. 3. Go to /etc/sysconfig/network Find the ifcfg-eth... file for each Ethernet device (the trailing identifier is the MAC address for the device), for example: ifcfg-eth-id-00:AA:BB:11:22:33 Rename the file to ifcfg-ethX. For example, to have the configuration for eth0 the name would be:ifcfg-eth0.

    Disabling the use of persistent storage device names (CODE11, CODE10 and CODE9 products) On CODE10 & 11 products like SUSE Linux Enterprise Server 10, the use of persistent names for storage devices is recommended in general. As of SLES10 SP1 it has been made the default for new installations. As with network devices, the use of persistent names for storage can cause problems when cloning machines though. To disable the use of persistent storage device names, proceed as follows: 1. 2. Examine the boot loader configuration file /boot/grub/menu.lst and the filesystem table /etc/fstab for the presence of /dev/disk/by-* references. Store the mapping of /dev/disk/by-* symlinks to their targets in a scratch file: ls -l /dev/disk/by-* > /tmp/scratchpad.txt 3. Remove all entries that involve storage that is not local to the system (such as SAN or iSCSI volumes) from the scratch file.

    4. 5.

    Edit /boot/grub/menu.lst and/etc/fstab, replacing the /dev/disk/by-* entries in them which occur in the scratch file by the device names the symlinks point to. Reboot the system and verify that it comes up cleanly.

    Steps to perform in case hardware has been exchanged on a physical machine (Disaster Recovery) In case hardware like storage,network device and/or motherboards with integrated devices has been exchanged on a physical machine, the above steps need to be performed from the SuSE Rescue System. Proceed as follows: 1. 2. 3. 4. 5. 6. Boot off the Installation CD/DVD and choose "Rescue System" Mount the system partition and perform a chroot, as described in TID 3134230 - How to access LVM partitions when system is booted with rescue CD. To disable the use of persistent network and storage device names perform the steps as described in the respective sections above. Exit from chroot (CTRL-D or "exit"). Umount the system partition. Reboot the server.

    You might also like