Linux, LILO & NO VALID BOOTSECTOR SIGNATURE

[Gelip]

Hi. I have PLOP inserted to motherboard BIOS. This working very good with Windows but now I need make Linux Server Netzonesoft nxp-5.8.513.
1. Deleted all partitions from disk 40GB with Partition Magic 8 (now disk Unallocated)
2. Install Linux server automatic partitioning with LILO Boot Manager
3. In PLOP is 3 Partitions:
HDA PARTITION 1
HDA PARTITION 2
HDA PARTITION 3
but if try boot from their have error: NO VALID BOOTSECTOR SIGNATURE (after selecting HDA 3 have blinking cursor)

I do not understand what's going on?

I started Acronis Disk Director to view disk partitions:

1. Linux native 0x83 Primary, Active 2GB
2. Linux Swap Primary 1GB
3. Linux native 0x83 Logical 1GB
4. Linux native 0x83 Logical 34GB

I tested Linux in VMware Workstation 8 and working good without PLOP but if mounted PLOP ISO image to VMware and trying boot Linux server then have the same situation - in PLOP is 3 HDA partitions and after select have the same error : NO VALID BOOT SECTOR SIGNATURE

[Elmar]

when you choose to boot HDA1 then lilo must be installed on that partition to boot linux.
i  assume you installed lilo to the mbr. when you want to start lilo from the HDA mbr, then press "q" in the main menu and choose the first option.

regards
elmar

[Gelip]

OK, slowly :-):

1. I don't know whether it is LILO in the MBR - probably yes - how to check?
2. Press "q" - where? in PLOP Menu? (In LILO menu no needed press any key - LILO start automatic after 5 sec.)
3. Why motherboard BIOS booting OK Linux and Windows?
4. Why PLOP not booting Linux only Windows?

P.S. I know that other solution is make other PLOP version with support Escape key to exit PLOP and redirect to BIOS boot list but this is a lot of work (my PLOP is from plpbt.bin version):

Difference plpbtrom.bin and plpbt.bin

plpbtrom.bin gives the control of the boot process back to the bios with a far return if you press esc. plpbt.bin makes a reboot with int 19h.

[Elmar]

1. I don't know whether it is LILO in the MBR - probably yes - how to check?

either you look at the mbr with a hex editor and see lilo or you check the line with "boot=" in the file /etc/lilo.conf

2. Press "q" - where? in PLOP Menu? (In LILO menu no needed press any key - LILO start automatic after 5 sec.)

you press "q" in the plop boot manager main menu

[Gelip]

After pressing "q" have this (look at attach image) but not help me :-(. LILO is in MBR right (look attach). This is my lilo.conf:

Code: [Select]

#
# lilo.conf
#
boot = /dev/sda
prompt
timeout = 50
change-rules
  reset
vga = 771
lba32
default = 2.6.35-64-1

image = /boot/2.6.35-64-1/bzImage
  root = /dev/sda1
  label = 2.6.35-64-1
  append = ""
  read-only
  initrd = /boot/2.6.35-64-1/initrd.gz
image = /boot/2.6.35-36-1/bzImage
  root = /dev/sda1
  label = 2.6.35-36-1
  append = ""
  read-only
  initrd = /boot/2.6.35-36-1/initrd.gz
Why motherboard BIOS booting OK Linux and Windows?
Why PLOP not booting Linux only Windows?

[Elmar]

After pressing "q" have this (look at attach image)

this is an old boot manager version

Why PLOP not booting Linux only Windows?

because lilo is in the mbr and when you use hda1 to boot then you boot the boot sector of the first partition and NOT the mbr!

when you dont want to upgrade the plop boot manager then install lilo to the boot sector of the first partition.

[Gelip]

OK, understand :-) but please help me reinstall LILO in Linux (maybe change to GRUB):

1. I deleted LILO from MBR like this:

Code: [Select]

lilo -u /dev/sda2. Restarted PC - and this is not good idea :-(. Then no boot Linux :-(
3. Reinstalled Linux and make this:

Code: [Select]

/sbin/lilo -U /dev/sda
/sbin/lilo -b /dev/sda1but after reboot I see L 99 99 99 99 99...  :-(

[Elmar]

change in /etc/lilo.conf

boot=/dev/sda

to

boot=/dev/sda1

then run the command "lilo" without any parameters as root.

[Gelip]

Your solution not working with PLOP, only working without PLOP from BIOS boot. After run lilo without any parameters get this error (attached image):

[Elmar]

Your solution not working with PLOP, only working without PLOP from BIOS boot.

i dont understand what you want to say with this sentence

After run lilo without any parameters get this error (attached image):

from where did you start lilo, from a live cd?

[Gelip]

One more time from beginning:

1. I have computer with PLOP in motherboard BIOS (plpbt.bin without Escape)
2. In this PC beginning was WinXP SP2 with 2 partitions NTFS
3. Installed Linux Server. This OS autoconfigure HDD and Boot loader LILO
4. After installing this OS I don't possible boot him after restart PC ;-( - PLOP displays NO VALID BOOTSECTOR SIGNATURE

Now make test in VMware how resole this problem
1. Instal Linux Server default - boot OK
2. Make your changes (boot=/dev/sda1 and run lilo without parameters)
3. After reboot Linux boot the same like default
4. NOW - if try boot from PLOP ISO have NO VALID....

Sorry, but I use Google Translator to making posts :-)

[Elmar]

One more time from beginning:

1. I have computer with PLOP in motherboard BIOS (plpbt.bin without Escape)
2. In this PC beginning was WinXP SP2 with 2 partitions NTFS
3. Installed Linux Server. This OS autoconfigure HDD and Boot loader LILO
4. After installing this OS I don't possible boot him after restart PC ;-( - PLOP displays NO VALID BOOTSECTOR SIGNATURE

the lilo command must run without errors to be successful.

Now make test in VMware how resole this problem without PLOP
1. Instal Linux Server default - boot OK
2. Make your changes (boot=/dev/sda1 and run lilo without parameters)
3. After reboot Linux boot the same like default
4. NOW - if try boot from PLOP ISO have NO VALID....

thats no wonder:

when you use bios boot then you have
bios -> loads mbr (it has lilo) -> lilo starts linux

when you use the plop boot manager then
bios -> plop boot manager -> you use hda1 -> the boot manager loads the boot sector of the first partition which has no data -> failure

what you need is lilo in the boot sector to get
bios -> plop boot manager -> you use hda1 -> the boot manager loads the boot sector with lilo -> lilo boots linux



info:
lilo can stay in the mbr and the boot sector at the same time. but when you successful installed lilo to /dev/sda1, then i would write a default mbr program to the mbr for a clean system. (lilo can do that with: lilo -M /dev/sda). then you have
bios -> loads mbr -> mbr loads the boot sector of the marked active partition -> the boot sector has lilo -> lilo starts linux

[Gelip]

Ad. quote1 - LILO install OK but PLOP not boot this OS

I analize what's going on with the MBR drive from beginning:

1. New Unallocated disk have null MBR - 0,0,0...
2. Command fdisk /mbr in DOS insert IPL code to MBR and 55 AA signature (partition table is null - offset 1BE-1FD)

I have that idea:

1. Install Linux autoconfigure HDD & LILO
2. Copy to first linux partition file ntldr+boot.ini or copy grldr and rename to ntldr + menu.lst and configure files boot.ini and menu.lst to boot linux
3. In hex editor replace IPL offset MBR 0-1BD linux to data from the same offset WinXP partition

Now PLOP probably boot from disk, disk IPL code search ntldr file and boot.ini run linux
or
PLOP boot disk, disk IPL code search ntldr, ntldr is renamed GRUB :-)) which search menu.lst config :-)

What do you think? Is this will work?

[Elmar]

What do you think? Is this will work?

no

[Gelip]

He, he. Working !

I try this:

1. In working WinXP rename ntldr file to ntldrxp
2. Copy to root C:\ file grldr (GRUB4DOS) and rename this to ntldr
3. Make menu.lst file in root C:\ like this:

Code: [Select]

default 0

title WinXP
find --set-root /ntldrxp
chainloader /ntldrxp4. Reboot computer from PLOP ISO e.g.
5. Select HDA PARTITION 1 in PLOP

[Gelip]

In linux partitions is XFS file system. I found this info:

Q: Does LILO work with XFS?

This depends on where you install LILO.

Yes, for MBR (Master Boot Record) installations.

No, for root partition installations because the XFS superblock is written at block zero, where LILO would be installed. This is to maintain compatibility with the IRIX on-disk format, and will not be changed.

Maybe this is problem ?! LILO must be installed on MBR if XFS file system?

[Elmar]

Maybe this is problem ?! LILO must be installed on MBR if XFS file system?

oh man, 100% thats the problem. i cannot guess that you use that file system. why dont you use ext3!?! forget the auto partitioning. be the master of your system!


EDIT:
quick and easy convert:

i assume /dev/sda1 was your / file system
boot a livecd
mount /dev/sda1
copy all files from /dev/sda1 to another partition in a directory
umount /dev/sda1
mkfs.ext3 /dev/sda1
mount /dev/sda1
copy back all files from sda1
chroot to /dev/sda1
run "lilo"
reboot

[Gelip]

OK, I worked it out already :-)

First, I created partitions on whole disk with Partition Magic. Next installed Linux to second primary partition - Linux installer write LILO to MBR (this distribution have possibility to change install partition). Next installed WinXP to first primary, active partition - Windows installer rewrite own IPL in MBR. Next copying GRUB4DOS to first partition NTFS C:\ like this and make menu.lst:

Code: [Select]

default 0
timeout 5

title Windows XP Professional SP2
find --set-root /ntldrxp
chainloader /ntldrxp

title Netzonesoft NxD 5.8.513 x86
root (hd0,1)
kernel /boot/2.6.29.2-32-1/bzImage
initrd /boot/2.6.29.2-32-1/initrd.gz
boot
In PLOP menu is 4 Partitions but booting only working from first and automatic run GRUB4DOS. Now I choose OS to boot :-) but PLOP is not helpful in this case :-(. This configuration works the same without PLOP.

[Gelip]

P.S. I know that other solution is make other PLOP version with support Escape key to exit PLOP and redirect to BIOS boot list but this is a lot of work (my PLOP is from plpbt.bin version):

Difference plpbtrom.bin and plpbt.bin

plpbtrom.bin gives the control of the boot process back to the bios with a far return if you press esc. plpbt.bin makes a reboot with int 19h.

Of course, there is another possibility :-). Pressing 'D' key to disable run PLOP but of course this statement:
6. In BIOS settings need DISABLE all boot options. BIOS boot capabilities no longer needed - now use PLOP :-): is not true 

PLOP is very nice boot manager but non standard in relation to BIOS boot:

[Gelip]

PLOP display error because Linux install LILO default in MBR on /dev/sda. That the error did not appear needs to install LILO on /dev/sda1 :-) . Same with other distributions of Linux, for example Debian - you need to install GRUB on /dev/sda1: