G
Guest
Guest
Archived from groups: alt.solaris.x86,alt.sys.pc-clone.compaq (More info?)
A friend of mine is trying to install Solaris 9 x86 on a Compaq DL380
G1 server. The machine has a dual channel SCSI controller, and an IDE
interface.
If a SCSI disk is on the internal SCSI (raid) controller, the system
will boot from a CD, and creates device files for the disk
(/dev/rdsk/c0t0.. etc), but Solaris's format or fdisk can't see the
hard disk at all. It seems the internal controller is not going to
work with Solaris x86.
He has another SCSI controller, which is badged Compaq, but made by
Adaptec - I believe it is a 39160, which is not in the HCL, but is in
a list of 'reported to work'. Whilst installation does ont complete on
this controller, it goes a lot further than using the internal one.
Using the Adaptec SCSI controller, he can boot the Solaris install (or
#1) CD from the IDE CD drive, set up file systems on the SCSI disk,
and let the installer read the data from the CD. However, when the
installation is finished with CD #1, and reboots, the system fails to
boot from the SCSI disk, so you can't load CD #2.
I'm pretty convinced that Solaris is being installed okay, but he does
not know how to persuade the system to boot from the SCSI disk on the
Adaptec controller which is plugged into a PCI slot, and ignore the
on-board SCSI controller. I think it is trying to boot from the
on-board controller, which fails, as there are no disks on that.
I know in most generic PCs you could go into the BIOS and disable the
on-board SCSI controller. You could then enter the BIOS of the SCSI
controller to boot from a specific SCSI id. But from what I understand
these Compaq machines are a little different.
Any ideas ? I'm pretty convinced if the machine can be persuaded to
ignore its on-board SCSI controller and boot from the Adaptec one in a
PCI slot, the Solaris installation will complete, leaving a working
Solaris system.
David Kirkby
david (DOT) kirkby (AT) onetel (DOT) net
A friend of mine is trying to install Solaris 9 x86 on a Compaq DL380
G1 server. The machine has a dual channel SCSI controller, and an IDE
interface.
If a SCSI disk is on the internal SCSI (raid) controller, the system
will boot from a CD, and creates device files for the disk
(/dev/rdsk/c0t0.. etc), but Solaris's format or fdisk can't see the
hard disk at all. It seems the internal controller is not going to
work with Solaris x86.
He has another SCSI controller, which is badged Compaq, but made by
Adaptec - I believe it is a 39160, which is not in the HCL, but is in
a list of 'reported to work'. Whilst installation does ont complete on
this controller, it goes a lot further than using the internal one.
Using the Adaptec SCSI controller, he can boot the Solaris install (or
#1) CD from the IDE CD drive, set up file systems on the SCSI disk,
and let the installer read the data from the CD. However, when the
installation is finished with CD #1, and reboots, the system fails to
boot from the SCSI disk, so you can't load CD #2.
I'm pretty convinced that Solaris is being installed okay, but he does
not know how to persuade the system to boot from the SCSI disk on the
Adaptec controller which is plugged into a PCI slot, and ignore the
on-board SCSI controller. I think it is trying to boot from the
on-board controller, which fails, as there are no disks on that.
I know in most generic PCs you could go into the BIOS and disable the
on-board SCSI controller. You could then enter the BIOS of the SCSI
controller to boot from a specific SCSI id. But from what I understand
these Compaq machines are a little different.
Any ideas ? I'm pretty convinced if the machine can be persuaded to
ignore its on-board SCSI controller and boot from the Adaptec one in a
PCI slot, the Solaris installation will complete, leaving a working
Solaris system.
David Kirkby
david (DOT) kirkby (AT) onetel (DOT) net