1 ) to pull out all the new hard drive does not recognize the newly added 2 ) Log in to any

one controller command-line interface ( through the serial por t or through rlogin protocol software can use Putty ) 3 ) The first piece of the new hard disk into the original slot , there is no co mmand-line interface to observe the following pop-up message : -> 07/22/09-04: 12:31 (GMT) (utlTimer): NOTE: fcnChannelReport ==> 0 +1 2 +3 = 4 = 5 = 6 = 7 07/22/09-04: 12:34 (GMT) (utlTimer): NOTE: fcnChannelReport ==> 0 +1 2 +3 = 4 = 5 = 6 = 7 07/22/09-04: 12:54 (GMT) (ssmDriveSpinTask): NOTE: cfgCommonReplaceCode: dev = 0 x400004 07/22/09-04: 12:54 (GMT) (ssmDriveSpinTask): WARN: Unsupported dacstore: dev = 0 x400004 07/22/09-04: 12:54 (GMT) (ssmDriveSpinTask): WARN: Unsupported dacstore: dev = 0 x400004 02/12/09-04: 27:00 (GMT) (ssmDriveSpinTask): WARN: Unsupported dacstore: dev = 0 xe 02/12/09-04: 27:00 (GMT) (ssmDriveSpinTask): WARN: Unsupported dacstore: dev = 0 xe Whenever you see the words "Unsupported dacstore", will be able to determine the new hard disk data structures can not be identified in the current microcode . We can solve the following way . The solution is to separate each new hard DacStore clear , as follows: 1 ) The controller's command line, type the command "isp cfgWipe1, 0x400004". Va lue after the comma is the pop-up message "dev =" behind the string of values, s uch as "0xe" or "0x400004". ( Actually a new hard devnum) 2 ) to pull out of the new hard disk , and then insert a new hard disk had a sec ond slot , the new pop-up messages to observe the command-line interface , acces s to new devnum 3 ) Repeat steps 1 ) and 2 ) until all the new hard DacStore are cleared. 4 ) all pulled out in order to insert a new hard disk . The new hard disk system can be identified . Note: 1 If there is no new data to any client installed , you can first of two control lers in the command line execution "sysWipe", the command will clear all disposa ble disk DacStore. Then restart the nose on the line. (SysWipe command can only be installed in the absence of any new case of execution of customer data must n ot be executed in the case of data , otherwise it will delete all customer data ) (2) In the case of data down a single block of a new hard drive in order to clea r the DacStore, devnum parameters must be careful , to be pop-up message "dev =" string of value behind , such as "0xe" or "0x400004". Must not make a mistake, otherwise the existing customer data to the hard drive removed . 3 can pull out all the new hard drive in the beginning after the first pass "cfg PhyList" command to get all the existing hard drive devnum, to ensure that no mi stype devnum.