Lacie 131018 User Manual - Page 198
Symptom, Reason, Solution
UPC - 093053789114
View all Lacie 131018 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 198 highlights
StorView RAID Module Symptom Reason Solution Lost communication Service is hung. with the RAID Controllers.(continued) On Linux system access the process viewer and stop the StorView Process. Restart the process and click the Rescan button on the StorView Main screen. Hot spare not automatically starting when drive failure occurs in a redundant array in which a global or dedicated hot spare is defined. The Auto Rebuild option is not Open the Controller Information enabled in the Controller Parameters. window (click the Controller icon), Hot spare disk drive is too small to be place a check mark in the box by used for the drive replacement. clicking the check box on the Auto Waiting for a valid replacement drive Rebuild parameter. to be inserted. Ensure that the disk drive defined as a hot spare is equal to or greater than the size of the drive members of the arrays. Auto Rebuild is not selected and no hot spare drive is assigned, but Auto Hot Spare is enabled. The array will begin rebuilding once a valid replacement drive is inserted in the drive slot of the failed drive. Consistently occurring time out errors when the browser window is open. Host HBA parameter settings are not configured for best performance optimization. Access your Host HBA settings and make the following changes: Execution Throttle Improve general I/O performance by allowing more commands on the fibre bus. Do this by changing your host bus adapter's execution throttle parameter to 256. Scatter/Gather (Microsoft Windows) Increase the general I/O performance by allowing larger data transfers. Do this by editing the "MaximumSGList" parameter in the register. The recommended hexadecimal value is "ff." The path is: HKEY_LOCAL_MACHINE/System/ CurrentControlSet/Services//Parameters/Device/. Shared Memory Error is displayed. The CGI script manager may have not This may occur when heavy I/O is released a segment of shared happening at the same time you are memory. accessing StorView. If this occurs you will need to stop and then restart the StorView Server service. 190