SATA Drive problem

[Gray_Wolf]

Hi All,
I'm not sure if this is the right/best NG for this but...

I replaced one of my older two Maxtor SATA 120GB with a new Seagate
320GB SATA drive on my HPT374 ATA RAID Controller. The DOS format and
partition went fine and the drive seems to work okay in the DOS test
mode.

When I boot into Win XP the sounding device on the controller card
beeps continuously. Windows recognizes the drive and it's lettered
partitions. I look at the partition's "Properties" and under
"File System:" it says "Raw".

In the Event Viewer I get an error 51 message: "An error was detected
on device \Device\Harddisk3\D during a paging operation."

After messing with it for a bit with no luck I put the old drive back
in and it still worked fine. I have the 48bit addressing working and
my 250GB IDE drive works fine so no problem there.
I think the drive is okay as I can boot off the Seagate
format/partition CD and all the tests come out okay.

 

[DL]

Perhaps your older sata drive and motherboard is sata1 and your new drive is
sata2
Sometimes a sata2 hd has a jumper to force sata1 Check on seagate site

 

[Gray_Wolf]

Perhaps your older sata drive and motherboard is sata1 and your new drive is
sata2
Sometimes a sata2 hd has a jumper to force sata1 sata1 and your new drive is
sata2Check on seagate site

Thanks for the reply.
The new drive is a SATA 3.0 Gbps and there's a jumper to set it to
SATA 1.5 Gbps but it doesn't make any difference. I'm thinking maybe
the later model drive doesn't want to work with the old controller but
it seems to work in the DOS self test mode.
I'm hoping someone has run into the same problem.

 

[DL]

Have you tried updating your Highpoint drivers and bios, if available, or
contacting HighPoint tech for a solution
I think you will find that its a Highpoint driver/bios problem with your
newer drives

 

[Ghostrider]

Hi All,
I'm not sure if this is the right/best NG for this but...

I replaced one of my older two Maxtor SATA 120GB with a new Seagate
320GB SATA drive on my HPT374 ATA RAID Controller. The DOS format and
partition went fine and the drive seems to work okay in the DOS test
mode.

When I boot into Win XP the sounding device on the controller card
beeps continuously. Windows recognizes the drive and it's lettered
partitions. I look at the partition's "Properties" and under
"File System:" it says "Raw".

In the Event Viewer I get an error 51 message: "An error was detected
on device \Device\Harddisk3\D during a paging operation."

After messing with it for a bit with no luck I put the old drive back
in and it still worked fine. I have the 48bit addressing working and
my 250GB IDE drive works fine so no problem there.
I think the drive is okay as I can boot off the Seagate
format/partition CD and all the tests come out okay.

It has been a long time since working with DOS. But DOS partitioning
and formatting on a 320 GB hard drive? There are limitations on the
partition size for DOS, perhaps 2.047 GB for FAT16 partitions.

Why not simply install the 320 GB drive and have Windows XP Disk Mgt.
take care of the partitioning and formatting?

 

[Gray_Wolf]

It has been a long time since working with DOS. But DOS partitioning
and formatting on a 320 GB hard drive? There are limitations on the
partition size for DOS, perhaps 2.047 GB for FAT16 partitions.

Why not simply install the 320 GB drive and have Windows XP Disk Mgt.
take care of the partitioning and formatting?

Doing it in windows was the first thing I tried. No Luck
They use the setup CD to boot into a DOS environment on a RAM drive
that's independent from the operating system to format and partition
or in case this a new setup with no OS installed
You can format in FAT 32 or NTFS. The drive works in the setup
environment according to the test programs you can run from there.
I'm thinking that there's a difference in the drivers they use in the
setup mode and the ones used when Win XP boots.

 

[Gray_Wolf]

Have you tried updating your Highpoint drivers and bios, if available, or
contacting HighPoint tech for a solution
I think you will find that its a Highpoint driver/bios problem with your
newer drives

I'm running the later drivers according to the info on the Highpoint
website. I've got a new mother board coming for a new system I'm
building that has onboard SATA support so I may just wait and see
what happens then.

 

[Guest]

So you replaced "a" drive on the RAID controller,does this mean you run
RAID,or simply run a SATA hd on it.The DOS format and partition went fine...
With what software did you try this task....Depending on what other lame
symptoms you might have,basically, 2 320gb SATA seagate hds in RAID on
a ICH5 intel or later controller,get recognized as 320gb (raw state from
seagate)
when useing the F6 option,once thru,xp formats & installs w/o a hitch..An
ICH5
RAID controller is intels 1st,they used silicon image before that.Pretty
simple
steps,but still wonder how you get "DOS format & partition went well".....

 

[Gray_Wolf]

So you replaced "a" drive on the RAID controller,does this mean you run
RAID,or simply run a SATA hd on it.

Just two SATA hd. No Raid
FWIW, I have two IDE hd on my primary & secondary IDE channels

The DOS format and partition went fine...
With what software did you try this task...

Seagate's "Disk Utility". It's on a bootable CDROM
that allows you to format and partition a new hard
when you have no working OS. DOS format was a poor choice of words
The Disk Utilities operate with a simple interface that allows you to
partition, format with choice of fat32, NTFS or some Linux format
and then you have three hd test utilities you can use to check
the hd with. What I'm trying to say is at this point in this
environment all the tests say the hd is okay. When I boot into
either Win2K or Winxp I can see the hd and it's partitions
and that's about it. Win's disk utility and Partition Magic won't
even start up. I don't recall the error message.
I didn't use the F6 option because It would have only loaded the
drivers that had already been installed. The system has no trouble
seeing the drive. It even shows up on the controller's BIOS start
up page. I can replace the new drive with the old one and everything
is back to normal

.Depending on what other lame
symptoms you might have,basically, 2 320gb SATA seagate hds in RAID on
a ICH5 intel or later controller,get recognized as 320gb (raw state from
seagate)
when useing the F6 option,once thru,xp formats & installs w/o a hitch..An
ICH5
RAID controller is intels 1st,they used silicon image before that.Pretty
simple
steps,but still wonder how you get "DOS format & partition went well".....

Seagate's "Disk Utility" CD

 

[DL]

I still think you should contact Highpoint Tech
I beleive this card is quite old and as such may have a problem with your
new hd

I found some other posts on probs with older Hightpoint cards in which Tech
suggested they installed later drivers available for a specific currently
supported card

 

[Gray_Wolf]

I still think you should contact Highpoint Tech
I beleive this card is quite old and as such may have a problem with your
new hd

I found some other posts on probs with older Hightpoint cards in which Tech
suggested they installed later drivers available for a specific currently
supported card

Thanks!! I'll see what I can get out of Highpoint Tech.
I shouldn't worry too much, I guess, I have a new MB
coming for a new computer. The MB has 4 onboard sata
ports that should work with the Seagate

 

[Dheeraj Abraham]

I have one HP pavilion DV 2550 laptop with vista,I want to install windows XP in this laptop.But when i tried to install the windows xp i am getting error message like setup didi not fid any hard disk drive installed in your computeR.I had checked HP site also i didnt get solution for this .As per the HP site they are ask me to disable SATA from bios system configuration(SATA native mode disable).I could not find this option in BIOS (Phoenix BIOS)

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com