Jump to content
  • Announcements

    • spinynorman

      Mandriva Official Documentation

      Official documentation for extant versions of Mandriva can be found at doc.mandriva.com.   Documentation for the latest release may take some time to appear there. You can install all the manuals from the main repository if you have Mandriva installed - files are prefixed mandriva-doc.
    • paul

      Forum software upgrade   10/29/17

      So you may have noticed the forum software has upgraded !!!
      A few things that have changed. We no longer have community blogs (was never really used) We no longer have a portal page.
      We can discuss this, and decide whether it is needed (It costs money) See this thread: Here
Guest DirecX

Lilo [solved]

Recommended Posts

Guest DirecX

I'm fairly new to linux, but I am learning rather quickly. After I updated mandrake, 10.0 official, I went to change a setting or two with Lilo and for some reason all information in regards to it's settings etc was, to my surprise, gone. Out of curiosity i looked at Lilo's config file and all of the information was there. I changed what i wanted to change there, yes i did change it correctly, and saved it and rebooted. Lilo was there but the modifications that I had made to it were not. I re-did my modifications and there was no change. I attempted to re-install Lilo two ways. First I opened the kernel and typed su, then /sbin/lilo -v and I received the error "Fatal: File system would be destroyed by LILO boot sector:/dev/hda1" I then attempted to re-install it by booting off of CD 1 of the install and it gave me the same error. Would it be best to un-install Lilo and remove mandrake and re-install it?

 

Thankx

Share this post


Link to post
Share on other sites

Any time you make changes in lilo, you must also run "lilo -v" in order for the changes to take effect. I am not sure what the results are of reinstalling the ways you describe.

 

Boot Mnadrake, Open a console and su to root. Type "lilo -v" . If you get an error, it is possible you have installed lilo into two different areas. I always use the mbr. The warning might be given if your edits are going to cause some sort of error. Why not post the lilo you wish to run and let's check it out for any possible issue.

Share this post


Link to post
Share on other sites
Guest DirecX

I did as you susgested with the lilo -v command and I recieved the same error:"Fatal: File system would be destroyed by LILO boot sector:/dev/hda1". Also how do you view the mbr in the console? :unsure:

 

Here is my lilo.conf file:

 

# File generated by DrakX/drakboot
# WARNING: do not forget to run lilo after modifying this file

boot=/dev/hda1
map=/boot/map
default="windows"
keytable=/boot/us.klt
prompt
nowarn
timeout=600
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label="linux"
root=/dev/hda7
initrd=/boot/initrd.img
append="devfs=mount acpi=ht splash=silent"
vga=788
read-only
image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/hda7
initrd=/boot/initrd.img
append="devfs=mount acpi=ht"
read-only
image=/boot/vmlinuz-i686-up-4GB
label="linux-i686-up-4GB"
root=/dev/hda7
initrd=/boot/initrd-i686-up-4GB.img
append="devfs=mount acpi=ht splash=silent"
read-only
image=/boot/vmlinuz-p3-smp-64GB
label="linux-p3-smp-64GB"
root=/dev/hda7
initrd=/boot/initrd-p3-smp-64GB.img
append="devfs=mount acpi=ht splash=silent"
read-only
image=/boot/vmlinuz-2.6.3-7mdk
label="263-7"
root=/dev/hda7
initrd=/boot/initrd-2.6.3-7mdk.img
append="devfs=mount acpi=ht splash=silent"
read-only
image=/boot/vmlinuz-smp
label="linux-smp"
root=/dev/hda7
initrd=/boot/initrd-smp.img
append="devfs=mount acpi=ht splash=silent"
read-only
image=/boot/vmlinuz
label="failsafe"
root=/dev/hda7
initrd=/boot/initrd.img
append="failsafe acpi=ht devfs=nomount"
read-only
other=/dev/hda1
label="windows"
table=/dev/hda

Edited by DirecX

Share this post


Link to post
Share on other sites

Uninstall lilo first. See if you get any warnings like "no lilo installed" or such.

Share this post


Link to post
Share on other sites

I think this is the problem:

 

 

other=/dev/hda1  
label="windows"

 

This is your Windows partition as far as I can tell and it probably is NTFS

 

 
boot=/dev/hda1  

 

You are trying to put the bootloader on the Windows partition. That will never work, I think.

 

Change boot=/dev/hda1 to boot=/dev/hda (to put the bootloader in the MBR) or boot=/dev/hda7 (to put lilo on your Linux partition).

 

Then run lilo -v or lilo -cv (if you want it to boot faster).

 

I always put the bootloader in the MBR. I never had any trouble with it there.

 

I hope this helps. ;)

Edited by a13x

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×