On 2014-07-04 16:37 (GMT-0500) David C. Rankin composed:
before spending a couple of hours to find out it won't work..
Adding to what Carlos wrote, the clone may not be in a ready to use state when the clone is complete. Anything in bootloader config or fstab dependent on device ID will break with the clone as the only HD in the system. Some initrds made with dracut get married to the hardware, and won't boot normally when original root device ID is not available at boot time. Sometimes getting around this is merely a matter of waiting for a timeout, then accepting the offered device name as a substitute for the missing device ID. Check /etc/dracut.conf for the state of the hostonly setting to see if this is a potential obstacle for your installation. If it is you should unset it and build a new initrd before cloning. Booting with both source and target attached simulaneously after the clone is complete will result in multiple devices with identical UUIDs too, which also you don't want of any devices affecting the boot process. So, before attempting to use the clone to boot from, take the trouble to restore uniqueness to every device that should be unique. e.g. assign new UUIDs to each filesystem at the very least, and match them to whatever pointers to them exist, if any do, in the bootloader menu and in fstab, which needs to be done after the BIOS and the kernel recognize the existence of the "new" devices on the clone, which I do by a reboot of the cloning media without the original source HD attached. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org