11-26-2008 06:33 AM
This is a 1.5TB -341AS drive, had SD17, updated to SD1A Windows Vista. First results from Sisoft with write cache on:
Detailed Benchmark Results
Buffered Read : 252.23MB/s
Sequential Read : 122.02MB/s
Random Read : 71.11MB/s
Buffered Write : 223.02MB/s
Sequential Write : 116.19MB/s
Random Write : 82.43MB/s
Random Access Time : 6ms
Then I went to device manager and turned off write cache. results:
Detailed Benchmark Results
Buffered Read : 252.51MB/s
Sequential Read : 123.45MB/s
Random Read : 75.01MB/s
Buffered Write : 48.71MB/s
Sequential Write : 119.12MB/s
Random Write : 71.60MB/s
Random Access Time : 5ms
I did a Bonnie in Solaris on the old firmware, I may test that again, but I'd have to Zen this whole image up to the server and format the drive, so I'd prefer someone really want that for some reason.
For some reason I do sometimes hear the drive making what sounds like a thermal re-calibration -- spinning down and back up again during a write operation.
11-27-2008 09:42 AM
Jafa so they actually gave you the wrong firmware the first time?
The explanation from support:
ST31500341A drives with part numbers of 9JU138-301 should be updated to CC1H.
Drives with part numbers of 9JU138 -300 and -336 should be updated to SD1A.
My drives are labeled -300. I was sent the CC1H firmware.
Support sent me the SD1A firmware to correct the problem but it failed to program.
It would be better if the CD image contained both frimware versions and the updater program chose the correct firmware based on the model of the hard drive. This would eliminate the need to be protective of the download and would eliminate mistakes by support.
11-28-2008 03:46 AM
My ST31500341AS p/n 9JU138-300 f/w SD17 totally hangs or leads to Windows BSOD with STOP 0x0000008e
I emailed firstname.lastname@example.org twice withing 2 days for new FW and still have no answer, is that normal?
11-28-2008 04:29 AM - edited 11-28-2008 04:30 AM
I got 5 of these, all with affected part number (-300) and dysfunctional firmwares (SD17/18).
I sent e-mail to support 2 days ago but... complete silence.
Just wonder if there's problems with the fixed FW too, why would they otherwise sit on them?
Perhaps AlanM could clarify the situation?
11-28-2008 07:37 AM
I have a -341AS which support did give me SD1A for it. I was getting bad block errors with Vista, so a stop error sounds reasonable to me. As I understand it now you need to phone support and ask for a manager to get the updated firmware. Its a silly rule, Western Digital has firmware for download on their page, and I agree with Nick that the software should just sniff out the part # and approve it. I have no idea the % of people savvy enough to jump through the firmware hoops to update the drive, but I imagine they'll be getting back some astronomical % of drive with what is a simple software bug. I see this whole snafu as being similar to the 75GB 'deathstar' IBM drives, except that that was a hardware bug without a recovery option, and this is at least (As far as we all can tell) a software bug.
On top of this all, they've apparently just re-did their support system. So it sounds like a perfect storm of a new support team plus buggy firmware that never should have passed Q&A. We loose in the short term, Seagate will loose in the long term with dissatisfied users.
11-28-2008 04:28 PM
To those of you awaiting an answer from support (me too)... Did you read that message on the technical support page:
The Call Center for North, Central & South America will be closed for a holiday on 11/27/08, reopening on 11/29/08. In the meantime please utilize Seagate's website or Knowledgebase to locate answers and we will be glad to further help you upon return.
So we'll have to wait...