Thanks @gatekeep and @mtexter for all your work. This is the only forum that I can find that has any useful information on this subject. You information has been most helpful. I have also found some more useful information in the documents found here:
ftp://ftp.kernel.ee/pub/IBM/LSI/I recently acquired a used Dell MD3000 array. I also have several Seagate 160GB and WD 2TB drives I would like to use in the array. AFIAK they are all Dell original drives, but only the Seagate 160GB drives are recognized. The WD 2TB drives are listed as Incompatible (Uncertified). Also in the serial console I get an error when inserting the "Uncertified" drive:
Code:
12/27/15-03:34:16 (GMT) (ssmSpin): WARN: Drive 0x1000b will be marked incompatible as DSM detected error: 5
Thanks to this thread I have been able to log into vxWorks and do some digging.
Version:
Code:
==============================================
Title: Disk Array Controller
Copyright 2005-2011 LSI Logic Corporation, All Rights Reserved.
Name: RC
Version: 07.35.39.64
Date: 08/16/2011
Time: 14:24:17 CDT
Models: 1331 1332 1333
Manager: devmgr.v1035api01.Manager
==============================================
I have logged into both controllers and run VKI_EDIT_OPTIONS and set driveSignMode=0. It reapplies everytime the controller reboots; however it does not seem to have any effect.
After setting driveSignMode=0 I have tried to execute both "dsmWipe 0x1000b,1" and dsmWipeAll. but both return:
Code:
-> dsmWipe 0x1000b,1
value = 12/27/15-04:21:14 (GMT) (tShellRem1): NOTE: DsmIOException Line 2905 File dsmDriveMgr.cc
0 = 0x0
->
I have noticed that there are quite a few symbol changes between FW 6.x and FW 7.x including the dsmWipe commands listed above. I wonder if the driveSignMode is no longer a valid symbol? If that is the case, would anyone know a new method for disabling the drive signature requirement? I have also considered trying to downgrade the firmware in the controllers, but I'm not sure if this is possible.
Thanks