Hi,
my Linux Server has just been hacked today by some stupid who changed my root passwd and did lots of other stupid things.

I want to do a new install of SuSE 7.2 on that computer, minimal system only.

AMD K62-550, 384 MB RAM, DVI K6BV3+ Mainboard
TEKRAM U2W SCSI Controller

I've got 6 HD's in that computer,
0. 60GB IDE (hda)
1. 9GB SCSI (sda)
2. 9GB SCSI (sdb)
3. 4GB SCSI ...
4. 4GB SCSI
5. 4GB SCSI

I tried to install a new minimal system on sdb1
(Whole drive ext2 as /, lilo to mbr on /dev/sdb )
with yast2, but after rebooting, the system didn't boot the new system, probably because i forgot to set scsi controller to boot from disk 2, so I tried to install LILO manually somewhere else.
I always get the same error when i call:
lilo -C lilo.conf

...

Warning: /dev/sdb is not on the first disk
Fatal: Sorry, don't know how to handle device 0x0102

The warning doesn't matter since I can set the SCSI Controller to boot from /dev/sdb, but the last line prevents lilo to write the mbr.

I've not found much info about that problem on the net, so i'm asking you.

here is my lilo.conf:

disk = /dev/hda
bios = 0x80
disk = /dev/sda
bios = 0x81
disk = /dev/sdb
bios = 0x82
disk = /dev/sdc
bios = 0x83
disk = /dev/sde
bios = 0x84
disk = /dev/sdd
bios = 0x85
boot=/dev/sdb
read-only
prompt
linear
timeout = 80

image = /boot/vmlinuz
label = linux
root = /dev/sdb1
table = /dev/sdb
# initrd = /boot/initrd

i tried to change "linear" to "lba32", removed the table, included the initrd... bla bla bla.

lilo -vv -C lilo.conf

gives:

LILO version 21.6, Copyright (C) 1992-1998 Werner Almesberger
Linux Real Mode Interface library Copyright (C) 1998 Josh Vanderhoof
Development beyond version 21 Copyright (C) 1999-2000 John Coffman
Released 04-Oct-2000 and compiled at 21:55:07 on May 15 2001.

Caching device /dev/hda (0x0300)
Caching device /dev/hda1 (0x0301)
Caching device /dev/hda2 (0x0302)
Caching device /dev/hda3 (0x0303)
Caching device /dev/hda4 (0x0304)
Caching device /dev/hda5 (0x0305)
Caching device /dev/hda6 (0x0306)
Caching device /dev/hda7 (0x0307)
Caching device /dev/hda8 (0x0308)
Caching device /dev/hdb (0x0340)
Caching device /dev/hdb1 (0x0341)
Caching device /dev/hdb2 (0x0342)
Caching device /dev/hdb3 (0x0343)
Caching device /dev/hdb4 (0x0344)
Caching device /dev/hdb5 (0x0345)
Caching device /dev/hdb6 (0x0346)
Caching device /dev/hdb7 (0x0347)
Caching device /dev/hdb8 (0x0348)
Caching device /dev/sda (0x0800)
Caching device /dev/sda1 (0x0801)
Caching device /dev/sda2 (0x0802)
Caching device /dev/sda3 (0x0803)
Caching device /dev/sda4 (0x0804)
Caching device /dev/sda5 (0x0805)
Caching device /dev/sda6 (0x0806)
Caching device /dev/sda7 (0x0807)
Caching device /dev/sda8 (0x0808)
Caching device /dev/sdb (0x0810)
Caching device /dev/sdb1 (0x0811)
Caching device /dev/sdb2 (0x0812)
Caching device /dev/sdb3 (0x0813)
Caching device /dev/sdb4 (0x0814)
Caching device /dev/sdb5 (0x0815)
Caching device /dev/sdb6 (0x0816)
Caching device /dev/sdb7 (0x0817)
Caching device /dev/sdb8 (0x0818)
Caching device /dev/loop0 (0x0700)
Caching device /dev/loop1 (0x0701)
Caching device /dev/loop2 (0x0702)
Caching device /dev/loop3 (0x0703)
Caching device /dev/loop4 (0x0704)
Caching device /dev/loop5 (0x0705)
Caching device /dev/loop6 (0x0706)
Caching device /dev/loop7 (0x0707)
Reading boot sector from /dev/sdb
Warning: /dev/sdb is not on the first disk
Merging with /boot/boot.b
Caching device /dev/ram2 (0x0102)
Fatal: Sorry, don't know how to handle device 0x0102

what is this boot.b??? After looking around it seems that it is the 'real' boot loader or something like that, it seems to have this '/dev/ram2' device that lilo cannot hande.

Any Ideas??

/dev/ram2 is a ramdisk. Do you really need it (or use it)? If not, remove it and try LILO again. BTW try 'lilo -vvv'

I don't know where to remove the /dev/ram2.
As you can see it's not in lilo.conf.
Do you think i should 'rm /dev/ram2' ?

By the way i'm doing this with the suse 7.2 rescue system,
after installing the ncrxxxx scsi driver module. I then mounted /dev/sdb1 to /mnt, then
'cd /mnt/etc' and then
'lilo -vv -C lilo.conf'.

lilo -vvv did not give more info.

The rescue system surely is on a ramdisk, but not on /dev/ram2. It seems to be included with boot.b somehow. ??

I've had enough of all that - so I installed Debian 3.0

I had some problem installing lilo - due to my complex setup - but it finally worked. In debian there was no strange ram2 device ;-)

Thanks

So I guess your suse had some ramdisks (I suppose because of scsi..). Nice that it works now.