Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You can only make Lilo to boot again if the source and target disks are indentical in size and you have mirrored faithfully the image from one to anther.
Lilo relies on the exact position in the disk to boot the system so any change of its partition position relative to the hard disk will render Lilo useless.
----------------------
You can get out of your trouble by booting up the PC with a Live CD, make a tempoarary directory in /mnt, monut your REd Hat partition on it, change root to the temp. directory and restore Lilo into the MBR.
mkdir /mnt/sda1 <----assuming Red Hat in sda1
mount /dev/sda1 /mnt/sda1
chroot /mnt/sda1 <----now you are inside Red Hat
lilo -b /dev/sda <---------tell Lilo to replicate itself in the MBR of your first Sata disk
exit
reboot
Watch the reply from Lilo after issuing the lilo -b command because Lilo will tell you problem it encounters.
Your dd statement can be very dangerous because the 1st 512 bytes include the partition table. If the two disks are of different size then that statement will kill the 2nd disk.
One of the many reasons why I suggest grub, instead of LILO. It's simply a smarter loader, and when something goes south it puts you in an environment where you can realistically do something about it. Well worth looking into, and switching to, imho.
Lilo can be a bit rough but it is as tame as Grub if you know how to handle it. I think every Linux user should face it head on as about 40% of the distros are still using it.
There is nothing wrong with it. Grub is just simpler and has a capacity to do bigger things, like runs without being attached to an operating system or to boot 100+ systems without losing a breath.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.