We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

SAS Drive Firmware mismatch

EagleMed-IT
EagleMed-IT asked
on
Medium Priority
1,081 Views
Last Modified: 2012-05-11
Greetings all

I have 6 Seagate Cheetah's all with model number ST3300655SS. I want to use these in a single RAID 10 array, however 3 of them have a firmware of S527 and 3 of them with firmware S513. So the drives are the exact same model and size, just different firmware.

I have seen RAID array's built before with firmware mismatches but I wanted to know if this is not recommended and for what reason.

Thanks all!
Comment
Watch Question

President
CERTIFIED EXPERT
Top Expert 2010
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
andyaldersaggar maker's framemaker
CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
In the end built the raid 10 array with 6 drives 2 sets of differing firmware. At this point there has been no issue.
DavidPresident
CERTIFIED EXPERT
Top Expert 2010

Commented:
You should still take the time to read release notes on the firmware.   I can't (won't) tell you how many times I see SEV-1 bugs in HDD firmware releases that address data loss when such-and-such happens.   Even releasing a firmware update, any update costs a manufacturer well over $50,000 in engineering & tests costs, plus you can more than double that for your subsystem OEM if they take the time to re-release a vanity version.

Granted, many times the revised firmware fixes an issue that only manifests itself on configurations you don't use, but you have no way of knowing.  I've seen seagate updates that fix anything from incorrect data getting retrieved from read cache depending on cache parameters; to disks locking up on certain errors; even disks refusing to spin up after a power cycle.   Ask yourself if they are spending $100,000 + to get an update out that isn't probably important.
andyaldersaggar maker's framemaker
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
I agree, bad decision not to start off with a clean sheet with the latest firmware everywhere, and bad decision to give us a C grade :(

Sure a firmware update could knock something out of sync, but that's all the more reason to get it out of the way now before putting the kit into production.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.