Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi
I just bought two 1TB seagate sata2 HD's
I am running a temporary system because I am still waiting for my new
mobo/ram/cpu to arrive. So now I run
epox ep8k9a2+ mobo
athlon 2800+
1,5 gb ram.
Xp pro 32bit, sp2_______SHORT VERSION_________
I have problems with my two new SATA2 1TB Seagate drives.
All sorts of errors from chkdsk, Format and in Event Viewer.
The disks sometimes appear to be working, but when trying to use them,
I get errors.
I DID put a jumper for restricting to SATA1 mode (1,5gb/s)
In event Viewer I get two errors every minute (=120 errors per hour).
There are 3 different ones, all with EventID 7011:
30000 milliseconds timeout from ShellHWDetection
30000 milliseconds timeout from dmserver
30000 milliseconds timeout from TrkWks.Anyone recognize this?
_______LONG VERSION_________
The main board has onboard SATA controller (SiI3112, 2 ports).
First I tried to install one of the disks in this one, but then thesystem would not start, so I disabled it in bios again.
Then I installed a sata raid PCI card (SiI 3114, 4 ports). And the it
SEEMED to work.
But not with my two older SATA1 250gb drives.
So I enabled the onboard controller again at put the old drives on thisone.
I XP I could not format the new disks in disk manager. It would
initialize and let me choose all settings, it would start format and
run until 99%, then a popup message saying that it was unable to
format. I tried this on both my new disks, but exactly same thing.
Then I got the tool called DiscWizard from Seagate and it would format
both disks (took only few minutes).
Then the disks got recognized in XP as disks with new partitions, and I
can copy files to Drive 1, but not to Drive 2; it says that the
partition is RAW.
I tried chkdsk with F switch, with F and R switch and /F /R /X but on
Disk 2 chckdsk hangs and on Disk 1 it says that there are failures,
begins to repair but then stops, saying that there is not enough space
or undefined error.
And now when I try to open Seagate DiskWizard, it hangs. Wanted to try
reformat.
Command line Format in XP checks the disks, but when trying to make a
file system structure it fails.
I have the latest driver for the PCI controller card. But I am in doubt
if it has the latest BIOS. Could that be something to check?
I also get warning in Event Viewer saying that the driver has predicted
that \Device\Harddisk3\DR3 will fail. I am not sure which of the disks
this is, but the one called Disk 3 Disk Manager is my old 250gb SATA1
drive that runs on the onboard controller. I just did a chkdsk /F /R /X
on it and there were no errors.
Temporary conclusions:
The two disks act differently - that puzzels me.
Each of them do not generate the same error all the time - it is as ifthey NEARLY work, but then dont.
They run on the PCI controller, but not on the onboard one. That pointsin the direction that the problems has to do with the disk and not the
controller. But that is only a theory.
Further checking:
Right now I am checking all the disks so I cannot try anything in acouple of hours.
I have an identical controller card that I am going to try.
Also I want to try the new disks one at a time. In both the onboard andPCI.
Is there some setting in the main board's bios that I should check?
Is there a good diagnostic tool that might not hang?What else should I check?
All suggestions are welcome

Oops sorry for the empty lines :)
I just bought two 1TB seagate sata2 HD'sI am running a temporary system because I am still waiting for my new mobo/ram/cpu to arrive. So now I run
epox ep8k9a2+ mobo
athlon 2800+
1,5 gb ram.
Xp pro 32bit, sp2_______SHORT VERSION_________
I have problems with my two new SATA2 1TB Seagate drives.
All sorts of errors from chkdsk, Format and in Event Viewer.
The disks sometimes appear to be working, but when trying to use them, I get errors.
I DID put a jumper for restricting to SATA1 mode (1,5gb/s)
In event Viewer I get two errors every minute (=120 errors per hour).
There are 3 different ones, all with EventID 7011:
30000 milliseconds timeout from ShellHWDetection
30000 milliseconds timeout from dmserver
30000 milliseconds timeout from TrkWks.Anyone recognize this?
_______LONG VERSION_________
The main board has onboard SATA controller (SiI3112, 2 ports).
First I tried to install one of the disks in this one, but then the system would not start, so I disabled it in bios again.Then I installed a sata raid PCI card (SiI 3114, 4 ports). And the it SEEMED to work.
But not with my two older SATA1 250gb drives.
So I enabled the onboard controller again at put the old drives on this one.I XP I could not format the new disks in disk manager. It would initialize and let me choose all settings, it would start format and run until 99%, then a popup message saying that it was unable to format. I tried this on both my new disks, but exactly same thing.
Then I got the tool called DiscWizard from Seagate and it would format both disks (took only few minutes).
Then the disks got recognized in XP as disks with new partitions, and I can copy files to Drive 1, but not to Drive 2; it says that the partition is RAW.
I tried chkdsk with F switch, with F and R switch and /F /R /X but on Disk 2 chckdsk hangs and on Disk 1 it says that there are failures, begins to repair but then stops, saying that there is not enough space or undefined error.
And now when I try to open Seagate DiskWizard, it hangs. Wanted to try reformat.
Command line Format in XP checks the disks, but when trying to make a file system structure it fails.
I have the latest driver for the PCI controller card. But I am in doubt if it has the latest BIOS. Could that be something to check?
I also get warning in Event Viewer saying that the driver has predicted that \Device\Harddisk3\DR3 will fail. I am not sure which of the disks
this is, but the one called Disk 3 Disk Manager is my old 250gb SATA1 drive that runs on the onboard controller. I just did a chkdsk /F /R /X on it and there were no errors.
Temporary conclusions:
The two disks act differently - that puzzels me.
Each of them do not generate the same error all the time - it is as if they NEARLY work, but then dont.
They run on the PCI controller, but not on the onboard one. That points in the direction that the problems has to do with the disk and not the controller. But that is only a theory.
Further checking:
Right now I am checking all the disks so I cannot try anything in a couple of hours.I have an identical controller card that I am going to try.
Also I want to try the new disks one at a time. In both the onboard and PCI.Is there some setting in the main board's bios that I should check?
Is there a good diagnostic tool that might not hang?What else should I check?
All suggestions are welcome

Oh
and I do have a fan on each disk so they do not overheat.I am also unsure if the PCI-card can run JBOD
It says it can do RAID 0,1,5,10, but do not mention JBOD. There is no such option in its own BIOS.
Could that cause all the trouble?

OK my conclusion is that there is nothing wrong with the disks!
I tried my other controller card (that has newer BIOS. It seemed a little better, but still all operation (chkdsk, format etc) was extremely slow.
And the same messages in Event Viewer.So I booted in an older install of XP and now everything seems fine.
I just formatted Disk 1 in Disk Manager and copied a lot of files to it. No problems
And right now Disk 2 is formatting.
Not a thing in Event Viewer!
One detail that might be omportant: I did a quick low level format in the BIOS menu of the controller card.
Could it perhaps be the format that the Seagate program did, that XP cannot handle?
I just chose default settings, which included no exra space beyond the partition. I know Windows leaves some megabytes for some reason

For these message:
30000 milliseconds timeout from ShellHWDetection
30000 milliseconds timeout from dmserver
30000 milliseconds timeout from TrkWks.Do you have Daemon Tool or older hard drive (specificly Maxtor brand)in your newer XP?
Remove them and make sure your card can handle 1TB

I have Fantom CD a program equal to Alcoho 120%
And I have two older maxtor 80 gb PATA and one maxtor 250 gb SATA 150
The disks are also installed in the XP where there are no trouble, so I will try to remove Fantom CD.
Thanks for the tip!

I have encountered remarkably similar problems after installing a new Seagate 160Gb SATA-300 Seagate drive (with jumper removed) in place of my old 60Gb SATA-150 Seagate drive (system Ghosted across), when subsequently trying reformat the old 60Gb drive (now placed in an adapter in the CD/DVD bay) - same Disk Management errors and same timeout errors in the Event log.
The problems seemed to somehow be due to the fact that I had two bootable drives installed in the system. This seemed to be somehow confusing the TrkWks client.
I eventually discovered that if I disabled the TrkWks service, then the XP Disk Management utility was able to operate normally, and I succeeded in reformatting the old 60Gb drive.
I've subsequently renamed the TrkWks service, but am now getting the TrkWks and shellHWDetection timeout errors when trying to back up by system using PC Data Connected, which hangs. I can't Cancel the PC Data Connected backup operation, and if I try to Shutdown the laptop, the Shutdown operation hangs after logging me off, and I have to force a power cycle.
Any suggestions most welcome!

Thanks for the reply.
I discovered that I had used standard HD jumpers that do not fit very well, but I thought it would work.
When I put the drives on a 300gb/s controller, I had no problems at all. And with the right jumpers it was fine too.

![]() |
Can't burn in XP
|
Cannot print from a share...
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |