EagleMed-IT
asked on
SAS Drive Firmware mismatch
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!
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!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
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.
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.
ASKER