asv@gaboon.UUCP (Stan Voket) (08/27/89)
Perhaps someone could shed some light on configurating Interactive
386/ix with a WD1007A-WA2 ESDI controller and a CDC/Imprimis 442 Meg
drive.
The problem:
Installing 386/ix on Disks/Controllers with more than 1024 Cylinders.
I know I can utilized all 1412 cylinders, it says so in the manual. I
"RTFM" but still have a case of "brain lock" here.
I tried two of the "logical" drive configurations on the WD
controller. that seem to make the drive "look" like it has 1023
cylinders.
I tried several partitioning schemes as is suggested by the manual but
it was getting very late. After several lengthly (hours!) attempts I finally
went with the default: Partition 1, unix, 100%, just to get things up and
runing. This used less than half of the drive. I'd sure like to do
this right the next time!
Has anyone used this controller/disk combination? (or other greater
than 1024 cylinder disk) If so I'm interesed in how you configured
things to utilize the entire hard disk for unix. Any help,
criticisms, and/or war stories will be greatly appreciated!
This topic may be of general interest. Please e-mail any responses
and I'll post a summary to the net.
Thanks for taking the time to reply.
--
+----------------------------------------------------------------------+
| - Stan Voket, asv@gaboon - OR - ...uunet!hsi!stpstn!gaboon!asv |
| Land Line: (203) 746-4489 TELEX 4996516 - |
+----------------------------------------------------------------------+joe@junkyard.UUCP (Joseph Sarkes) (08/31/89)
In article <3306@gaboon.UUCP>, asv@gaboon.UUCP (Stan Voket) writes: > The problem: > > Installing 386/ix on Disks/Controllers with more than 1024 Cylinders. > > I tried two of the "logical" drive configurations on the WD > controller. that seem to make the drive "look" like it has 1023 > cylinders. > > Has anyone used this controller/disk combination? (or other greater > than 1024 cylinder disk) If so I'm interesed in how you configured > things to utilize the entire hard disk for unix. Any help, > criticisms, and/or war stories will be greatly appreciated! > Basically what is happening is that the mapping done by the controller is read by the install software. This data is saved and used while partitioning the disk. You <can> edit the /etc/partitions file and get the whole disk accessible by rerunning mkpart and remaking the file systems manually. The better way is to circumvent the mapping done by the controller completely by installing a jumper at W14 on the WD1007A-WA2 (Sector translation enabled if jumper removed). This will allow the full disk to be seen when the install program reads the size of the disk, and you <should> be all set. This is based on previous grief taking many hours and reinstalls to check results. Best of luck, and if everything works fine for you using this, post it as your running different software than I. Joseph Sarkes (junkyard!joe)