Member_2_231077
asked on
Netapp disk in HP unit ?
Can anyone explain what this means? I've had to hack the ends off the serial numbers as it's not my SAN. The structure of the error message doesn't seem to match the product ID at first glance, it's logged against a HP MSA2000/P2000.
Controller A Serial Number: 2S6xxxxx
Controller B Serial Number: 2S69xxxxx
Chassis Midplane Serial Number: 2S6xxxxxx
Enclosure: 2
Slot: 4
Vendor: SEAGATE
Product ID: X411_S15K6420A15
Drive SN: 3QQ27HLM000090xxxxxx
Error: A disk that is part of a vdisk is down. Unknown reason. The disk may contain stale metadata. Recommended action: Clear the metadata to reuse the disk.
Controller A Serial Number: 2S6xxxxx
Controller B Serial Number: 2S69xxxxx
Chassis Midplane Serial Number: 2S6xxxxxx
Enclosure: 2
Slot: 4
Vendor: SEAGATE
Product ID: X411_S15K6420A15
Drive SN: 3QQ27HLM000090xxxxxx
Error: A disk that is part of a vdisk is down. Unknown reason. The disk may contain stale metadata. Recommended action: Clear the metadata to reuse the disk.
ASKER
What do you make of "Product ID: X411_S15K6420A15" ?
Array disk made by Seagate and sold by IBM and NetApp
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
dlethe, It's actually the other way round, the NetApp disk is in an HP unit.
I suspect they've just reformatted it using seatools. Would the NetApp HDD settings be retained after reformatting and cause the disk to keep going offline? It's still got the NetApp firmware on it as well. Does what you've said above apply in reverse?
I suspect they've just reformatted it using seatools. Would the NetApp HDD settings be retained after reformatting and cause the disk to keep going offline? It's still got the NetApp firmware on it as well. Does what you've said above apply in reverse?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The same firmware number means nothing other than the drive CAN be reprogrammed to match 100% of the operational characteristics of the desired drive. So actually it is a great thing if you have an original pre-programmed disk with desired settings (plus potentially OEM-specific settings other than the mode subpages / pages) ..
There is more to it than matching those. "Secret information can be programmed in other places that are not accessible by READ & WRITE I/O requests, but they too can be cloned.
The biggest exception to the rule is SATA disks. One can carve out protected regions and password protect them. As the password is 256 bits and brute force attempts will brick the drive, it would be a waste of time to try to clone that .. IF you determine that such a password exits.
Now it would not be unethical for me to take a SAS disk (or SATA drive that isn't protected) and clone settings onto another that has exact same firmware. There is no reverse engineering involved, there is no interpretation of data involved. There is no theft of IP involved. All of those scenarios come into play if one clones different models of disk and/or different firmware revisions and information has to be interpreted and extrapolated.
Whoops .. one more exception TCG drives. That is hands off theft of IP trying to deal with those.
There is more to it than matching those. "Secret information can be programmed in other places that are not accessible by READ & WRITE I/O requests, but they too can be cloned.
The biggest exception to the rule is SATA disks. One can carve out protected regions and password protect them. As the password is 256 bits and brute force attempts will brick the drive, it would be a waste of time to try to clone that .. IF you determine that such a password exits.
Now it would not be unethical for me to take a SAS disk (or SATA drive that isn't protected) and clone settings onto another that has exact same firmware. There is no reverse engineering involved, there is no interpretation of data involved. There is no theft of IP involved. All of those scenarios come into play if one clones different models of disk and/or different firmware revisions and information has to be interpreted and extrapolated.
Whoops .. one more exception TCG drives. That is hands off theft of IP trying to deal with those.
HP is not picky about disks. It will happily reprogram SFF-equivalent laptop drives onboard.
And their metadata is in visible sectors.
And their metadata is in visible sectors.
They don't reprogram the bad block format and layout. Proof of that is doing so requires a low level format MEDIA INIT
They also don't reprogram mode pages other than a few bits on page 1Ch
They also don't reprogram mode pages other than a few bits on page 1Ch
ASKER
Pity you addressed the solution as HP disk in NetApp SAN rather than the way I asked it as in NetApp disk in HP SAN. Solution is similar of course except I can't tell the customer "told you so" and point them to this thread to justify my refusing to send them HP branded replacements this way around.
For the record, the answer is the same for NetApp disk in HP SAN. The firmware is different.
For the record the array in question is years out of support, so whatever can be mashed together to work to reasonable degree is anywhere between free and cheap...
The issue is the firmware & mode page settings. HP & NetApp care a great deal about things like automatic error recovery settings, retry counts, prefetch constraints and such .. get them wrong and you end up with data corruption after retries.
RAID metadata usually is saved in the very last sectors of disk. It erases perfectly as on a disk without RAID