> One of guys hit this issue too. I don't know what he had to fix in > grub's menu, but I know the final fix wa in /etc/fstab, so don't > forget to have your friend update that as well. > > We actually do a lot of cloning of our lab machines. We edited the > grub/fstab fields to go back to /dev/sda, etc. prior to making the > clone. Our machines are similar enough that it works for us. > > If there is a better way, we're all ears. > > Greg > -- > Greg Freemyer > Litigation Triage Solutions Specialist > http://www.linkedin.com/in/gregfreemyer > First 99 Days Litigation White Paper - > http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf
My installation of 10.3 showed that both menu.lst (GRUB) and fstab uses the ID of the disk (is that called the UUID?). Understandably, you need to edit both menu.lst and fstab to get the clone working properly. The former will allow you to start the kernel whereas the latter lets you mount the disk. IIRC, during the installation, there is an option under the advanced section for partitioning for you to choose whether you want to use the ID or the device name (e.g. /dev/sda). If you were to install a new OS, take a look at the advanced options for partitioning. Regardless, even after changing both menu.lst and fstab to use, say, /dev/sda1, you will need to ensure that the cloned disk is recognised in the same order when its placed into a new system. i.e. the BIOS recognises it as /dev/sda and not /dev/sdb. Cos if the order is wrong, the entry in menu.lst/fstab will be incorrect as well. Any other input? -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
