On Sun, Apr 19, 2009 at 1:28 AM, David C. Rankin
On the second, I didn't clue in to the buffered disk reads issue until I got the new drive from Seagate and compared the two with hdparm. Noticing the difference in buffered disk reads, I didn't want to have to send that drive in as well, so I just searched for any other possible solution and the firmware update was found. After the dramatic improvement the new firmware provided, I'd be willing to bet there is a 50% chance it would have fixed the first drive as well.
They actually had released a patch back in like October, but the patch was screwed up, and it was bricking drives. So, I never got around to checking to see if it was fixed after the first couple of weeks, since I never saw any progress. I'm suprised that it never hit slashdot when the good firmware was released. Fortunately for me, even though I didn't have a backup of that drive, a friend of mine has copies of most of what was on it, so I should be good one way or the other. It wasn't anything critical. And, I lost some critical stuff a couple of weeks ago when I lost my 80GB Seagate drive. It got a bad sector and I ran Spinrite on it, and it recovered it. Instead of making a backup, I just booted the drive. The next time I tried to boot, the Data was corrupted(and the drive was an OEM drive I got used and out of warrenty). My fault for not having a backup. My 2nd 500 and my 1.5T drive fortunately don't fall under the serial numbers of the problem. Only that particular drive. I never noticed the DMA hangs really, but it was only used for storage, or video re-encoding( which did hang sometimes, but I never pinned it to a particular drive since I had 2 500's and it would happen on either, and the fact that my Celeron E1200 is running a 100% overclock). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org