No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Customers Assume That the Storage Device Fails to be Powered on Because the Startup Time is too Long

Publication Date:  2012-07-18 Views:  57 Downloads:  0
Issue Description
A customer powers off a S6800E before it is moved to a new equipment room. After the S6800E is installed in the new equipment room, the customer power it on and then logs in to it after it has been powered on for more than 20 minutes, but the S6800E enters the safe mode. After a few minutes, the 6800E is logged in to again, but it is still in the safe mode. The customer assumes that the S6800E fails to be powered on after removal.
Alarm Information
None
Handling Process

Step 1 Restart the S6800E. After 20 minutes, the S6800E can be logged in to because the dirty data has been flushed to data disks during the previous power-on.

Step 2 Onsite engineer should be patient when a similar fault occurs.

Root Cause

1. According to the collected logs, the customer connects seven disk enclosures to the controller enclosure and creates many 100 GB LUNs. Therefore, LUN connection takes about 18 minutes.

 2. The storage system takes about 15 minutes to flush the dirty data from coffer disks to data disks. Therefore, the storage system is still in the safe mode after it has been powered on for more than 20 minutes. 3. Although the services in the storage system have been stopped before removal and the disk indicators are off, the dirty data in coffer disks is not flushed to data disks immediately. Therefore, the dirty data still exists in coffer disks when the storage system is powered on again.

Suggestions
Coffer disks are designed for data reliability and energy saving. When no service runs in a storage system, the data in the cache is not written to data disks immediately if the amount of data stored in the cache does not reach the preset threshold, and the process has low priority, that is, the process is executed every several seconds. Similar faults often occur. Onsite engineers are advised to wait for longer time to log in to the storage system again after the storage system enters the safe mode.

END