For a solution to this problem please see:
http://h200003.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=es&taskId=110&prodSeriesId=254931&prodTypeId=15351&objectID=PSD_EU041208_CW01
ie.:
Description
A ProLiant server running SCO OpenServer 5 will display a drive size
that is significantly smaller than expected under all of the
following conditions:
The server is configured with an array logical drive.
The capacity of the logical drive is greater than 255 GB.
The Array Configuration Utility (ACU) Version 7.10 default
parameters are used to configure the array.
If the logical volume is configured using Option ROM Configuration
for Arrays (ORCA) Utility, the drive size is displayed as expected
under SCO OpenServer 5.
The difference in drive parameters between ORCA and ACU is that ORCA
sets the logical number of sectors / track at 63, whereas ACU sets
it as 32. If the MAX BOOT parameter in ACU is enabled, the number
logical number of sectors/track is set to 63; therefore, SCO
OpenServer 5 will correctly identify the drive capacity
Resolution
For SCO OpenServer 5 to recognize the correct drive size, perform
either of the following:
Use ORCA to configure the drive array. To invoke ORCA press F8 when
the message "Press F8 to run the Option ROM Configuration for Arrays
Utility" is displayed.
OR
Enable the MAX BOOT parameter when creating a volume greater than
255 GB under ACU when using SCO OpenServer 5.
NOTE:
This issue has also been worked-around by using the "biosgeom" boot
string in the format: biosgeom=(x,x,x) after "defbootstr" at boot
time and in /etc/default/boot
OpenServer 5.0.7 does have a limitation of 500Gb disk size with SCSI.
Use the latest "wd" version on SATA disks which overcomes this
restriction.
|