From what I can see in the 3ware 3DM2 web interface (which responds fast) there is nothing wrong with the raid array, and no rebuild was done since February.
There are no events in the GUI also that I can see, but I don't know if they don't show because of an HTTP time out. The event window loads after a few minutes, but 0 events.
I will send the logs to support as soon as I can get them. I'm trying to reload the Status -> hardware page for the last couple of hours.. without success.
I guess the GUI might be an apache or similar running some application, is there anyway of restarting the web server without having to restart the whole system?
I contacted support with the log files and I was told that there were detected problems with the filesystem.
Now I ask, which file system might this be? the FS where the NSS resides on the flash disk or the filesystem of raid array itself?
I was told to run the Repair Filesystem under the Extended console tools, but this looks to me that it will repair the LV where all the data is on.
How could a problem in this filesystem affect only the GUI and not the volume performance, as everything appears to be OK with the volumes?
Anyway, it I'm to do this, how long does it take to repair a 2TB volume? Cos I have to schedule a maintenance window for this, as I will have to reboot the DSS.
The Filesystem repair will be for your Logical volumes not on the module as the module runs from memory. Engineers have asked you to run this and make sure to verify a memory test. To do this reboot the system and after POST enter the ESC or TAB key to access a basic menu.
For the time on the repair for 2TB depends on many factors but anywhere from 1 - 7 min. if all is running smoothly longer if there are other issues.
Yes, the issue is solved. Apparently it was related with remote LDAP auth.
Although the network was correctly configured and that the LDAP server is working well with other systems, somehow disabling the LDAP auth brought the system back to normal speed.
I decided to disable LDAP for now, as I was not using it lately.