SEO

I'm building a new system to run my OpenServer 5.0.6. I have the following
configuration

Intel Server Board SE7520AF2 motherboard with LSI onboard SCSI Raid
controller
Single Intel Xeon processor
Two Seagate 15000rpm ST318453LW 18gb disks as the Unix install drives.
Hardware mirrored.
Two Seagate 15000rpm ST373453LW 73gb disks as a mountable user drives.
Hardware mirrored.
I have installed the Intel RAID Activation key and added 512 mb memory for
the SCSI Raid controller.

My problem is that when I run mkdev hd to define the second hard disk for
the 73 gig drives, they only show up as 4.4 gig drives. They seem to mount
and run fine at the 4.4 gig size.

My questions:

Is there something special that I must do to get the full capacity of the
drives?
Am I exceeding some arbitrary drive size limit in OpenServer 5.0.6?
Any suggestions?

I have two of these servers to build and need to get this one configured and
running before I order more hardware tha may not work. The second server
will be a 5.0.5 operating system.

Thanks in advance for any assistance

Alan
alan@lasere.com

Alan Maul wrote:

> I'm building a new system to run my OpenServer 5.0.6. I have the following
> configuration
>
> Intel Server Board SE7520AF2 motherboard with LSI onboard SCSI Raid
> controller
> Single Intel Xeon processor
> Two Seagate 15000rpm ST318453LW 18gb disks as the Unix install drives.
> Hardware mirrored.
> Two Seagate 15000rpm ST373453LW 73gb disks as a mountable user drives.
> Hardware mirrored.
> I have installed the Intel RAID Activation key and added 512 mb memory for
> the SCSI Raid controller.
>
> My problem is that when I run mkdev hd to define the second hard disk for
> the 73 gig drives, they only show up as 4.4 gig drives. They seem to mount
> and run fine at the 4.4 gig size.
>
> My questions:
>
> Is there something special that I must do to get the full capacity of the
> drives?
> Am I exceeding some arbitrary drive size limit in OpenServer 5.0.6?
> Any suggestions?
>
> I have two of these servers to build and need to get this one configured and
> running before I order more hardware tha may not work. The second server
> will be a 5.0.5 operating system.

The problem you're having is a bug in the "lsil" HBA driver, versions
prior to 1.03.28. You can get 1.03.28 from either:

ftp://ftp.sco.com/pub/openserver5/50.../lsil_1.03.28/
http://www.lsilogic.com/downloads/do...ad_type=driver

The bug causes it to present drives larger than 64GB as [size mod 64GB].

Installing the newer driver onto a system already running with the old
driver will cause previously the truncated drives to appear with a new
geometry. You will lose the filesystems on the drives. So your best
bet is to start over, using the new driver as your BTLD during initial
install.

>Bela<

"Bela Lubkin" <belal@sco.com> wrote in message
news:20041223230253.GI13175@sco.com...
> Alan Maul wrote:
>
>> I'm building a new system to run my OpenServer 5.0.6. I have the
>> following
>> configuration
>>
>> Intel Server Board SE7520AF2 motherboard with LSI onboard SCSI Raid
>> controller
>> Single Intel Xeon processor
>> Two Seagate 15000rpm ST318453LW 18gb disks as the Unix install drives.
>> Hardware mirrored.
>> Two Seagate 15000rpm ST373453LW 73gb disks as a mountable user drives.
>> Hardware mirrored.
>> I have installed the Intel RAID Activation key and added 512 mb memory
>> for
>> the SCSI Raid controller.
>>
>> My problem is that when I run mkdev hd to define the second hard disk for
>> the 73 gig drives, they only show up as 4.4 gig drives. They seem to
>> mount
>> and run fine at the 4.4 gig size.
>>
>> My questions:
>>
>> Is there something special that I must do to get the full capacity of the
>> drives?
>> Am I exceeding some arbitrary drive size limit in OpenServer 5.0.6?
>> Any suggestions?
>>
>> I have two of these servers to build and need to get this one configured
>> and
>> running before I order more hardware tha may not work. The second server
>> will be a 5.0.5 operating system.
>
> The problem you're having is a bug in the "lsil" HBA driver, versions
> prior to 1.03.28. You can get 1.03.28 from either:
>
> ftp://ftp.sco.com/pub/openserver5/50.../lsil_1.03.28/
>
> http://www.lsilogic.com/downloads/do...ad_type=driver
>
> The bug causes it to present drives larger than 64GB as [size mod 64GB].
>
> Installing the newer driver onto a system already running with the old
> driver will cause previously the truncated drives to appear with a new
> geometry. You will lose the filesystems on the drives. So your best
> bet is to start over, using the new driver as your BTLD during initial
> install.
>
>>Bela<

I initially used the lsil 1.03.28 driver in this system. The drive worked
fine.

After installing the Intel Raid activation key, the lsil driver would no
longer work. I then loaded the amird driver that I got from the Intel site
and I could then see the drives. The 17 GB drive works fine, but the 73GB
shows up as 4.4GB. That much of the drive seems to work fine also.

Just for the record I have several intel shg2/xeon boards with lsi and
adaptec raid cards and never heard of any such thing as a intel raid
activation key.

These are not that exact model though.

This is the value provided by system builders that will preinstall SCO
and warantee the complete system.

It's not that there is anything all that hard about installing osr5,
it's that they weed out problem hardware and only present you with
tested hardware in tested combinations.

I have used Seneca Data for the last few years and have no complaints
at all but I'm sure there are still at least a few others out there
that do a good job.

On 27 Dec 2004 21:32:28 -0800, brian@aljex.com wrote:

>Just for the record I have several intel shg2/xeon boards with lsi and
>adaptec raid cards and never heard of any such thing as a intel raid
>activation key.

Dell uses them on the Perc 3 line.

Alan Maul wrote:

> I initially used the lsil 1.03.28 driver in this system. The drive worked
> fine.
>
> After installing the Intel Raid activation key, the lsil driver would no
> longer work. I then loaded the amird driver that I got from the Intel site
> and I could then see the drives. The 17 GB drive works fine, but the 73GB
> shows up as 4.4GB. That much of the drive seems to work fine also.

The current models of AMI RAID hardware use the same underlying chips as
driven by the "lsil" driver, so it's not completely surprising that both
drivers could run the same board. I believe the chips are configured
differently, but clearly a board could provide both interfaces in a
switchable manner.

The bug that caused "lsil" to top out at 64GB is something that's can
easily happen in any OSR5 HBA driver. It's the HBA driver that decides
the drive's notional "geometry". Many drivers default to a geometry of
64 heads, 32 sectors/track -- 1MB per cylinder. OSR5 supports a maximum
of 65535 cylinders, so this geometry leads to a maximum drive size of
64GB.

Other HBA drivers take various approaches. A common one is:

if (the real size of this drive would fit)
geometry = 64 heads, 32 sectors/track
else
geometry = 255 heads, 63 sectors/track

The latter geometry limits drives to 539043724800 bytes (539GB or
502GiB). I believe 127 sectors/track also works, and 255 might work on
OSR507. But HBA drivers would be best advised to use (255,63) for
drives that fit, switching to (255,127) and then (255,255) only as
necessary.

So. You should check that you have the newest "amird" driver available.
If you do, and it still has this problem, talk to LSI about it.

>Bela<