[SOLVED] Lilo multi boot problem

ldmn · 05-31-2010, 11:19 AM

Greetings.

I cant multi-boot from Zenwalk lilo to Vector Linux, although it succeeds to boot to Zenwalk and Windows.

A similar issue was solved here: (http://www.linuxquestions.org/questi...indows-781695/), but this helped me not, although I removed the read-only line from Lilo.

So I present my specs, and thank you if you can help.

My Zenwalk config:
Lilo in MBR
partitions recognized as SDA

Lilo default lines:
append="resume=/dev/sda5 splash=silent"
...
image=/boot/vmlinuz
root = /dev/sda2
label = Zenwalk
initrd = /boot/initrd.splash
read-only

My inserted Vector-specific lines:
image=/boot/vmlinuz
root=/dev/sda3
label= Vector

My Vector config:
Lilo is in its boot sector
partitions recognized as HDA

Error messages when booting to Vector and getting frozen:
-Can't translate "/dev/sda5" into a device id yet
-VFS: Cannot open root device "803" or unknown-block(8,3)
-Please append a correct "root=" boot option; here are the available partitions:
hda driver: ide disk
hda1
hda2
......
hda8
-Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3)

foodown · 05-31-2010, 04:11 PM

Well, the copy of LILO installing to the MBR is the only one that will matter. There is no sense in additionally installing one to your boot sector . . .

I wonder if, since the Vector system knows the IDE drives as "hdx," you need to change the inserted Vector root line to reference the root partition in that way . . . Only problem is, I could see lilo complaining when you try to reinstall it into the MBR.

The problem is that LILO is telling the Vector kernel to mount its root fs from /dev/sda3, and it doesn't call that block device by that name. It calls it /dev/hda3.

Why does the error message say "/dev/sda5?"

What happens when you change the line from "root=/dev/sda3" to "root=/dev/hda3"? Will lilo recycle?

If it won't install lilo after you change that, could you post your entire lilo.conf file from the Zenwalk system?

ldmn · 05-31-2010, 10:01 PM

Thank you for help.

So only one LILO is needed in the MBR, I didn't know that, but tried it that way too.
When only one LILO was placed in the MBR (either of Zenwalk or Vector) and no additional was installed in any boot sector, then:
-neither Zenwalk nor Vector could recognise each other's presence (-as with 2 LILOs). What's more, manually setting up LILO in Zenwalk's install program with expert option caused error when trying to write LILO to MBR. Only simple lilo setup was successful.
-If I manually edited Zenwalk's Lilo conf, hoping for a selectable Vector: system got frozen while loading Vector (with my aging laptop's 2 leds blinking misteriously for ever), without showing any error message.

I don't know why /DEV/SDA5 is shown in error messages, perhaps because of this LILO.conf line:
append="resume=/dev/sda5 splash=silent "

After changing "root=/dev/sda3" to "root=/dev/hda3", then unfortunately LiLo doesn't add Vector to selectable items. (adds only Zenwalk and Windows).

Here's my Lilo conf:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="resume=/dev/sda5 splash=silent "
boot = /dev/sda
bitmap=/boot/splash.bmp
bmp-table=234p,348p,1,4
bmp-colors=220,0,,255,220,
bmp-timer=539p,396p,220,0,
prompt
timeout = 50
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x64k
vga = 791
# 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

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = Zenwalk
  initrd = /boot/initrd.splash
  read-only
# Linux bootable partition config ends

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda3
  label = Vector
# Linux bootable partition config ends

# Windows bootable partition config begins
other = /dev/sda1
  label = Windows
  table = /dev/sda
# Windows bootable partition config ends

foodown · 05-31-2010, 10:15 PM

Okay, I think I have your fix.

First, boot your Zenwalk system.

Open your lilo.conf file in a text editor.

Change it to this:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# append="resume=/dev/sda5 splash=silent "
boot = /dev/sda
bitmap=/boot/splash.bmp
bmp-table=234p,348p,1,4
bmp-colors=220,0,,255,220,
bmp-timer=539p,396p,220,0,
prompt
timeout = 50
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x64k
vga = 791
# 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

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = Zenwalk
  initrd = /boot/initrd.splash
  append="resume=/dev/sda5 splash=silent "
  read-only
# Linux bootable partition config ends

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda3
  label = Vector
  append="root=/dev/hda3"
# Linux bootable partition config ends

# Windows bootable partition config begins
other = /dev/sda1
  label = Windows
  table = /dev/sda
# Windows bootable partition config ends

Then, run 'lilo' as root. It should install LILO into the MBR with the above config. A reboot at this point should yield the desired functionality . . . let me know if it doesn't.

ldmn · 05-31-2010, 11:26 PM

Victory is yours / ours !

so the lines with append were missing.

Thanx much.

foodown · 06-01-2010, 11:28 AM

Awesome! I always feel nervous about posting a script or config without the ability to test it locally . . . Glad it worked!