On Wed, Oct 10, 2001 at 12:31:04PM +1300, Demian Dixon wrote:
> Hello all!
> 
> I have an interesting setup on my PC and I'm having some problems with LILO, 
> wondered if anyone had any bright ideas.   I couldn't find a decent LILO mailing 
> list so thought I would try here.
> 
> Conmputer setup is as follows:
> Three hard-drives in machine.  Two identical 20GB IDE drives and a UW SCSI 4GB 
> drive.
> The two 20GB IDE drives are connected to a HighPoint370a PCI controller card 
> (which provides two IDE channels) (software IDE Raid0)   They are on seperate 
> channels.   The onboard IDE interfaces on the motherboard have a DVD-ROM on the 
> primary as master and the secondary is disabled. The highpoint card makes the 
> two 20GB drives appear as one virtual 40GB drive.
> The 4GB Scsi drive (with Solaris on it) is attached to an Adaptec 2940UW scsi 
> card.
> 
> I have Redhat and Windoze on the IDE Raid0 and I am using LILO to boot between 
> them, no problem.   The drivers I am currently using for the Highpoint emulate a  
> SCSI device so redhat sits on SDA1 etc and Windoze is on SDA5....
> 
> I recently installed Solaris8 for Intel on the 4GB SCSI drive, to do this I had 
> to remove the Highpoint RAID card for the install as a reboot doesn't give me 
> access to the scsi drive to boot from.  If the Highpoint card isn't isntalled 
> then I can boot into Solaris no problem, it has a boot loader in the MBR on the 
> SCSI drive.
> 
> >From Redhat I can see the SCSI drive wth Solaris as SDC (I have a Jaz drive 
> which is SDB)
> 
> I added the following to my /etc/lilo.conf file
> other = /dev/sdc
> label = Solaris

  loader=/boot/chain.b
  map-drive=0x80 to=0x82
  map-drive=0x81 to=0x80
  map-drive=0x82 to=0x81
  unsafe

Add those lines to your Solaris section.  I guarantee it'l work.

The chain.b loader line is needed if the "other" partition or drive
starts with a boot loader rather than an os file.  A win9x partition
starts with an os file, and Solaris definitly has to put a boot loader
in the MBR of its disk.

Normally only the first two drives can be bootable (0x80 and 0x81)
but 0x82 is the third this is why it warns that you may be unable
to boot.

To fix that, add the map-drives lines above - they tell lilo to make
the first (raid) drive third, and the third (4gb scsi) drive second,
and the second (jaz) drive first.  Why?  Because when you installed
Solaris, the jaz drive was first and the 4gb scsi drive was second.
You are just putting things where Solaris expects them.
Hopefully putting the raid drive third will not bother Solaris.

Many peope use map-drive to fool windows into thinking its on the first
drive when its not.  If it fools windows, it may be able to fool
solaris.

What's the 'unsafe' line for?  It tells lilo "Just DO IT!" even
if it thinks the solaris boot block in /dev/sdc is not valid.
Try it without unsafe, and if it complains, try it with.

If this doesn't work, it will be close, and you can try adjustments
to make it fit.

> 
> and reran lilo.  I get a warning message about: warning, drive 0x82 may not be 
> accessible from BIOS.
> 
> I also tried other = /dev/sdc1 and /dev/sdc2
> 
> All i ever get is the Lilo prompt of:
> L?
> 
> The PC has a BIOS which is set to boot from SCSI.
> The HighPoint card has a BIOS which is set to boot the IDE Raid drive (you 
> cannot disable this)
> 
> The adaptec 2940UW SCSI card that I have has the BIOS enabled and is set to boot 
> from SCSI ID 6 (the hard-drive with Solaris in it)  The scsi card has a cdr on 
> it as well and if I have a bootable cd-rom in there then I can boot from it.  
> The Solaris partition is set to active.
> 
> No matter what I do I can't boot from that SCSI drive.  If the Highpoint card is 
> installed then I always boot from the hard-drive array attached to it unless I 
> set the BIOS on the motherboard to boot from floppy or I have a bootable CDROM 
> in the CDR on the SCSI bus
> 
> Will the BIOS=???? option for lilo.conf make a difference if I remap the SCSI 
> drive to be Bios=0x80?     Or can I copy the MBR from the SCSI drive to a file 
> and start booting from this or something similarly tricky?
> 
> Any ideas gratefully accepted!!!!
> 
> Regards
> 
> Demian Dixon
> Core Technology
> RHCE
> 
> 
> 
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list

-- 
Jan Carlson                                 janc at kubwa dot com



_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to