Sign in to follow this  
anaxagoras

New Sata Drive, Problem

Recommended Posts

I just added a second sata drive to my desktop system, the first was a 250GB WD drive, I just added a 200 GB seagate a week or two ago.

When I transfer data between the two drive, the seagate gets a dma time out error, and then just stops responding. I tried to seperate the sata cables as much as i can so they hardly even come in proximity of each other, unfortunatly no one around here stocks sata cables of any decent lenghts.

Is this problem likely that i just need sheilded cables? Makes me warry about my future plans to create a massive SATA2 Raid5 array.

I'm running Gentoo linux, btw. My motherboard is the DFI Lanparty B, nfroce2. Running the latest bios.

Share this post


Link to post
Share on other sites
I just added a second sata drive to my desktop system, the first was a 250GB WD drive, I just added a 200 GB seagate a week or two ago.

When I transfer data between the two drive, the seagate gets a dma time out error, and then just stops responding.  I tried to seperate the sata cables as much as i can so they hardly even come in proximity of each other, unfortunatly no one around here stocks sata cables of any decent lenghts. 

Is this problem likely that i just need sheilded cables?  Makes me warry about my future plans to create a massive SATA2 Raid5 array.

I'm running Gentoo linux, btw.  My motherboard is the DFI Lanparty B, nfroce2.  Running the latest bios.

Which kernel are you running?

Are you using the binary nvidia drivers, or the drivers in the kernel?

Thank you for your time,

Frank Russo

Share this post


Link to post
Share on other sites

Give the 2.6.9-gentoo-r5 sources a shot (gentoo-dev-sources). This resolved some CD-Rom to HDD transfer issues I was having on an nForce 420. Ping the thread if you need assistance with the configuration and compilation.

Thank you for your time,

Frank Russo

Share this post


Link to post
Share on other sites

OK, i just compiled gentoo 2.6.9-r9 dev sources, and the transfer rate between drives was definitly quicker, but after about a gig or so of data transfer between drives (and this is repeatable at approximatly the 1 gig mark) it starts spewing out errors.

The name of my box is mephisto, sda is the Seagate Drive and sdb is my Western Digital drive:

Dec 5 04:21:22 mephisto ata1: command 0x35 timeout, stat 0xd8 host_stat 0x61

Dec 5 04:21:22 mephisto ata1: status=0xd8 { Busy }

Dec 5 04:21:22 mephisto SCSI error : <0 0 0 0> return code = 0x8000002

Dec 5 04:21:22 mephisto FMK Current sda: sense = 70 80

Dec 5 04:21:22 mephisto Raw sense data:0x70 0x00 0x80 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

Dec 5 04:21:22 mephisto end_request: I/O error, dev sda, sector 136303623

Dec 5 04:21:22 mephisto ATA: abnormal status 0xD8 on port 0xF881A087

Dec 5 04:21:22 mephisto ATA: abnormal status 0xD8 on port 0xF881A087

Dec 5 04:21:22 mephisto ATA: abnormal status 0xD8 on port 0xF881A087

Dec 5 04:21:52 mephisto ata1: command 0x35 timeout, stat 0xd8 host_stat 0x61

Dec 5 04:21:52 mephisto ata1: status=0xd8 { Busy }

Dec 5 04:21:52 mephisto SCSI error : <0 0 0 0> return code = 0x8000002

Dec 5 04:21:52 mephisto FMK Current sda: sense = 70 80

Dec 5 04:21:52 mephisto Raw sense data:0x70 0x00 0x80 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

Dec 5 04:21:52 mephisto end_request: I/O error, dev sda, sector 136303631

Dec 5 04:21:52 mephisto ATA: abnormal status 0xD8 on port 0xF881A087

Dec 5 04:21:52 mephisto ATA: abnormal status 0xD8 on port 0xF881A087

Dec 5 04:21:52 mephisto ATA: abnormal status 0xD8 on port 0xF881A087

Share this post


Link to post
Share on other sites

If it is a cable issue it's more likely to be a bad connector somewhere, either on the drive itself or the mobo, rather than signal interference between the two conductors.

SATA uses low-voltage differential signalling along a twisted pair of conductors for both the incoming link and outgoing link. If it was an interference issue, the cable would be more likely to cause interference within itself than receive interference from a nearby cable... :)

The twisted pair structure and differential signalling will greatly cut down on the interference issue, so you needn't worry about that I think.

SATA connectors on the other hand are routinely bashed for being both fragile and insecure, early on there were plenty of cases where merely touching the cable/connector caused transmission errors, or where cables simply detached completely with little or no effort (such as transporting the PC in a car).

Have you tried all SATA connectors on your mobo/controller card and checked if it makes a difference?

Share this post


Link to post
Share on other sites

Yeah, my system has 4 SATA headers, and I tried all of them. The thing that puzzles me is that the problem only happens when both drives are mounted in the OS. I can have both drives connected, but as long as i don't have /dev/sdx1 mounted to /mnt/sataA or whatever it works fine.

It's just when both drives are mounted in the OS do i get a problem, and when i do a lot of data transfering.

It almost makes me wonder if it's a problem with the drivers? but if it were you'd think there would be a few more people out there bitching?

Share this post


Link to post
Share on other sites

I have only 1 SATA drive on sil_3512 controler and aswell am unable to run any kernel above 2.6.6 (getting similar error message as above)

tryed both Vinalla nad Gentoo versions of kernels, i guess ti something within the driver .

has anyone an idea ?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this