On Sat, 2003-11-22 at 18:37, Michael Kraus wrote: > G'day... > > Ahh, well, afaik (this was true for LILO anyway), the boot loader doesn't > actually reference a file by the filename, but rather the size and offset of > the file on the drive.
grub understands the file system. So grub can handle disk defragmentation, partition resizing etc all just fine - as long as partition order and #'s don't change. The break of grub on the origin drive is the key: it means that grub was already broken, or broken during the image process. Or, if the partition #'s changed (say a primary becoming an extended) it would break things, as grub references fields relative to the parition. As to what could break grub, if the /boot partition (the 'install location of grub') changes, then the installed info for grub will be incorrect, and grub won't be able to read menu.lst, which is the list of what to boot. Recovering would normally be as simple as putting in manual boot details (the root, kernel and initrd commands), booting, and then running grub-install to update grub. Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>.
signature.asc
Description: This is a digitally signed message part
-- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
