EMC AX100 Release Notes - Page 22

Known problems and limitations Description AX100 and AX100i - After reboot, although you can ping one or both SPs, neither SP is accessible for I/O. The SP boot/fault light on the SP is blinking. This may also be seen during a reboot due to a software upgrade of the FLARE OE. AX100, AX100i, AX100SC, AX100SCi -- During an upgrade operation a message similar to the following appears in the event log: Checking file system on C: The type of the file system is NTFS. Volume label is FLARE Partition. Details Frequency: Very Intermittent Prevention/resolution: Shut down and restart the storage system. If this does not work, then see the AX100 hardware troubleshooting trees for the SP boot/ fault light on the AX100 support website. Frequency: Every Time Prevention/resolution: The message is expected and should be ignored. A disk check has been scheduled. Windows will now check the disk. Cleaning up minor inconsistencies on the drive. ... Windows has finished checking your disk. Please wait while your computer restarts. This is due to an intentionally scheduled run of a utility to verify that all files were transferred and installed on the storage system correctly. (83371) AX100i, AX100SCi - If the host iSCSI name is being changed from the default, the new name must be a minimum of 16 valid characters in length. If the iSCSI name is shorter than 16 characters, the host will not configure its virtual disks at powerup. (118537). AX100 and AX100i - Under certain conditions following a virtual disk expansion, the capacity reported for the virtual disk will remain the original capacity even though the expansion was performed. This can occur only when the user does not specify a capacity when starting the expansion. If the user specifies a capacity value (does not take the default) when starting the stripe expansion, then the new capacity is reported correctly. (128513) Frequency: Every time Prevention /resolution: Create an iSCSI name with a minimum of 16 valid characters. Frequency: This requires Navisphere Manager to be used. This condition will occur Every Time under the following conditions: the user 1) does a no-grow expansion, 2) changes the capacity of the meta-virtual disk, 3) does an expansion. In this case the expansion in 3) always leaves the capacity at the prior value. This condition occurs Very Intermittently in the case where no-grow is not involved and only in cases where the user is performing multiple meta-virtual disk expansions at the same time. Prevention/resolution: To prevent the condition, specify a capacity when initiating the meta-virtual disk expansion. If the failure has already occurred, use Navisphere to manually change the capacity of the meta-virtual disk to the correct capacity. 22 EMC AX100-Series Integrated Management Software Release Notes