Hard Drive Upgrade
Hello, I just recently upgraded the hard drive on my Debian machine (an intel box running potato), and while everything copied successfully, I could not get the new hard disk to boot. I then changed my lilo.conf to point to /boot/vmlinuz-2.2.14 instead of the symlink at /vmlinuz, and everythinig worked fine. Does anyone know what's going on here? How come lilo doesn't recognize the symlink like it did before? If you any more information, just let me know. Thanks. -- Daniel Kruszyna
Hard Drive Upgrade
Hello, I just recently upgraded the hard drive on my Debian machine (an intel box running potato), and while everything copied successfully, I could not get the new hard disk to boot. I then changed my lilo.conf to point to /boot/vmlinuz-2.2.14 instead of the symlink at /vmlinuz, and everythinig worked fine. Does anyone know what's going on here? How come lilo doesn't recognize the symlink like it did before? If you any more information, just let me know. Thanks. -- Daniel Kruszyna
Re: Hard Drive Upgrade
Actually, come to think of it, even though the new drive wouldn't boot at first, it still got as far as Loading Linux, so I guess it might not be a lilo problem after all. The boot process got to Loading Linux, but not to Uncompressing Linux. Changing the image= in my lilo.conf from /vmlinuz to /boot/vmlinuz-2.2.14 still made the drive bootable though. Anybody know what's going on here? -- Daniel Kruszyna
Re: Hard Drive Upgrade
On 19 May 2000, Karl M. Hegbloom wrote: Had you run `lilo' on the new drive before you tried to reboot? If not, then what it was is that the kernel isn't at the same block address as it was on the other disk... Yes, I followed the instructions at http://www.linuxdoc.org/HOWTO/mini/Hard-Disk-Upgrade.html which does explain how to run lilo on the second disk and make it look like it is the first one. I think LILO did find the kernel, because I did get the Loading Linux.. message, but the boot never got to the Uncompressing Linux stage. -- Daniel Kruszyna
