incorrect LILO selection SLACK install - no boot from hda1
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
incorrect LILO selection SLACK install - no boot from hda1
Hello...
During the Slack install process I was being walked through it over the phone by an experienced Slack user which really helped things move along.
The one thing we overlooked was the proper selection when it came time to install LILO.
I think I was given a choice as to whether or not to over write the MBR and my guide told me not to. I think he may have thought I was going to set up a dual boot device. I'm not. Slackware is the only OS.
Now the system needs a floppy at boot, which I'm not really comfortable with. I would like the system to boot normally like it should which leads me to this question:
I have read some methods for reinstalling and reconfiguring LILO in the Slack Book. All of it seems to make sense but it it one of those things I am not comfortable doing without some guidance. What I think I want to do is overwrite the MBR with LILO so it is the only resident boot loader on the system. People have said it can be done - but I really wouldn't know where or how to start.
Boot up Slackware with the floppy
Click terminal mode, type "su", supply the password and become the super user witb the root privileage to amend the system file
The Lilo comman "lilo -b" allow you to put Lilo anywhere you wish to
Code:
lilo -b /dev/hda
put Lilo in the first IDE disk
Code:
lilo -b /dev/sda
put Lilo in the first Sata disk
Only you know which your book disk hda or sda boot first so choose the one that is at the top of the booting queue.
Code:
lilo -b /dev/fd0
puts Lilo in the floppy
Code:
lilo -b /dev/hda9
puts Lilo in the partition hda9 and so on
The last alternative is for the OS residing in hda9 to be booted by the boot loader controlling the MBR.
Lastly if you alter /etc/lilo.conf you must issue the "lilo" command in a terminal so that the bootloader is re-compiled, otherwise the changes will not be implemented.
The boot disk is an IDE. I followed the normal convention of formatting the drives hda1 - hda2 - hda3...
I haven't made any modifications to /etc/lilo.conf.. Will I have to make some changes after performing the above commands? Or does performing the above commands make alterations to the .conf file which in turn requires me to issue the lilo command at the end.. Just so I understand.. Thank you...
If you Lilo boots fine from the floppy then there is no need to change it. I just remind you of the characrteristic of Lilo.
Lilo, Grub and XP's NTLDR actually all keep the boot loader in the root partition of the hard disk. To boot it from the MBR a user must ask the boot loader to replicate its first 512 bytes there and burn the boot loader address into it too to form a link.
If Lilo has a probelm to boot then you can only make it toe the line by amending /etc/lilo.conf. Right? After amendments you must issue "lilo" as a command in a Bash shell so that Lilo recompiles its boot loader.
If Lilo boots satisfactorily then its /etc/lilo.conf has no error and so you should leave it alone.
Thanks this thread fixed my problem. I installed slackware over a ubuntu install and used the same option as the origional post by studioq. But the mbr still had grub in it. and grub could not find stage1 so
Code:
lilo -b /dev/hda
replaced grub with lilo and now I don't need the floppy to boot.
I am glad this helped. I tried to make the title key word specific so that someone with the same issue could find it. I have yet to perform this operation.. Many fish to fry.. But I will report my results here..
It still didn't work. I am probably doing something wrong..
I tried to make the modifications to lilo by typing:
lilo -b /dev/hda
and got a response of "Ignoring entry 'boot' - Added Linux.
The system wont boot from disk...
When I type su nothing happens either. Should I be looged on as someone other than root when I ussue the 'su' command? Or could it be a problem that I never set an su password?
I only ask because I dont know..
Thank you..
Only a root user is allowed to touch the system files in Linux, so persevere with it.
When Lilo returns the message "added Linux" it means the compilation was successful and the distro was added without any error.
The above is Lilo's part in not finding any syntax error in the /ect/lilo.conf. The content inside has been found executable as Lilo check each entry during compilation. If one or two commands are rubbish then there is nothing Lilo can do as it just execute them one by one. No other boot loader bothers to check the correctness of the figuration entries, except Lilo.
If your system still refuses to boot can you paste the error message here? A complete printout of /etc/lilo.conf helps also.
Slackware is the easiest distro in the world to boot with only a standard kernal name as "vmlinuz" and no initrd file.
In fact if there is any distro that I have difficulty in booting 75% of them can be fired up by using Slackware's kernel.
If you log in as root the command "su" should cause no response.
A lot of your so call problems isn't real.
Ignoring entry 'boot' = Lilo doesn't make much use of your "boot = /dev/hda" statement.
Linux doesn't use active flag in a partition and so any complaint is irrelevant.
I couldn't fault your lilo.conf as you haven't pasted the error during booting. I would try to put a "#", thus disabling that line, in front all the lines except
One other thing someone mentioned today is that there may be some system bios issue that is hanging it up. That is one thing I dont know about though. I am going to try to cause the error. I also dont know where I can find an error log for the boot process. If I can find that I will paste it too.... Here we go..
When the system finishes POST - I get no boot error. It just sits there. Normally It would tell me if it couldn't find a boot device. But this one just sites there.
After perfoming the above commands this is the text that was output:
root@filebox:/etc# lilo
Warning: RAID1 install implied by omitted 'boot='
Warning: Partition 1 on /dev/hda is not marked Active.
Added Linux *
root@filebox:/etc#
Usage: fdisk [-b SSZ] [-u] DISK Change partition table
fdisk -l [-b SSZ] [-u] DISK List partition table(s)
fdisk -s PARTITION Give partition size(s) in blocks
fdisk -v Give fdisk version
Here DISK is something like /dev/hdb or /dev/sda
and PARTITION is something like /dev/hda7
-u: give Start and End in sector (instead of cylinder) units
-b 2048: (for certain MO disks) use 2048-byte sectors
After entering th "-l" parameter I got this:
root@filebox:~# fdisk -l
Disk /dev/hda: 61.4 GB, 61471162368 bytes
255 heads, 63 sectors/track, 7473 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 3000 24097468+ 83 Linux
/dev/hda2 3001 6000 24097500 83 Linux
/dev/hda3 6001 7473 11831872+ 82 Linux swap
root@filebox:~#
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.