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.
This ones been asked plenty of time but I couldn't seen to find the answer I was looking for. I have a slackware 9.1 box with 2 hardrives hda, hdb. I put slackware on hdb and made hda my /home directory. Then I put lilo on the mbr. When I boot I get a message with some error. I forget exactly what it was.
I messed up the mbr before I put slackware on and it didn't straighten it out.
What should I do?
I'm at work right now so I can't post my lilo.conf file. I just want to get some ideas.
Please be as exact as possible. Not just something like "run fixmbr". I know how to do it with windows but I don't have it on that comptuer.
I didn't look at the active boot flag with fdisk, but I think the mbr is corrupted anyways. Can it be corrupted? What are someways the mbr can become corrupted? Can you tell me what info is in the mbr?
boot flag is irrelevant (it's a windows thing).
You can boot your Slack with the Slack cd. After you boot, you can configure lilo. Remember you need to run 'lilo' to apply changes to lilo.conf. When you get to your pc, post your lilo.conf and the output of 'fdisk -l' here.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,801
Rep:
Quote:
I had a version of slack on hda. Now I'm trying to boot from the hdb HD.
Shouldn't be a problem.
Quote:
I'm guessing that the mbr on hda still has lilo installed on it from before. How can I remove it?
I don't think you need to. A previous post told you how to boot from the Slackware CD so you could fix lilo.conf and reinstall the bootloader. You can install lilo into the MBR of the first drive and have lilo boot linux from the second drive. In fact, my main system does something very similar. My lilo.conf specifies "boot=/dev/sda". but the root filesystem is on /dev/sdc. Works like a charm.
i am having a similar problem here too, i am using 2 hdd's and installing slack 9.1 to hda. when i get to installing lilo it gives an error saying lilo can't be installed. i have a 32mb partition at hda1 from some other linux install, do i need to mount that as /boot/ at the begining of the install process? -do i even need this partition at all ? thanks
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.