My Favorites

Close

Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

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 11 Service Pack 4 (SLES 11 SP4)
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

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. Go to /etc/sysconfig/network
  2. 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
  3. 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. Open /etc/sysconfig/network/config for editing
  2. Find the line reading:
    FORCE_PERSISTENT_NAMES="yes"
  3. Change it to:
    FORCE_PERSISTENT_NAMES="no"
  4. 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. Go to /etc/sysconfig/network
  2. 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
  3. 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. Examine the boot loader configuration file /boot/grub/menu.lst and the filesystem table /etc/fstab for the presence of /dev/disk/by-* references.
  2. 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. 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.
  5. Reboot the system and verify that it comes up cleanly.
Network persistent device names

As of SLES 11 SP4 the behavior to disable persistent naming changed. In order to disable reboot persistent udev rules please create the following file with no content: /etc/udev/rules.d/75-persistent-net-generator.rules. This empty file overrides /lib/udev/rules.d/75-persistent-net-generator.rules and thus prevents the creation of udev rules for network devices, even if the file was deleted.

A different approach is to use the PCI BUS-IDs instead of the MAC address. This has the advantage in hardware environments, that defective NICs can be replaced without any change, else the network needs to get reconfigured. This can be done in YaST2:
  1. start yast2 lan
  2. select the NIC and press edit
  3. click on the hardware tab
  4. select change to edit the udev rules
  5. change from MAC address to BUS ID for the selected ethernet device
  6. save the changes and exit YaST2
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. Boot off the Installation CD/DVD and choose "Rescue System"
  2. 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.
  3. To disable the use of persistent network and storage device names perform the steps as described in the respective sections above.
  4. Exit from chroot (CTRL-D or "exit").
  5. Umount the system partition.
  6. Reboot the server.

Change Log

Updated for CODE11 / SLES11

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:3048119
  • Creation Date:08-JAN-08
  • Modified Date:12-AUG-16
    • SUSESUSE Linux Enterprise Desktop
      SUSE Linux Enterprise Real Time Extension
      SUSE Linux Enterprise Server

Did this document solve your problem? Provide Feedback

< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center