09-17-2009 08:54 PM
Hi, I'm having trouble with a new Barracuda 1.5TB SATA drive. Started receiving "Bad Block" errors in the Windows logs, so I ran chkdsk to fix, but it didn't fix anything. So I next installed SeaTools for Windows and tried to run the long generic test, and that failed shortly into the test (and doesn't provide an option to fix, what a pain!). So, I then downloaded SeaTools for DOS and created a CD. I booted from that, but it doesn't detect any of my large SATA drives. It finds my 500GB SATA drive just fine, but doesn't list any of my 1TB drives, or my new 1.5TB drive. So, it can't fix what it can't see. The on-board VIA controller doesn't recognize drives that large, so I'm using an add-in SATA controller for the larger drives, which are detected at boot-up just fine by the controller's BIOS, and Windows sees them just fine, but not in DOS. I'm assuming that it's a driver issue at the moment, but I have not been able to locate a DOS driver. The controller is using an Sil3114 chip set. Any ideas or thoughts would be welcome, since if I can't fix it I will have to ship it back, which will be a real pain for just a few bad blocks!
09-25-2009 11:15 PM
09-26-2009 07:06 PM - edited 09-26-2009 07:07 PM
Need to see some system specs mate, I suspect you have a latest tech drive on an oldish board?
Can you find your MB model number and the sata card post it, it'll save a lot of time if we know a bit about what you are running it on.
09-30-2009 05:13 PM - edited 09-30-2009 05:19 PM
10-28-2009 08:19 PM
Thanks fzabkar, that explains a lot. It figures that they would support almost every other SiI chipset other than the 3114!! That makes diagnosis and repair extremely dificult since I can't do it in this system. That only leaves me a couple of options. 1. Move the drive to another system that has a chipset that SeaTools supports, or 2. Go buy a different controller just to allow SeaTools to diagnose and repair my Seagate drives (not likely to happen, considering that the controller works perfectly in every respect with my other drives and with Windows!).
The really frustrating thing is that the other drive manufacturers utilities work just fine with this conroller. The IBM/Hitachi utility for example will boot up and see every drive in the system and even scan my Seagate drives, but of course won't repair anything but an IBM/Hitachi drive. Very frustrating. This is now my fourth Seagate drive to fail. My Samsung drives just keep humming.
Yes, Cantbecanit, it is an older board and controller. But as mentioned above, they both work flawlessly apart from the SeaTools issue, so I'm not going to retire them for that. This system is my domain croller/DVR/file server, so it doesn't have to be the greatest, just serve up files to the rest of the network clients, and it's little 2.6GHz Athlon processor does this just fine with plenty of cycles left over. I was just hoping that there was an easy fix to my delima, but alas it appears that it was not meant to be.
Thanks to all for your help.
10-28-2009 08:46 PM