LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   strange LiLo problem...? (http://www.linuxquestions.org/questions/slackware-14/strange-lilo-problem-4175440543/)

WiseDraco 12-08-2012 02:31 AM

strange LiLo problem...?
 
Hello!
set up yesterday Salckware x32 14.0 on wife-s netbook eeepc 1000, and get a strange problem.
that system have an a two ssd discs:
sda - 8 Gb with installed on it Xandros from factory, sda1 is bootable partition
sdb - 32 Gb second SSD, previosly installed on it slack 12.2, lilo

on previously system ( slackware 12.2 with lilo) i have in lilo.conf
for xandros
other = /dev/sda1
label = Xandros
table = /dev/sda

and all works fine - if i choose "Xandros", then he loads fast and without questions.
system boots from first (sda) disc, as so, mbr is on sda
now i set a slackware 14.0. and configure lilo analogically as old -

other = /dev/sda1
label = Xandrosss
table = /dev/sda

and after choose "Xandrosss" at start, i got a
"Loading Xandrosss", and after second -

Error 2: Bad file or directory type

Error 2: Bad file or directory type

Press any key to continue...

***And after i press "anykey", i got a table with "normal boot / Perform Disk Scan / Restore Factory Settings".
if i choose normal boot - get again Error 2: Bad file or directory type , press any key

maybe anyone know, what is changed in lilo between these slackwares distro, and how i can get working my xandros too? slack 14 from that lilo starting without problems....

slugman 12-08-2012 03:06 AM

hmm
 
Any luck if you boot into slack14, and retry running lilo?

Boot into slack14, edit /etc/lilo.conf with vi (if neccessary), and rerun lilo.

If there is anything awry with the setup, lilo should spit out some errors when it is adding the boot entries.

WiseDraco 12-08-2012 03:23 AM

Quote:

Originally Posted by slugman (Post 4845025)
Any luck if you boot into slack14, and retry running lilo?

Boot into slack14, edit /etc/lilo.conf with vi (if neccessary), and rerun lilo.

If there is anything awry with the setup, lilo should spit out some errors when it is adding the boot entries.

it is always done in this morning. also comment off table= option - without any changes. lilo output at config update ( lilo -v -v )is ok, without general errors.
i think, this is general lilo problem... i also encounter some another problem ( not remember correctly) via old slackware (12.2) and new one (14 ) also on lilo - but not remeber precise, cannot use in lilo.conf other=/dev/sdX for another linux system on another disc in new lilo version or so on....then,as i remeber, lilo says an error on install stage, but not remember details - remember only, on old suystems, pre - 13.37 i never encounter that situation in that configurations....

markush 12-08-2012 03:48 AM

Hello,

I would recommend that you post the output of
Code:

fdisk -l
and your complete lilo.conf

Markus

WiseDraco 12-08-2012 04:19 AM

2 Attachment(s)
Quote:

Originally Posted by markush (Post 4845038)
Hello,

I would recommend that you post the output of
Code:

fdisk -l
and your complete lilo.conf

Markus


Code:

fdisk -l
Disk /dev/sda: 8069 MB, 8069677056 bytes
255 heads, 63 sectors/track, 981 cylinders, total 15761088 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x29642963

  Device Boot      Start        End      Blocks  Id  System
/dev/sda1  *          63    6425999    3212968+  83  Linux
/dev/sda2        6426000    15727634    4650817+  83  Linux
/dev/sda3        15727635    15743699        8032+  c  W95 FAT32 (LBA)
/dev/sda4        15743700    15759764        8032+  ef  EFI (FAT-12/16/32)

Disk /dev/sdb: 32.3 GB, 32279224320 bytes
255 heads, 63 sectors/track, 3924 cylinders, total 63045360 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x90599059

  Device Boot      Start        End      Blocks  Id  System
/dev/sdb1  *          63    63045359    31522648+  83  Linux

lilo.conf actual:

Code:


# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
compact        # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Append any additional kernel parameters:
append=" vt.default_utf8=1"
prompt
timeout = 50
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# 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
# ramdisk = 0    # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb1
  label = Slack
  read-only  # Partitions should be mounted read-only for checking

image = /boot/vmlinuz-generic-3.2.29
 initrd = /boot/initrd.gz
  root = /dev/sdb1
  label = Slack_gen
  read-only  # Partitions should be mounted read-only for checking


# Linux bootable partition config ends
# Linux bootable partition config begins

other = /dev/sda1
label = Xandrosss

##  table = /dev/sda
#  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

lilo -v -v -v output:

Code:


LILO version 23.2 (released 09-Apr-2011)
  * Copyright (C) 1992-1998 Werner Almesberger  (until v20)
  * Copyright (C) 1999-2007 John Coffman  (until v22)
  * Copyright (C) 2009-2011 Joachim Wiedorn  (since v23)
This program comes with ABSOLUTELY NO WARRANTY. This is free software
distributed under the BSD License (3-clause). Details can be found in
the file COPYING, which is distributed with this software.
Compiled at 14:13:34 on Aug 20 2012
Running Linux kernel 3.2.29 on i686

Warning: LBA32 addressing assumed
device-mapper major = 253
raid_setup returns offset = 00000000  ndisk = 0
 BIOS  VolumeID  Device
Reading boot sector from /dev/sda
pf_hard_disk_scan: ndevs=2
  0800  29642963  /dev/sda
  0810  90599059  /dev/sdb
Resolve invalid VolumeIDs
Resolve duplicate VolumeIDs
  0800  29642963  /dev/sda
  0810  90599059  /dev/sdb
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = 3
device codes (canonical) = 3
Device 0x0800: BIOS drive 0x80, 255 heads, 981 cylinders,
              63 sectors. Partition offset: 0 sectors.
Using Volume ID 29642963 on bios 80
Device 0x0811: BIOS drive 0x81, 255 heads, 3924 cylinders,
              63 sectors. Partition offset: 63 sectors.
Using Volume ID 90599059 on bios 81
mode = 0x03,  columns = 80,  rows = 25,  page = 0
Using BITMAP secondary loader
Calling map_insert_data
Secondary loader: 19 sectors (0x3800 dataend).
Warning: The boot sector and map file are on different disks.
bios_boot = 0x80  bios_map = 0x81  map==boot = 0  map S/N: 90599059
Mapping bitmap file /boot/slack.bmp
Device 0x0811: BIOS drive 0x81, 255 heads, 3924 cylinders,
              63 sectors. Partition offset: 63 sectors.
Using Volume ID 90599059 on bios 81
width=640 height=480 planes=1 bits/plane=8
Calling map_insert_file
Compaction removed 26 BIOS calls.
Bitmap: 28 sectors.
BIOS data check was okay on the last boot
image_menu_space = 16

Boot image: /boot/vmlinuz -> vmlinuz-huge-smp-3.2.29-smp
Device 0x0811: BIOS drive 0x81, 255 heads, 3924 cylinders,
              63 sectors. Partition offset: 63 sectors.
Using Volume ID 90599059 on bios 81
Setup length is 32 sectors.
Compaction removed 11617 BIOS calls.
Mapped 11838 sectors.
Added Slack  *
    <dev=0xe1,hd=75,cyl=66,sct=199>
    "ro root=811  vt.default_utf8=1"

Boot image: /boot/vmlinuz-generic-3.2.29
Device 0x0811: BIOS drive 0x81, 255 heads, 3924 cylinders,
              63 sectors. Partition offset: 63 sectors.
Using Volume ID 90599059 on bios 81
Setup length is 31 sectors.
Compaction removed 5450 BIOS calls.
Mapped 5572 sectors.
Mapping RAM disk /boot/initrd.gz
Device 0x0811: BIOS drive 0x81, 255 heads, 3924 cylinders,
              63 sectors. Partition offset: 63 sectors.
Using Volume ID 90599059 on bios 81
Compaction removed 6844 BIOS calls.
RAM disk: 6954 sectors.
The initial RAM disk will be loaded in the high memory above 16M.
Added Slack_gen  +
    <dev=0xe1,hd=75,cyl=66,sct=204>
    "ro root=811  vt.default_utf8=1"

Name: /dev/sda1  yields MBR: /dev/sda  (with primary partition check)
Boot other: /dev/sda1, on /dev/sda, loader CHAIN
Device 0x0801: BIOS drive 0x80, 255 heads, 981 cylinders,
              63 sectors. Partition offset: 63 sectors.
Using Volume ID 29642963 on bios 80
Device 0x0800: BIOS drive 0x80, 255 heads, 981 cylinders,
              63 sectors. Partition offset: 0 sectors.
Using Volume ID 29642963 on bios 80
Compaction removed 0 BIOS calls.
Mapped 6 (4+1+1) sectors.
Added Xandrosss
    <dev=0xe1,hd=75,cyl=67,sct=165>

 BIOS  VolumeID  Device
  80    29642963    0800
  81    90599059    0810
Writing boot sector.
/boot/boot.0800 exists - no boot sector backup copy made.
Map file size: 36352 bytes.
RAID device mask 0x0000
Failsafe check:  boot_dev_nr = 0x0800 0xfffffff0
map==boot = 0    map s/n = 90599059
2 warnings were issued.

and finally - old lilo.conf, who work without problems on slack 12.2:

Code:


# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sdb
compact
default = Linux_working
#Linux
##_wrk_Nwst
##Linux_working

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 90
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# 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
# Windows bootable partition config begins
##other = /dev/sda3
##  label = Windows
##  table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-huge-smp-2.6.27.7-smp
  root = /dev/sdb1
  label = Linux_Orig
  read-only

image = /boot/vmlinuz-elantech
  root = /dev/sdb1
  label = Linux_elantech
  read-only

image = /boot/vmlinuz
  root = /dev/sdb1
  label = Linux
  read-only

image = /boot/vmlinuz.working
  root = /dev/sdb1
  label = Linux_working
  read-only

image = /boot/vmlinuz.wrk.nwst
  root = /dev/sdb1
  label = Linux_wrk_Nwst
  read-only

image = /boot/vmlinuz.last
  root = /dev/sdb1
  label = Linux_last
  read-only

##image = /boot/vmlinuz-2.6.21.4-eeepc
##  root = /dev/sda1
##  label = Xandros
##  read-only


other = /dev/sda1
  label = Xandros
 table = /dev/sda

other = /dev/sdc1
label = USB_sdc
#table = /dev/sdc
# Linux bootable partition config ends


marbangens 12-08-2012 04:23 AM

its not an UEFI system is it?
are you running in bios mode with normal lilo?

markush 12-08-2012 04:27 AM

Well, lilo says
Quote:

adding Xandrosss
in your lilo.conf there is a line
Code:

label = Xandros
are you sure that _this_ lilo.conf is really read by lilo?

Markus

marbangens 12-08-2012 04:41 AM

Quote:

Originally Posted by markush (Post 4845055)
are you sure that _this_ lilo.conf is really read by lilo?

You must run lilo with root to execute the configuration. when installed its done but after
you have edited /etc/lilo.conf you must not forget to run the lilo command.
also when you have an efi system mbr booting can be complicated check out your bios options.

WiseDraco 12-08-2012 04:58 AM

Quote:

Originally Posted by markush (Post 4845055)
Well, lilo says in your lilo.conf there is a line
Code:

label = Xandros
are you sure that _this_ lilo.conf is really read by lilo?

Markus


as i wrote, this fragment is from old lilo.conf, from slack 12.2. whan all works fine. current lilo.conf with xandrosss is higher...

WiseDraco 12-08-2012 05:01 AM

Quote:

Originally Posted by marbangens (Post 4845061)
You must run lilo with root to execute the configuration. when installed its done but after
you have edited /etc/lilo.conf you must not forget to run the lilo command.
also when you have an efi system mbr booting can be complicated check out your bios options.


about root and "run lilo after edit conf" - i know it all for years. i started on slackware on 4.00 about 2001 yer or so on.

dont know about efi and so on, but on slack 12.2 on the same system with the same bios settings / etc all works, now, after i replace slack 12.2 with slack 14.0, and try to use similar lilo.conf - it not work. i hope, anyone know, where is problem...;)

markush 12-08-2012 05:12 AM

Please post the lilo.conf which lilo now uses and the output of the lilo command without the -v option.
Note that errormessages are most important for troubleshooting.

Markus

WiseDraco 12-08-2012 06:01 AM

Quote:

Originally Posted by markush (Post 4845073)
Please post the lilo.conf which lilo now uses and the output of the lilo command without the -v option.
Note that errormessages are most important for troubleshooting.

Markus


look at fifth message in this topic,
Today, 12:19 PM #5
WiseDraco

lilo.conf actual:

Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
compact # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.

and so on and:

lilo output:

Warning: LBA32 addressing assumed
Warning: The boot sector and map file are on different disks.
Added Slack *
Added Slack_gen +
Added Xandrosss
2 warnings were issued.
#

markush 12-08-2012 06:19 AM

Put a line
Code:

lba32
under "compact" in your lilo.conf this fixes the lba32 warning message.

It seems that lilo could not find a failure in your setup. The second warning message about mapfile and bootsector on different disks is clear but no problem.

Now what exactly happens when you try to boot Xandros? Only the errormessages you posted in your first post?

How old is the Xandros installation? when did you upgrade this for the last time? Which bootloader uses Xandros? as you know when you chainload (with the "other" option in lilo, the other system must have a bootloader anywhere, in this case in the superblock of /dev/sda1

As an alternative setup you could also put the xandros kernel into your Slackware bootdirectory and load both, Slackware and Xandros, with lilo.

Markus

WiseDraco 12-08-2012 06:40 AM

Quote:

Originally Posted by markush (Post 4845106)
Put a line
Code:

lba32
under "compact" in your lilo.conf this fixes the lba32 warning message.

It seems that lilo could not find a failure in your setup. The second warning message about mapfile and bootsector on different disks is clear but no problem.

Now what exactly happens when you try to boot Xandros? Only the errormessages you posted in your first post?

How old is the Xandros installation? when did you upgrade this for the last time? Which bootloader uses Xandros? as you know when you chainload (with the "other" option in lilo, the other system must have a bootloader anywhere, in this case in the superblock of /dev/sda1

As an alternative setup you could also put the xandros kernel into your Slackware bootdirectory and load both, Slackware and Xandros, with lilo.

Markus

ues, i can define "lba32" in lilo. but i think, it give nothing in my situation.
When i try to boot Xandros i get error 2 messages, as i wrote in first post.
when i install slack 14, in install process i define sdb for mbr, and system automatically too make a boot record for "another linux" ( for Xandros) like
image = /boot/ vmlinuz-3.x.x-smp
root = /dev/sda1

until i see and fix that, i run "Xandross" choice, and get to boot - but after system boot it looks like different from my standart xandros.
after that i change that in lilo.conf to other= and so on, and get the same problem with error 2: , when i choose xandrosss. in the same time i have a old mbr on /dev/sda/.
i change "first boot device" in BIOS to sda ( 8 Gb), see an old lilo ( from slack 12.2) , choice "Xandros", and all be very ok. switch again to first boot from sdb - on xandros get again error 2 problem. then i think - maybe problem is for that new lilo is on different disk, than xandros, and install new lilo to /dev/sda, but nothing change - xandros not run....
also i have saved mbr from /dev/sda, so i theoretically can restored old mbr on sda, but i want to get work my new lilo with Xandros via other= , who works for many years on LiLo, but now looks like an broken...?

oh yes - Xandros is as old, as eeepc 1000H is old - approx 3 - 4 years, it is default factory install. no major upgrades, no any upgrades for at least year or two.
do not know, what loader he uses, looks like xandros based on debian and use GRUB ?

PS yes, few seconds ago check this - restore my saved mbr on sda - and after that, again, Xandros start without any problem. now i have "old" and "new" mbr in file. this can help to determine and resolve problem with new lilo?

WiseDraco 12-08-2012 08:36 AM

2 Attachment(s)
there is both mbr's - get with
dd if=/dev/sda of=/root/sda_mbr_backup.img bs=512 count=1

in attach - sda_mbr_slack14 is new, mbr make with slack 14, and another - slack122 - is old mbr, make from slack 12.2, with working Xandros booting...


All times are GMT -5. The time now is 10:19 AM.