Problem with ST3160023A

[Tigrisshark]

I tried installing two ST3160023A Drives in my PC, but for some strange reason they can't be split into partitions: Whenever I try to I get an error on the very last partition (regardless of the size) and the formating of the drive is impossible (neither Win2k's program, nor PartitionMagic nor DiscManager).
With PM I get the error 514, but the so-called fix for the problem (running scandisk over it) won't work because the drive is RAW and scandisk cannot work with that.
Afterwards when I try to enter PM I get the message that the partitiontable is invalid and PM quits.
When I boot up again the Table seems alright again (at least for PM) because I can enter it and see all partitions being good exept the last one, which is still unformated.

I tried using it both as standalone disks or over RAID0, but to no use.

 

[wolluf]

1. Are drives being detected as correct size in bios?
2. Can you ceate one partition on them to take up whole drive?
3. If yes for 2, have you only been using PM to partition?
4. Are they both additional drives to existing system with operating system in place on another drive?

 

[Tigrisshark]

1. Yes, both detected in the HP-Bios AND in Windows in the right size- either 2x160GB or while in RAID0 as 320 GB
2.If I do so the same problem arises- same does apply when destroying the RAID array and tring to format them as default IDE drives with one partition
3.I tried PM, Diskmanager (the version for the Seagate-Website) and the diskmanager native to Win2k
4. Yes, they represent the 3rd/4th drive while the 1st/2nd make up another RAID0-Array with 5 partitions.
C: Windows
E: Programs
F: Games
G: Media
H: Data

 

[wolluf]

Are the RAID controllers both on the motherboard or is one on a separate additional card? If you disconnect the 1st/2nd drive (and/or connect the 3rd/4th where 1st/2nd normally are), can you then partition the drive(s) - eg, by starting win2k install from CD?

 

[Tigrisshark]

It's an Epox 4BDA2+ Motherboard, that has an HP372-Chipset on it, so both are connected to the same Controler- I tried switching them, but to no effect.
I didn't try the Win2k Install-CD because I almost killed my first Array when trying to install the new drives (had to Hex the bootsector to get it working again).
I once got the drives partitioned on another PC, but since I wanted to use the drives as a second array I needed to delete those partitions again (and my second PC doesn't have a RAID-Controller).

 

[wolluf]

So have you tried them on their own in machine? - with attempt to format using 2k install CD (surely you've nothing to lose - other drives not present & new ones not working anyway.

Also - you had to 'Hex the bootsector to get it working again' - you mean for these new drives? Do you mean the master boot record? And did you create a new one (eg, run fdisk /mbr from 98 boot floppy or fixmbr from 2k's recovery console)

 

[Tigrisshark]

NO, I had to restore the RAID-Entry in my old drives with a Hex-Editor, they somehow have been damaged when I installed the two disks.

I'll see if the Win2k CD will do the job.

 

[donbator]

I am having the same problem with my ST3160023AS
I have and ABIT AT7-MAX2 And I have the two drives Raid 0 on the SATA part of the Highpoint 374 RAID Controller. I could use the win2k to partition and format everything but the last segment. Then win2k just crashed each time I tried to create the last partition. I tried PMPro and that didn't work, neither did the Seagate Disk Manager. I basically can't format my last 35GB of my RAID 0 HDs. Any help would be appreciated.

 

[Tigrisshark]

Do you have the same problem when writing on the partitions? I always get a error that it the data can't be written and that it basically will loose the data that should be written.

(BTW: Wrote a mail to Highpoint about this, haven't got a anwser yet- but will post it here if anything comes up)

 

[donbator]

I didn't have a problem writing to the different partitions which I could create. I was basically up all night working on it and finally got it up and running. This is what I had to do.
First I deleted the RAID array and then recreated it, as if starting from scratch. Then I used the Seagate Disk Manager to partition and format the RAID array before installing the OS. I made a 10GB, 50GB and two 130GB partitions and ntfs formatted all of them. The option I picked in the DM was win2k with SP3, but I still made sure my partitions were less than 137GB just in case. When I installed win2k I did not use the fdisk or format which came up but just installed on the created partition. I am now able to access and write to each partition. I think there may be several issues and conflicts with the combination of the highpoint controller with SATA RAID and the way win2k wants to controll everything, and some conflicts with PM and other software. I think the issue ultimately lies with win2k since it was the one giving the errors and not allowing PM and DM do do what they needed. You may have already tried this but maybe if you set up all the partitions before installing the OS, you may avoid this problem.

 

[Tigrisshark]

Yeah- I partitioned my disks on another PC now and they seem to run (have just plugged em in).
Anyway- there is another thing I ultimately discovered.
Being a rather old PC-Self-Builder, I jumpered my disks Master/Slave, but to my surprise I now discovered that you have to jumper the disks to Cable Select when using a ATA100/133 Cable... I didn't even see that notice until my father checked the disk-labels (it's hidden there somewhere, it's small but it actually is there- believe me ). Anyway, with this fixed I'll try again to partition them through the RAID, I'll post my results here..