#16 Error "No support for bootloader"

[Anonymous]

I use System Imager 2.0.1 on a Debian Woody.
rsync is 2.4.6
lilo 22.1

After that the image is downloaded to the client from
the image server, It tells me the amount of data, and
the speed. Then it starts System Configurator (I
guess), and there's the following error:

Use of uninitialized value in concatenation (.) or
string at /usr/lib/systemconfig/Boot/YaBoot.pm line 91.
No support for bootloader
at /usr/bin/systemconfigurator line 322

And then there is the System Imager failure message.

It seems that everything works fine until system
configurator is launched:
- boot with DHCP OK
- hostname and IP OK
- /a/ contains the image OK
- systemconfig Fail

I didn't manage to understand where it does come from.
My first idea was to look for the config parameter
given to systemconfig but everything seems right
there. I don't understand Perl, so that's hard for me
to debug...

I wish my description could help you doing such a good
work. I'm interested in your project since 6 months,
I've seen it working, but I'm sad it doesn't work for
me :(

Thanks for your help.

[Steven A. DuChene]

Logged In: YES
user_id=2347

I had the exact problem the other day when I had an
DEFAULTBOOT line in the
/var/lib/systemimager/images/<imagename>/etc/systemconfig/systemconfig.conf
file with a typo in it. I had something like the following:

CONFIGBOOT = YES
CONFIGRD = YES

[BOOT]
ROOTDEV = /dev/hda2
BOOTDEV = /dev/hda
LABEL = linux
DEFAULTBOOT = linuxblah <<<<<< this doesn't match any
kernel LABEL line below

[KERNEL0]
PATH = /boot/vmlinuz-2.4.18pre3ac2
LABEL = linuxfoo

[KERNEL1]
PATH = /boot/vmlinuz
LABEL = linux

[Nobody/Anonymous]

Logged In: NO

In fact, I havent got any /var/lib/systemimager/images/<imagename>/etc/systemconfig/systemconfig.conf on my
image server hard-drive :(

Maybe system imager didn't work properly. However,it still seems to be a bug for me as I followed the
instructions.

Have you ever had a such problem ?

[Sean Dague]

Logged In: YES
user_id=21949

What scsi device are you using?

[Brian Elliott Finley]

Logged In: YES
user_id=140

I have the same problem on Debian Woody on ia64 with elilo.
Also with no systemconfig.conf.

[Brian Elliott Finley]

Logged In: YES
user_id=140

With regards to the "What SCSI device?" question, the disk
is /dev/sda and the boot device is /dev/sda1.

[Brian Elliott Finley]

Logged In: YES
user_id=140

As it turns out, I was able to change something in
SystemImager that minimizes the issue with Debian Woody on
ia64. As it turns out, elilo was seeing the mtab file on
the freshly imaged partitions, and considering it's
information. This resolved part of the issue, but
systemconfigurator still complains.

I have modified SystemImager to no longer store the
/etc/mtab file.

[Sean Dague]

Logged In: YES
user_id=21949

Ignore the original bug, as it is not duplicatable. The new
bug is the ia64 issue that Brian is hitting.