On Sun, 2006-01-15 at 15:06 -0500, John Nall wrote: > Herbert Graf wrote: > > > This is a common problem, the clone went fine. > > > > The problem (and Ghost does the same thing) is that while the clone > > happens the boot manager isn't copied over correctly. This results in > > the "GRUB" you see. > > > . > Well, as you have probably read by now, I have the problem cleared up. > It is nice to know that the clone went OK, however, as I was worried > whether or not there might be other problems that I have yet to > encounter. So apparently there was just that one glitch. > > Just as a side comment, however, it seems to me that if Disk B is not > _exactly _the same as Disk A after the clone operation has completed -- > that the boot manager isn't copied over correctly -- then the clone did > not go fine. I thought the definition of "clone" meant that they were > equal in every respect? You have to be careful of the definition of "clone". If you make a bit-to-bit copy of a Linux drive, and the drive geometry isn't identical, the clone CAN be identical, but you still won't be able to boot. The reason is you DON'T want an exact copy. You want a program that will make an exact copy of all your data, but at the same time be able to "interpret" the "nitty gritty" and modify it accordingly. Examples are the partition table (same partition + different drive geometry = garbage), and the boot sector. Ghost and programs like that "interpret" the partition table and the boot loaders used for windows/dos correctly, but for Linux they simply crap out. It's a shame, and VERY frustrating when you don't understand what's going on, but that's just the way it is. Blame the software makers for not supporting Linux properly, but at least Linux gives you the tools to fix the problem yourself. TTYL ----------------------------- Herbert's PIC Stuff: http://repatch.dyndns.org:8383/pic_stuff/ -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist