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>


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


How to Judge that an Underlying Link of the S5100 Storage Device is Unstable?

Publication Date:  2012-07-20 Views:  122 Downloads:  0
Issue Description
Underlying links of the S5100 become unstable due to device insertion or removal, power cycle, I/O timeout, or error code. When an underlying link becomes unstable, all I/O requests cannot be delivered. If an underlying link of the S5100 is in the unstable state for a long time, the device performance dramatically deteriorates. This case describes how to judge that an underlying link is unstable and how to find the reasons.
Alarm Information
Handling Process
Refer to accessory
Root Cause
If a link becomes unstable due to device insertion or removal, or power cycle, it is a normal phenomenon, and the system does not remain unstable for a long time or frequently. If no device is inserted or removed from the system and the system is not restarted, but events are still generated to inform device insertion or removal, it indicates that a link becomes unstable, which may be caused by I/O timeout or error code.
Error code may cause unstable links, which does not mean that once error code is generated, links become unstable. When device insertion or removal is detected on the S5100, the entire device is scanned. During the process, links become unstable temporarily. It is a normal phenomenon. When you detect that error code is generated on a disk slot or expansion port, it is unwise to immediately judge that the disk slot or expansion port causes unstable links. You should repeatedly run the showphyerrcode command at an interval to check the changes of error code. If error code is generated on a disk slot or expansion port continuously, the disk slot or expansion port may cause unstable links.