I don't see anywhere information on setting up the booting of Linux
with the RocketRAID. I tried to write the MBR of the designated BOOT
drive and even though lilo said that it had done it, I get a never
ending flow of 01's on the screen instead of a lilo boot screen.
More information:
The operating system is a Linux2.4.20 Kernel compiled from kernel.org
source. The distribution is Debian 3.0 (but like I said, I built my
own kernel) and I am using the standard lilo distribution that came
with it.
The RR100 is in a P4 2.4GHz and supports two 200G WesternDigital Drives
(each on its own Cable as the master.)
Additionally, there are two 80G Maxtors on the MSI motherboards IDE
controllers (one is shared with the CD/RW)
The RR100 is a new addition and intended to replace the two 80G's
The system currently boots to the first 80G and I built a kernel with
the Open Source RR100 RAID driver and it works great. I can see the
two 200G drives as a SINGLE (RAID1) 200G SCSI drive. I was able to
partition, format and copy the full system from the 80G drives to the
200G drive.
Now I am attempting to write a boot record to the RAID array so that I
can remove the two 80G drives.
As part of making the boot process work, I also compiled IDE HPT370
support into the kernel. Without it, the native IDE driver would see
the HPT370 chips and try to enable the drives. This would result in
multiple "interrupt lost" errors. Now with the support compiled in,
the errors are gone and the SCSI device still works great.
My first attempt at making the system boot was to tell lilo to write
the MBR to the /dev/sda device (RR100).
didn't work (and I figure its because the SCSI driver
does not load till after the boot)
My second attempt was to have lilo write the MBR to /dev/hde (RR100
first IDE drive)
didn't work
My final attempt was to have lilo write the MBR to /dev/hdg (RR100
second IDE drive)
didn't work
Before each attempt at booting, I disabled the two 80G drives (they are
in carriers so I just unjack them) and this leaves the RR100 as the
only harddrive in the system (I confirmed this in the bios). I have
also gone into the RR100 bios and set the first drive of the set to be
the Boot Drive.
So now I have had lilo on all occasions tell me that the MBR was
updated successfully only to have the system boot and display a never
ending stream of 01 01 01's to the console.
Any ideas would be greatly appreciated... Here is some output from a
lilo run....
root@willow:/home/keith# dpkg-reconfigure lilo
Running /usr/sbin/liloconfig
LILO, the LInux LOader, sets up your system to boot Linux directly
from your hard disk, without the need for a boot floppy.
You already have a LILO configuration in the file /etc/lilo.conf
Checking your /etc/lilo.conf for incompatible options...
Install a boot block using your current LILO configuration? [Yes]
==========================================================================
WARNING: Even if lilo runs successfully, see
/usr/share/doc/lilo/INCOMPAT.gz
for changes in the usage of the /etc/lilo.conf file.
If needed: edit /etc/lilo.conf and rerun '/sbin/lilo -v'
Running lilo...
LILO version 22.2, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2001 John Coffman
Released 05-Feb-2002 and compiled at 20:57:26 on Apr 13 2002.
MAX_IMAGES = 27
Reading boot sector from /dev/hde
Warning: /dev/hde is not on the first disk
Merging with /boot/boot-menu.b
Boot image: /vmlinuz -> /boot/vmlinuz-2.4.20-idepci
Added Linux_2.4.20
Boot image: /vmlinuz.raid -> /boot/vmlinuz-2.4.20-raid
Added RAID.2.4.20 *
Boot image: /vmlinuz.old -> /boot/vmlinuz-2.2.20-idepci
Added Linux_2.2.20
/boot/boot.2100 exists - no backup copy made.
Writing boot sector.
And the top of the lilo.conf file that produced it.
# Support LBA for large hard disks.
#
lba32
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81
#disk=/dev/sda
# bios=0x80
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hde
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/sda1
And the IDE and SCSI section of the boot screen (when booting off the
80G drive)
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
ICH4: IDE controller on PCI bus 00 dev f9
PCI: Device 00:1f.1 not available because of resource collisions
ICH4: BIOS setup was incomplete.
ICH4: chipset revision 1
ICH4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:DMA
HPT370A: IDE controller on PCI bus 03 dev 00
PCI: Enabling device 03:00.0 (0005 -> 0007)
HPT370A: chipset revision 4
HPT370A: not 100% native mode: will probe irqs later
HPT370: using 33MHz PCI clock
ide2: BM-DMA at 0xbc00-0xbc07, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xbc08-0xbc0f, BIOS settings: hdg:DMA, hdh:pio
hda: MAXTOR 6L080J4, ATA DISK drive
hdb: MAXTOR 6L080J4, ATA DISK drive
hdd: LITE-ON LTR-40125S, ATAPI CD/DVD-ROM drive
hde: WDC WD2000JB-00EVA0, ATA DISK drive
hdg: WDC WD2000JB-00EVA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xcc00-0xcc07,0xc802 on irq 16
ide3 at 0xc400-0xc407,0xc002 on irq 16
blk: queue c035d4a4, I/O limit 4095Mb (mask 0xffffffff)
hda: 156355584 sectors (80054 MB) w/1819KiB Cache, CHS=9732/255/63,
UDMA(100)
blk: queue c035d5f0, I/O limit 4095Mb (mask 0xffffffff)
hdb: 156355584 sectors (80054 MB) w/1819KiB Cache, CHS=9732/255/63,
UDMA(100)
blk: queue c035db6c, I/O limit 4095Mb (mask 0xffffffff)
hde: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63,
UDMA(33)
blk: queue c035ded0, I/O limit 4095Mb (mask 0xffffffff)
hdg: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63,
UDMA(100)
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
hdb: unknown partition table
hde: hde1 hde2 hde3 hde4 < hde5 hde6 hde7 hde8 >
hdg: hdg1 hdg2 hdg3 hdg4 < hdg5 hdg6 hdg7 hdg8 >
(extra non-disk messages deleted)
Adding Swap: 2097136k swap-space (priority -1)
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: LITE-ON Model: LTR-40125S Rev: ZS0K
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
Device Driver for HPT37x2 ATA RAID Controller
Version 1.31, Compiled Nov 24 2003 08:58:36
Found Controller: HPT370 UDMA/ATA100 RAID Controller
scsi1 : hpt37x2
Vendor: HPT Inc. Model: HPT37x2 RAID 1 Rev: 1.05
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
EXT2-fs warning (device sd(8,1)): ext2_read_super: mounting ext3
filesystem as ext2
EXT2-fs warning (device sd(8,3)): ext2_read_super: mounting ext3
filesystem as ext2
EXT2-fs warning (device sd(8,5)): ext2_read_super: mounting ext3
filesystem as ext2
EXT2-fs warning (device sd(8,6)): ext2_read_super: mounting ext3
filesystem as ext2
EXT2-fs warning (device sd(8,7)): ext2_read_super: mounting ext3
filesystem as ext2
EXT2-fs warning (device sd(8,8)): ext2_read_super: mounting ext3
filesystem as ext2
|