LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 04-21-2014, 03:06 PM   #1
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,960

Rep: Reputation: 55
lilo 23.2: Fatal: trying to map files from unnamed device 0x001


Hi: I have browsed the web for that message but could not find anything useful for my case. Having got this message I reduced lilo.conf to a minimum:
Code:
$ cat /etc/lilo.conf
lba32
boot=/dev/sda
$
And I still got the same message. The machine has only one hard disk with three primary partitions and one extended partition, the hard disk being parallel ATA (IDE). I first used lilo 22.8 but got, with a complete lilo.conf, "Fatal: Setup length exceeds 31 muximum; kernel setup will overwrite boot loader". Then I saw a post where the author of lilo said he had taken notice of that message and that the poster would have to wait until lilo 23.2 was out, which prompted me to run 23.2, only to get the message in this post title. What can possibly be the cause?
 
Old 04-21-2014, 09:15 PM   #2
widget
Senior Member
 
Registered: Oct 2008
Location: S.E. Montana
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628

Rep: Reputation: 496Reputation: 496Reputation: 496Reputation: 496Reputation: 496
I really know nothing about Lilo. Need to state that right off the bat.

I like bootloaders though and so this interested me enough to do a casual search. Have you looked at the wikipedia article. Looks like it was well written and has what looks like a good example of a /etc/lilo.conf file.

Also has quite a bit more information on usage and error codes.

More importantly some good looking external links.
http://en.wikipedia.org/wiki/LILO_%28boot_loader%29
 
Old 04-21-2014, 09:27 PM   #3
astrogeek
Moderator
 
Registered: Oct 2008
Distribution: Slackware [64]-X.{0|1|2|37|-current} ::12<=X<=14, FreeBSD_10{.0|.1|.2}
Posts: 4,924
Blog Entries: 8

Rep: Reputation: 2797Reputation: 2797Reputation: 2797Reputation: 2797Reputation: 2797Reputation: 2797Reputation: 2797Reputation: 2797Reputation: 2797Reputation: 2797Reputation: 2797
What fs are you using? I found a reference to that message when used with btrfs, ext4 fixed it (also seemed to be related to the particular motherboard).

**UPDATE ** - I wrote the above assuming that it had been working and now failed for some reason, although now I see that is not actually stated in your original post.

So for my own clarity could you be explicit about the partitions and post a more complete lilo.conf, and let us know if it is a new install or one that previously worked.

That message is normally associated with the "root" specification line within a stanza (not the "boot" device line).

Last edited by astrogeek; 04-22-2014 at 04:22 AM.
 
Old 04-21-2014, 09:31 PM   #4
Emerson
LQ Guru
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~arch
Posts: 6,316

Rep: Reputation: Disabled
You must specify the kernel image to boot and the root device (passed to kernel).
 
Old 04-22-2014, 09:06 AM   #5
cynwulf
Senior Member
 
Registered: Apr 2005
Posts: 2,215
Blog Entries: 5

Rep: Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307
Yes, the config file is far too minimal...

Have a read: https://wiki.debian.org/LILO
 
Old 04-22-2014, 02:34 PM   #6
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,960

Original Poster
Rep: Reputation: 55
Quote:
Originally Posted by astrogeek View Post
What fs are you using? I found a reference to that message when used with btrfs, ext4 fixed it (also seemed to be related to the particular motherboard).

**UPDATE ** - I wrote the above assuming that it had been working and now failed for some reason, although now I see that is not actually stated in your original post.

So for my own clarity could you be explicit about the partitions and post a more complete lilo.conf, and let us know if it is a new install or one that previously worked.

That message is normally associated with the "root" specification line within a stanza (not the "boot" device line).
I have made many tests under different OSs and different versions of lilo. So the following can be a bit confusing.

Under slack12:
Code:
root@local:~# fdisk -l

Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1        2432    19535008+  83  Linux
/dev/hda2   *        2433        5923    28041457+  83  Linux
/dev/hda3            5924       14468    68637682    5  Extended
/dev/hda4           14469       14593     1004062+   c  W95 FAT32 (LBA)
/dev/hda5            5924        5985      497983+  82  Linux swap
/dev/hda6            5986        8417    19535008+  83  Linux
/dev/hda7            8418       10849    19535008+  83  Linux
/dev/hda8           10850       14468    29069586   83  Linux
root@local:~# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:

lba32
# append=" vt.default_utf8=0"
# append= no ira ide simulation aca?
append="nomodeset"
boot = /dev/hda

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

# 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 = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset

# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
#End LILO global section

# Windows bootable partition config begins
#other = /dev/hda3
#  label = xp
#  boot-as=0x80
# Windows bootable partition config ends

other=/dev/hda4
  label=fdos
  boot-as=0x80

# Linux bootable partition config begins
#image = /boot/vmlinuz
#  root = /dev/sdb1
#  label = lin14
#  read-only
# Linux bootable partition config ends

############# PROBLEMATIC STANZA
#image = /mnt/deb7/vmlinuz
#  root = /dev/hda6
#  initrd=/mnt/deb7/initrd.img
#  label = deb7
#  read-only

image = /mnt/deb4/vmlinuz
  root = /dev/hda2
  initrd=/mnt/deb4/initrd.img
  label = deb4
  read-only

image = /boot/vmlinuz
  root = /dev/hda1
  label = slack12
  read-only

root@local:~# lilo -V
LILO version 22.8
root@local:~# lilo -v -v -t
LILO version 22.8 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 01:09:42 on Jun 10 2007.
Running Linux kernel 2.6.21.5-smp on i686

raid_setup returns offset = 00000000  ndisk = 0
 BIOS   VolumeID   Device
Reading boot sector from /dev/hda
pf_hard_disk_scan: ndevs=1
  0300  4DDB4591  /dev/hda
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = 0
device codes (canonical) = 1
Warning: Unable to determine video adapter in use in the present system.
Using MENU secondary loader
Calling map_insert_data
Secondary loader: 18 sectors (0x3600 dataend).
bios_boot = 0x80  bios_map = 0x80  map==boot = 0  map S/N: 4DDB4591
BIOS data check will include auto-suppress check

Boot other: /dev/hda4, on /dev/hda, loader CHAIN
  Swapping BIOS boot drive with 0x80, as needed
Mapped 6 (4+1+1) sectors.
Added fdos *

Boot image: /mnt/deb4/vmlinuz -> boot/vmlinuz-2.6.18-4-686
Setup length is 15 sectors.
Mapped 2464 sectors.
Mapping RAM disk /mnt/deb4/initrd.img -> boot/initrd.img-2.6.18-4-686
RAM disk: 8750 sectors.
Added deb4

Boot image: /boot/vmlinuz -> vmlinuz-huge-smp-2.6.21.5-smp
Setup length is 15 sectors.
Mapped 8630 sectors.
Added slack12

 BIOS   VolumeID   Device
  80    4DDB4591    0300
The boot sector and the map file have *NOT* been altered.
One warning was issued.
root@local:~#
In the lilo.conf listed, a stanza is marked PROBLEMATIC. If I uncomment it, this is what I get:
Code:
root@local:~# lilo -v -v -t     
LILO version 22.8 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 01:09:42 on Jun 10 2007.
Running Linux kernel 2.6.21.5-smp on i686

raid_setup returns offset = 00000000  ndisk = 0
 BIOS   VolumeID   Device
Reading boot sector from /dev/hda
pf_hard_disk_scan: ndevs=1
  0300  4DDB4591  /dev/hda
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = 0
device codes (canonical) = 1
Warning: Unable to determine video adapter in use in the present system.
Using MENU secondary loader
Calling map_insert_data
Secondary loader: 18 sectors (0x3600 dataend).
bios_boot = 0x80  bios_map = 0x80  map==boot = 0  map S/N: 4DDB4591
BIOS data check will include auto-suppress check

Boot other: /dev/hda4, on /dev/hda, loader CHAIN
  Swapping BIOS boot drive with 0x80, as needed
Mapped 6 (4+1+1) sectors.
Added fdos *

Boot image: /mnt/deb7/vmlinuz -> boot/vmlinuz-3.2.0-4-686-pae
Setup length is 33 sectors.
Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader
Removed temporary file /boot/map~
root@local:~#
This seems to be a known problem to the developers of lilo. The solution, go on to lilo 23.2. All this happened in the task of writting the MBR (aka boot sector) after having installed Debian 7.4. Debian 7.4 spoke of lilo and grub as in an equal foot. That is I could use one or the other. But in the process of installation, it offered me only grub. I said no. But then I saw there was no lilo in the whole bunch of software that had been downloaded from the net (netinst installation). So I booted with the Slackware 14.0 disk (as if installing for the first time), which has lilo 23.2 and invoked lilo. But lilo was not! So I went, in the DVD, to /slackware/a/ and 'installpkg lilo-.......xz'. Having run it, I got the message in this thread title.
 
Old 04-23-2014, 07:26 PM   #7
Emerson
LQ Guru
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~arch
Posts: 6,316

Rep: Reputation: Disabled
Below is working lilo.conf as an example for booting current and backup kernel.
Code:
$ cat /etc/lilo.conf
disk = /dev/sda
        bios = 0x80
prompt
timeout = 30
default = gentoo

image = /boot/bzImage
        label = gentoo
        read-only
        root = /dev/sda1
        vga = 0x317
image = /boot/bzImage.pre
        label = gentoo.pre
        read-only
        root = /dev/sda1
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Fatal: Trying to map to unnamed device 0x000f (NFS/Raid missing?) gamewolf Slackware 5 08-14-2011 10:15 PM
mkrescue Fatal: device-mapper: only linear boot device supported Molly Slackware 5 01-06-2009 05:35 PM
Lilo wont write to MBR, Fatal error: only linear boot device supported agentc0re Slackware 2 03-16-2008 03:23 PM
"Fatal: empty map section" lilo error kaz2100 Linux - Software 2 12-25-2007 10:42 AM
Lilo: unnamed device 0x0008 radim24 General 1 12-06-2006 10:05 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 02:44 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration