
Many have criticized Seagate’s handling of the firmware problems, with initial slowness to publically address issues, fuzziness on which drives were affected and culminating in the vendor offering free data recovery services for those with bricked drives, with advanced exchanges for select customers. Our own Rage3D Administrator Lupine chronicled his issues with affected drives, RMA’ing problem drives and receiving drives with the same problem firmware back.
In the meantime, I had left my four Seagate 7200.11 1Tb drives doing backup duty as a RAID 5 set in an external enclosure. The original SD01 firmware stood the test of time, with no random rebuilds, dropped drives or poor performance seen – workhorses, all around. Moving to a new backup architecture, the drives became free once more for a revisit: new firmware, SD1A. Like before, no extravagant testing methods were used – just throw HDTach’s long bench at it three times and average the results.

Ideally the cache should be write-though – the data is written to the disk and kept in the cache for faster reads, vs. write back mode where data is flushed from cache periodically. In this mode data is very sensitive to power reliability and system stability; a bad overclock, system crash or a power interruption could not only cause data loss but operating system corruption if critical files are not written to disk.
To account for this, the tests were performed with the write cache enabled, and disabled, via the Intel Matrix Storage Manager. The CPU used in the system was an Intel Xeon X3210 B3 quad core processor, clocked at 3Ghz, with 4Gb of Buffalo Firestix DDR2 ram running at 900Mhz 5-5-5-15.
Seagate claims 105MB/sec maximum transfer rate for the ST31000340AS, which was verified in HDtach for the first 20% (200 GB) of the drive, in single disk configuration. Interestingly, the ST31000333AS 1Tb and ST3150041AS 1.5Tb drives are rated at 115MB/s and 120Mb/s, respectively. Those of you taking advantage of the recent sales on 1Tb and 1.5Tb drives are getting some fast drives, cheap.
Single and Two Disk configurations:
Here are the results for single disk and RAID 0 from the previous review Vista x64 benchmarks and the new flashed firmware, with write cache enabled and disabled:

No significant difference seen, certainly the differences in burst or average speed can be accounted for in the variations of driver and controller used. The single disk SD1A firmware appears marginally faster that the SD01.
Looking at RAID 1, again no big surprises:

Here I again included the single disk results to allow a simple contrast of RAID 1 with single disk. How much do you lose with the added redundancy? Hard to say as this is not a write test, but interesting to see how much benefit the RAID 1 performance gains from Intel Write Cache. Indeed, the Intel RAID 1 mode uses both disks for simultaneous reads, allowing different data to be read from both disks at the same time.
Three Disk Configurations:
These results compare the previous review’s Vista x64 results for RAID 0 and RAID 5 with updated firmware disks in Raid 0 and Raid 5. The previous review highlighted an issue both the LSI and Adaptec controllers had under Vista x64 with large parity configurations.

Using the ISM the SD1A drivers are clearly performing better. Again the use of write cache is noticeable, not only in burst results but in sustained average reads as well. CPU usage is low, 3-4% without write cache enabled and 6-10% with write cache enabled.
Four Disk Configurations:
Finally, we contrast the four disk results. These were the most problematic in the previous review – Vista 64bit driver issues, >2Gb volume issues under 32bit Windows XP. With the Intel ICH it was a breeze to generate results. Throughout the tests, the Intel Matrix Storage volume was initialized as a basic disk using GPT and a single volume created and quick formatted before bench testing.

Here, with write cache disabled, CPU usage stayed low at 3-4%. Enabling the write cache saw a jump to 11% for RAID 5 and 13% for RAID 0, with RAID 10 at 8% cpu usage. It would be interesting to see how CPU usage with write cache scaled up with five and six disk arrays. The increase is CPU usage makes me wonder if more than 4MB cache is used, depending on the size of the array and number of members. In terms of speeds the SD1A firmware drives have a strong showing here, mostly due to mature drivers I think.

So how am I using these four ST321000430AS drives? In my HTPC/NAS with three disks in Intel Matrix Storage RAID 5 with the fourth disk as hot-spare and auto-rebuild target, running on a UPS. While no RAID array replaces a backup solution, it can give immense peace of mind for storage security. Load times for UT3 aren’t bad, either…