=================== BUG #4245: FULL BUG SNAPSHOT =================== http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4245&group_id=68
Submitted by: None Project: GNU GRUB Submitted on: Wed 07/09/2003 at 05:37 Category: None Severity: Major Priority: None Bug Group: Software Error Resolution: None Assigned to: None Status: Open Release: GNU GRUB 0.93 Reproducibility: Every Time Planned Release: Summary: Copying a hard drive and making the copy bootable is hard Original Submission: I'm making copies of my hard drive. To do this, I turn off my computer, plug in another hard drive, turn it on, and type: fdisk /dev/hdb (create hdb1 (/boot), hdb3 (/)) mke2fs -j /dev/hdb1 mke2fs -j /dev/hdb3 mkdir /mnt/hdb3 mount /dev/hdb3 /mnt/hdb3 mkdir /mnt/hdb3/boot mount /dev/hdb1 /mnt/hdb3/boot tar cl / | (cd /mnt/hdb3; tar xp) cd /boot tar cl . | (cd /mnt/hdb3/boot; tar xp) grub-install --root-directory=/mnt/hdb3 hdb umount /mnt/hdb3/boot umount /mnt/hdb3 shutdown -r 0 What I want to happen is for the new hard drive to become bootable when it's the only hard drive (hda). What I sometimes get is an error saying that it can't find hdb in the bios list. On other occasions, it clobbers the grub on hda hard disk so that it boots to the grub command line. As these are serial-console machines, it appears that the machine just isn't booting at all, but in reality, it's booting to the non-existent screen on the non-existent graphics card. What I'd like is a fool-proof method of making /dev/hdb bootable when it becomes /dev/hda in a new computer. A FAQ entry would be enough. Thanks! -- [EMAIL PROTECTED] No Followups Have Been Posted CC list is empty No files currently attached For detailed info, follow this link: http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4245&group_id=68 _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub
