Drive Array Size Limitation - SCO 5.0.5
Stephen C Young
system to recognize all the drive space in my array configuration. I
had the system configured with three (3) 9.1 GB hard drives with a
Compaq 221 Controller Array. I had to blow all the data away
(controller does not allow for expansion) and the re-configure the
array with five (5) 9.1 GB drives after backing all data up to tape
drive. Upon adding the additional two (2) hard drives I am not seeing
the additional drive space. The most the system will recognize is 17.7
GB. Has anyone else run into this problem and found a resolution? Any
help would be appreciated. Need help ASAP.
Thanks,
Stephen
Stuart J. Browne
"Stephen C Young" <stephe...@duron.com> wrote in message
news:4d30cee2.04030...@posting.google.com...
After blowing away the data, did you re-configure the container in the
controller configuration? Otherwise, it'll still be configured in (what
appears to be) a RAID 5 container with 3 disks.
I know for a fact that OSR505 has no issues seeing and using in excess of
200GB 'disks' (raid arrays)..
bkx
Scott McMillan
As Stuart already mentioned, if you did not adjust the 221 controller to
make use of the additional disks, then you'll not access any more than the
original ~18Gb. If you were to share with us the configuration of your
221/5 disks, that would help.
What *exactly* did you do after "adding the additional two (2) hard drives"?
I've seen this happen when one attempts to use eg. Norton Ghost to
"mirror" SCO over to a new disk - The drive mappings/filesystems transfer
with the Ghost image, and the system knows nothing of the additional drive
space.
Specific information on the steps you performed would certainly result in
more appropriate responses.
Scott McMillan
bpc
I am no expert but;
I had a similar problem when trying to use an array of 3 x 36GB physical
drives arranged as a single logical volume in RAID5 . SCO 5.0.5 installed OK
but I could not "see" the full disk capacity. Solution was to use the RAID
controller software to configure 4 logical volumes which are seen by SCO 5.0.5
as 4 separate drives.
Also there is a technical article TA # 114422 "I get error messages
during SCO OpenServer 5.0.5 installation with any Compaq Array Controller that
has a large Boot Logical volume. "
on the SCO support web site relating to the inability of 5.0.5 to deal with a
root volume of > 17Gb.
Brian
Stephen C Young
After I destroyed all data on the disks to reconfigure the array I
added the two additional hard disks to the system and re-configured
array for 5 disks using the Compaq SmartStart disk utilities. In the
SmartStart utility it reads that total drive space is 45.5 GB and
taking away the raid overhead usuable space is 36.4 GB. After
configuring the array I booted to CD-rom and used the ida fd(64)
volume disk to begin the install along with the necessary bootstring
options and went through screen of entering in license info and system
name and etc. However, when I come to divvy it only shows 17.7 GB of
space to be divided up. Even completed entire install to see if hard
drive space number shown was maybe stuck in bios and that system would
see the additional hard drive space after completing install, but that
did not work either. Any other help would be appreciated. Thanks
Stephen C Young
After I destroyed all data on the disks to reconfigure the array I
added the two additional hard disks to the system and re-configured
array for 5 disks using the Compaq SmartStart disk utilities. In the
SmartStart utility it reads that total drive space is 45.5 GB and
taking away the raid overhead usuable space is 36.4 GB. After
configuring the array I booted to CD-rom and used the ida fd(64)
volume disk to begin the install along with the necessary bootstring
options and went through screen of entering in license info and system
name and etc. However, when I come to divvy it only shows 17.7 GB of
space to be divided up. Even completed entire install to see if hard
drive space number shown was maybe stuck in bios and that system would
see the additional hard drive space after completing install, but that
did not work either. Any other help would be appreciated. Thanks
Stephen
Bela Lubkin
> After I destroyed all data on the disks to reconfigure the array I
> added the two additional hard disks to the system and re-configured
> array for 5 disks using the Compaq SmartStart disk utilities. In the
> SmartStart utility it reads that total drive space is 45.5 GB and
> taking away the raid overhead usuable space is 36.4 GB. After
> configuring the array I booted to CD-rom and used the ida fd(64)
> volume disk to begin the install along with the necessary bootstring
> options and went through screen of entering in license info and system
> name and etc. However, when I come to divvy it only shows 17.7 GB of
> space to be divided up. Even completed entire install to see if hard
> drive space number shown was maybe stuck in bios and that system would
> see the additional hard drive space after completing install, but that
> did not work either. Any other help would be appreciated. Thanks
Boot up from that installed system, go to single-user mode, and show us
the output of:
# cat /dev/string/cfg
# dparam /dev/rhd00
# fdisk -p -f /dev/rhd00
# divvy -P -N /dev/rhd00
# divvy -S /dev/rhd00
Hopefully that'll give us a clue...
>Bela<
Stephen C Young
Output of command 'cat /dev/string/cfg':
%kernel - - - rel=3.2v5.0.5 kid=98/07/02
%cpu - - - unit=1 family=6 type=Pentium II (D)
%cpuid - - - unit=1 vend=GenuineIntel tfms=0:6:5:2
%fpu - 13 - unit=1 type=80387-compatible
%pci 0x0CF8-0x0CFF - - am=1 sc=1 buses=3
%PnP - - - nodes=0
%serial 0x03F8-0x03FF 4 - unit=0 type=Standard nports=1
fifo=yes
%serial 0x02F8-0x02FF 3 - unit=1 type=Standard nports=1
fifo=yes
%console - - - unit=vga type=0 12 screens=68k
%adapter 0x3000-0x30FF 10 - type=cha ha=0 id=7 PCI slot=0 geo=B
wid=16 Compaq Fast-SCSI-2 (rev 5.21E)
%adapter 0x3400-0x34FF 11 - type=cha ha=1 id=7 PCI slot=0 geo=B
wid=16 Compaq Fast-SCSI-2 (rev 5.21E)
%floppy 0x03F2-0x03F7 6 2 unit=0 type=135ds18
%adapter 0x01F0-0x01F7 14 - type=IDE ctlr=primary dvr=wd
%ida0 0x4000-0x401F 15 - PCI slot=4 units=1 Compaq IDA/SMART
(rev 5.25a)
%cd-rom - - - type=IDE ctlr=pri cfg=mst
dvr=Srom->wd
%disk - - - type=IDA0 unit=0 cyls=4355 hds=255
secs=32
Output of command 'dparam /dev/rhd00':
4355 255 0 0 0 0 0 32
Output of command 'fdisk -p -f /dev/rhd00':
1 1 1110269 1110269 UNIX Active
Output of command 'divvy -P -N /dev/rhd00':
0 0 15359 boot EAFS
1 15360 209919 swap NON FS
2 209920 17674549 root HTFS
6 17674550 17674559 recover NON FS
7 0 17764303 hd0a WHOLE DISK
Output of command 'divvy -S /dev/rhd00':
Partition size is 17764304 1K blocks
Thanks!
Stephen
Bela Lubkin
> > > After I destroyed all data on the disks to reconfigure the array I
> > > added the two additional hard disks to the system and re-configured
> > > array for 5 disks using the Compaq SmartStart disk utilities. In the
> > > SmartStart utility it reads that total drive space is 45.5 GB and
> > > taking away the raid overhead usuable space is 36.4 GB. After
> > > configuring the array I booted to CD-rom and used the ida fd(64)
> > > volume disk to begin the install along with the necessary bootstring
> > > options and went through screen of entering in license info and system
> > > name and etc. However, when I come to divvy it only shows 17.7 GB of
> > > space to be divided up. Even completed entire install to see if hard
> > > drive space number shown was maybe stuck in bios and that system would
> > > see the additional hard drive space after completing install, but that
> > > did not work either. Any other help would be appreciated. Thanks
> Output of command 'cat /dev/string/cfg':
> %disk - - - type=IDA0 unit=0 cyls=4355 hds=255 secs=32
>
> Output of command 'dparam /dev/rhd00':
> 4355 255 0 0 0 0 0 32
>
> Output of command 'fdisk -p -f /dev/rhd00':
> 1 1 1110269 1110269 UNIX Active
>
> Output of command 'divvy -P -N /dev/rhd00':
> 0 0 15359 boot EAFS
> 1 15360 209919 swap NON FS
> 2 209920 17674549 root HTFS
> 6 17674550 17674559 recover NON FS
> 7 0 17764303 hd0a WHOLE DISK
>
> Output of command 'divvy -S /dev/rhd00':
> Partition size is 17764304 1K blocks
Ok, well this is all self-consistent and shows a 17GB drive size.
There is one possibility that comes to mind. OpenServer can store its
idea of drive geometry into the masterboot sector; if this drive was so
stamped, it's possible the stamp would have survived through all the
reconfiguration. I'm not even sure that the IDA driver pays attention
to that stamp, but it's definitely worth trying this.
So, what you need is a command that will wipe out the masterboot sector
of this drive. Doing so will of course wipe out all data on the disk;
you'll have to reinstall from scratch.
To wipe out the masterboot sector on your root drive:
DANGER!-- dd if=/dev/zero of=/dev/rhd00 count=1 --!DANGER
Then reinstall.
You'll know very early in the reinstall process whether this helped.
Look for the "%disk... IDA0" line. Hopefully the geometry will have
expanded -- you should see something like 4355/255/63 or 9000/255/32.
If you still see 4355/255/32 then there's something wrong with the IDA
configuration, check it carefully in the SmartStart disk utilities.
>Bela<
Stephen C Young
Thanks! The command, dd if=/dev/zero of=/dev/rhd00 count=1 ,worked. It
cleared the master boot record and the system now reads 8711/255/32.
All the help is appreciated.
Stephen
FyRE
Young) wrote:
[Bela's "fix"]
>> dd if=/dev/zero of=/dev/rhd00 count=1
>>
>> Then reinstall.
>
>Thanks! The command, dd if=/dev/zero of=/dev/rhd00 count=1 ,worked. It
>cleared the master boot record and the system now reads 8711/255/32.
>All the help is appreciated.
Hmm, it seems along with accepting handouts from MS to stay alive, SCO
engineers (a species many thought extinct) have taken the MS route for
fixing problems: Backup, reinstall, wash, rinse, repeat... Now, if
you'd been using Linux...
--
FyRE < "War: The way Americans learn geography" >
Bill Vermillion
Go back and re-read the original post.
Stephen was adding two disks to a RAID array, and could not get
the first disk to give the proper parameters. It was a fresh OS
install on an older reconfigured system.
This was not a typical MS fix to which you have alluded.
Bill
--
Bill Vermillion - bv @ wjv . com
Steve Fabac
FyRE, You are a worthless piece of human debris with no reason to
draw another breath. What kind of low-life, scum sucking, piece of
shit will take the effort to alter Bela's reply (as show above)
to omit important information to a hapless newbe that might find only
your post and not see the Bela's warning (inserted below as Bela
replied, to highlight your despicable posting).
Don't bother to reply to this post, you have no defense for your
action and this is not a conversation, just a condemnation of your
your character.
> So, what you need is a command that will wipe out the masterboot sector
> of this drive. Doing so will of course wipe out all data on the disk;
> you'll have to reinstall from scratch.
>
> To wipe out the masterboot sector on your root drive:
>
> DANGER!-- dd if=/dev/zero of=/dev/rhd00 count=1 --!DANGER
>
> Then reinstall.
> --
> FyRE < "War: The way Americans learn geography" >
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
Morex Support
an new one. The add function leaves the original array size alone and
allocates empty space that must be defined.news:20040316214...@sco.com...