I recently had an issue attempting to extend our production NAS file pool on our NS-960. We had just added Six new 2TB SATA disks to the array, and when I launched the Disk Provisioning Wizard it gave me this error:
“The number of drives available for provisioning additional storage are insufficient”.
That of course wasn’t true, as a 4+2 RAID6 config is indeed supported on this platform and I had just added six drives. I did come up with a workaround to do it manually thanks to some helpful advice from our local EMC technical rep. I manually created a RAID6 Raid Group in a 4+2 config, and then created a single LUN using all of the available space in the Raid Group (about 7337GB). Once the LUN is created, you can add it to the Celerrra storage group, in my case it was named “Celerra_hostname”.
When adding the LUN to the storage group, there is a critical step that you must not skip. The HLU number must be modified! After you click on a LUN, click add, look for it in the list and notice that the far right column shows the HLU (Host LUN ID). The LUN you just added will have a blank entry. It doesn’t look like it’s an editable field, but it is – simply click on the blank area where the number should be and you’ll get a drop down box. The number you chose must be greater than 15. Once you’ve modified the HLU for the new LUN, then click on OK to complete the process.
Next, you’ll want to switch back over to the Celerra Management interface, click on the ‘Storage’ tab, then click on the ‘Rescan Storage Systems’ link. You will get a warning message that states:
“Rescan detects newly available storage and storage systems. Do not rescan unless all primary Data Movers are operating normally. The operation might take a few minutes to complete.”
Heed the warning and make sure your data movers are up and functional. You can monitor the progress in the background tasks area. On my first attempt the Rescan failed. I got this error message:
“Storage API code=3593: SYMAPI_C_CLARIION_LOAD_ERROR. An error occurred while data was being loaded from a Clariion.” | “No additional information is available” | “No recommended action is available”.
At the point I got that error I was at the end of my work day and decided to get back to it the next day. I had planned on opening an SR. When I re-ran the same scan the next day it worked fine and my production pool auto-extended. Problem solved.