[SOLVED] Boot sector of installed Vector Linux doesn't have a boot signature

ic_torres · 02-13-2011, 06:02 PM

upon adding the installed VL on the existing LILO.. (btw i have not installed its LILO on the installation setup) since i know that i will just add it to the "existing" LILO

the error above arises upon doing the lilo run command..

$adding Vector6.0 etc....
FATAL : Boot sector of /dev/hdc13 doesn't have a boot signature

1. i have tagged the /dev/hdc13 bootable via CFDISK. but same problem arises..

ntubski · 02-13-2011, 08:46 PM

Are you chainloading the Vector partion in lilo.conf? Like this:

Code:

other = /dev/hdc13

In that case you would need to install a bootloader in /dev/hdc13 as well. Otherwise you can boot the Vector kernel directly with

Code:

image = /mnt/hdc13/boot/vmlinuz # path to the Vector Linux kernel
  initrd = /mnt/hdc13/boot/initrd.gz # if initrd is used

ic_torres · 02-14-2011, 05:48 AM

here is my existing LILO's content :

Quote:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
append = "=ide-scsi"
default = linux
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
bitmap = /boot/bitmap/boot.bmp
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769

# End LILO global section
# Partition 1 : DOS/Windows
other = /dev/hda1
label = Windows
table = /dev/hda
# Partition 2: Linux GUI mode
image = /boot/vmlinuz
root = /dev/hdc3
label = linux
append = " "
read-only

# Partition 3: Linux TUI mode
image = /boot/vmlinuz
root = /dev/hdc3
label = linux-tui
append = "2 "
read-only

# Partition 4: Linux GUI mode
image = /boot/vmlinuz
root = /dev/hdc3
label = Vector5.8
append = "4 "
read-only

# Partition 5: Linux
#image = /boot/tamu/vmlinuz-linux-hdc2
#root = /dev/hdc2
#label = ZW4.6.1
#read-only
#initrd = /boot/tamu/initrd-linux-hdc2

# Partition 6: Linux
#image = /boot/tamu/vmlinuz-vector-hdc12
#root = /dev/hdc12
#label = Vector6.0
#read-only

# Partition 7 : Linux
#other = /dev/hdc5
#label = Slackware

# Partition 8: OpenBSD
other = /dev/hdc1
label = OpenBSD

# Slackware
other = /dev/hdc5
label = Slack12.0

# Zenwalk
other = /dev/hdc2
label = Zenwalk4.6.1

# Vector6.0
other = /dev/hdc13
label = Vector6.0
root@slackerz:/mnt/vl/etc#

ic_torres · 02-14-2011, 06:54 AM

and here is the LILO of the installed VL6.0

Quote:

# Partition 1 : DOS/Windows
other = /dev/sda1
label = Win
table = /dev/sda
# Partition 2: Linux GUI mode
image = /boot/vmlinuz
root = /dev/sda6
label = linux
append = "splash=silent "
read-only
initrd = /boot/initrd
# Partition 3: Linux TUI mode
image = /boot/vmlinuz
root = /dev/sda6
label = linux-tui
append = "2 splash=silent "
read-only
initrd = /boot/initrd
# Partition 4: Linux GUI mode
image = /boot/vmlinuz
root = /dev/sda6
label = linux-gui
append = "4 splash=silent "
read-only
initrd = /boot/initrd
# Partition 5: Linux
image = /boot/tamu/vmlinuz-vector-sda3
root = /dev/sda3
label = vector-sda3
read-only

# Partition 6: Linux
image = /boot/tamu/vmlinuz-vector-sda5
root = /dev/sda5
label = vector-sda5
read-only

# Partition 7: Linux
image = /boot/tamu/vmlinuz-vector-sda7
root = /dev/sda7
label = vector-sda7
read-only
initrd = /boot/tamu/initrd-vector-sda7
# Partition 8: Linux
image = /boot/tamu/vmlinuz-vector-sda8
root = /dev/sda8
label = vector-sda8
read-only
initrd = /boot/tamu/initrd-vector-sda8

ntubski · 02-14-2011, 07:52 PM

Since you are chainloading Slackware and Zenwalk I'll assume you want to chainload Vector as well. You should have at least this in the Vector Linux lilo.conf:

Code:

boot = /dev/hdc13
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
prompt
timeout = 1200

# Vector6.0
image = /vmlinuz # path to Vector Linux kernel from its root filesystem
  label = Vector6.0
  initrd = /initrd.gz # if needed

Then run lilo from Vector Linux, or run lilo -r /mnt/hdc13 from your main distro. Then you should be able to rerun lilo from your main distro without error.

ic_torres · 02-14-2011, 08:13 PM

do you mean that i just need to add this lines on the "Vector6.0" LILO file?

Quote:

boot = /dev/hdc13
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
prompt
timeout = 1200

# Vector6.0
image = /vmlinuz # path to Vector Linux kernel from its root filesystem
label = Vector6.0
initrd = /initrd.gz # if needed

did i get it right?

then run lilo to update the file. ..
then reboot.. then try to load the VL6.0 again. . .

ic_torres · 02-15-2011, 04:24 PM

BIG THANKS to ntubski. . .you gave me the idea