Very Computer

I'm trying to accomplish the task of dual booting both Redhat linux
7.1 and Windows 2000.  The catch is that I already have Windows 2000
installed on two hard drives configured in a RAID-0 configuration
using a HPT370 hardware raid controller (IWILL SIDE-RAID100).  Linux
is installed on a hard-drive on IDE-0.  I tried to dual boot through
the NTLDR using the following steps:

1) created a boot linux boot image and copied it to a floppy
    dd if=/dev/hda6 of=/bootsect.lnx bs=512 count=1
    mount -t msdos /dev/fd0 /mnt
    cp /bootsect.lnx /mnt
    umount /mnt

2) I rebooted to Windows 2000 and copied the bootsect.lnx to the root
directory

3) I modified my boot.ini to append the following line
    c:\bootsect.lnx="Linux"

I rebooted the machine and received a menu where I could boot Windows
2000 and Linux and I thought I was home free.  When I chose the Linux
option, the computer just displayed a blank screen like it couldn't
find the boot image on the ide0 hard drive.  Why is this??  Is there
another way to do this?

Thanks in advance to all replies
John

I also tried to get this to work using LILO, but couldn't get LILO to
recognize the RAID card.  Really would love to be able to switch OSes
at boot!!

You can easily boot NT-whatever from lilo installed to the MBR:

[etc]# cat lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
vga = normal

image = /boot/vmlinuz-2.4.17
  root = /dev/hda5
  label = linux
  read-only

other = /dev/hda1
  label = winxp      <-  This one is NT-5.1
  table = /dev/hda

other = /dev/hda2
  label = freebsd
  table = /dev/hda

other = /dev/hda3
  label = solaris
  table = /dev/hda

image = /vmlinuz
  root = /dev/hda5
  label = old
  read-only
[etc]#

Are any of those OSes installed on a hardware Raid controller?  If it
is can you explain how you got linux (LILO) to recognize the raid
controller?

Thanks John

As to getting Linux to recognize a RAID controller, I have no idea.  I
use Linux on my desktop system and use Solaris on my server.  The other
OS which appear in that lilo.conf file are for educational usage.

I have in the past installed Linux on a system using a Promise Ultra100
TX2 controller where the hard drive was recognized as /dev/hde.  The
BIOS on that system was set to boot from SCSI first.

    /dev/sda (the mirror drive).
    /dev/sdb (the RAID5 array).

Boot with the RedHat installation CD into rescue mode and see what you see
in /proc/scsi, and which /dev/sd? drives are accessible with fdisk.

I'm not at my machine currently, but using your example how do I tell
LILO to boot off of two devices (one raid array)? I've had some
experience using LILO to boot other IDE drives, but I never configured
LILO to boot a RAID array.

Thanks
John

Quote:> Thanks for your reply Nico.

> I'm not at my machine currently, but using your example how do I tell
> LILO to boot off of two devices (one raid array)? I've had some
> experience using LILO to boot other IDE drives, but I never configured
> LILO to boot a RAID array.

> Thanks
> John

How exactly does the device show up for "fdisk" reports or installation
attempts using "fdisk" with the installation CD? Or does it show up? And
what is reported by /proc/pci?

I remember when I was installing Linux that FDISK complained about
corrupted partitions the two drives in the raid.

/proc/pci reports:

 Bus 0, device 11, function 0:
  Unknown mass storage controller: Triones Technologies, Inc. HPT366
(rev 3).
  IRQ 11.
  Master Capable Latency=120.
  I/O at 0xdc00 [0xdc07]
  I/O at 0xd800 [0xd803]
  I/O at 0xd400 [0xd407]
  I/O at 0xdc00 [0xd003]
  I/O at 0xcc00 [0xccff]

also in /var/log/messages:
  localhost kernel: hde : IC35LO20AVER07-0, ATA Disk Drive
  localhost kernel: hdg : IC35LO20AVER07-0, ATA Disk Drive

Thanks for taking the time to help, Nico

Quote:> *IF* the particular hardware RAID shows the hardware-mirrored boot drive as
> /dev/sda, you need to do the following steps, it just looks like a normal
> SCSI device. Use the partitions as found on the disk.

> How exactly does the device show up for "fdisk" reports or installation
> attempts using "fdisk" with the installation CD? Or does it show up? And
> what is reported by /proc/pci?

Quote:> Nico

> I remember when I was installing Linux that FDISK complained about
> corrupted partitions the two drives in the raid.

> /proc/pci reports:

>  Bus 0, device 11, function 0:
>   Unknown mass storage controller: Triones Technologies, Inc. HPT366
> (rev 3).
>   IRQ 11.
>   Master Capable Latency=120.
>   I/O at 0xdc00 [0xdc07]
>   I/O at 0xd800 [0xd803]
>   I/O at 0xd400 [0xd407]
>   I/O at 0xdc00 [0xd003]
>   I/O at 0xcc00 [0xccff]

> also in /var/log/messages:
>   localhost kernel: hde : IC35LO20AVER07-0, ATA Disk Drive
>   localhost kernel: hdg : IC35LO20AVER07-0, ATA Disk Drive

Quote:> Thanks for taking the time to help, Nico

> > *IF* the particular hardware RAID shows the hardware-mirrored boot drive
as
> > /dev/sda, you need to do the following steps, it just looks like a
normal
> > SCSI device. Use the partitions as found on the disk.

> > How exactly does the device show up for "fdisk" reports or installation
> > attempts using "fdisk" with the installation CD? Or does it show up? And
> > what is reported by /proc/pci?