Hello Tim, Thanks for the message, this I will try on sunday. Am I correct in thinking that the clone will only boot when connected to the original server's motherboard (ie in its place) due to specific settings and configs being copied over. In other words it will fail to boot if on any system other than the original? Thanks for the advice, this is kind of a last measure as I did not want to take the original server down; it seems that all else has failed (thanks to all that helped). Khaled -----Original Message----- From: fedora-list-bounces@xxxxxxxxxx [mailto:fedora-list-bounces@xxxxxxxxxx]On Behalf Of Tim Sent: 19 October 2005 11:35 To: For users of Fedora Core releases Subject: Re: installing a grub/lilo bootloader on the MBR of a MOUNTED hdd On Wed, 2005-10-19 at 10:51 +0100, Khaled wrote: > I have duplicated a running server (sella) on my network to an empty > hdd (sellaCone) mounted as /mnt/sellaClone on another hdd hosting > Fedora 3 (host hdd=hda, sellaClone=hdc). Since I am cloning only the > primary partition, only hdc2 is being cloned (suse 9.2 puts swap > partition as hdc1). > > My problem is that having duplicated all imported info/directories, I > need to create a bootloader on the MBR so that the disk can be booted > on its own. I did it this way when I transferred to a bigger drive: Do all the drive content copying. Remove the old drive, leaving the new drive as the boot drive. Boot from the rescue CD. Chroot into the drive, as the prompt says. Run: grub-install /dev/hda Since I was swapping drives, I didn't bother working out if I could install a bootloader to another drive while the old drive was still in the box. For more information, read the GRUB info file, it's more detailed than its man file. Or look at its website. -- Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
