| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Files spread between Dropbox, Google Drive, Gmail, Slack, and more? Dokkio, a new product from the PBworks team, integrates and organizes them for you. Try it for free today.

View
 

Drive fault - Dashboard on web interface will not load

Page history last edited by Wesha 9 years, 8 months ago

When using Intel/EMC software version 1.1.11.32736 or lower

 

Problem: When powering on the server after it has been off the drive LEDs on the front may be lit an amber color indicating a drive fault. The web interface will work, but when attempting to access the Dashboard section the web page will not load and the web service will fail to provide access to any other pages.

 

!!!Warning!!! Use this guide at your own risk. The process I used here was avoided at first because I was initially unaware of the consequences. Even though I am confident with the results, they may change based on the problem at hand.

 

Solution: Turn off the server using the front power button. Once the server is off locate the reset button on the back of the unit. Using a pen or similar device press in the reset button and hold it while turning on the server from the front button. Continue holding in the reset button for 5 seconds. This will reset the firmware on your device to the factory version.

 

The server will use DHCP to get its IP address. If you have the device on a router, log into the router to find which IP has been leased to it.

Connect to this address in a web browser.

 

You will be asked to enter a new password for the server. Configure the box settings as necessary, including time zone, IP address, etc.

The built in software will scan the filesystem of all the disks. If there are no issues with the drives themselves the lights on the front of the unit should be steady blue.

At this point it may appear everything is back online, however, some files may not be accessible due to server permissions. You may also notice that any users that were created previously do not show up. The next step is to upgrade the firmware.

In the web interface go to Settings and click Update. Click to Update the device software to the latest version. (It is assumed that the latest version is the last version that was used before the drive faults)

 

After updating the software and restarting any old data should be accessible again. All previous users should be returned as well. Configure the system as desired and you are done.

 

 

 

Comments are welcome.

 

 

---

Debugging information:

 

Here is some logging information that was captured during the drive faults I was having. I used SSH to access the logs.

 

/var/log/evms-engine.log

Nov 21 15:12:55 NAS _3_ LocalDskMgr: check_multipath: Cannot get list of DM devices.

Nov 21 15:12:55 NAS _3_ LocalDskMgr: check_multipath: Cannot get list of DM devices.

Nov 21 15:12:55 NAS _3_ Engine: engine_ioctl_object: ioctl to object md/md0 failed with error code 19: No such device

Nov 21 15:12:55 NAS _3_ Engine: engine_ioctl_object: ioctl to object md/md0 failed with error code 19: No such device

Nov 21 15:12:55 NAS _5_ Engine: initial_discovery: Discovery time: 00:00:00.068693

Nov 21 15:12:55 NAS _5_ Engine: is_object_change_pending: Change pending: Object sda1 needs to be activated.

Nov 21 15:12:55 NAS _5_ Engine: is_object_change_pending: Change pending: Object sdb1 needs to be activated.

Nov 21 15:12:55 NAS _5_ Engine: is_object_change_pending: Change pending: Object lvm2/md0Container/md0Region needs to be activated.

Nov 21 15:12:55 NAS _5_ Engine: is_object_change_pending: Change pending: Object md/md0 needs to be activated.

Nov 21 15:12:55 NAS _5_ Engine: is_volume_change_pending: Change pending: Volume /dev/evms/md0vol1 needs to be activated.

Nov 21 15:12:55 NAS _5_ Engine: is_volume_change_pending: Change pending: Volume /dev/evms/md0vol1 needs to have fsck run on it.

 

/var/log/soho.log ? (didn't write down the log name)

2009/11/21 15:13:28.229174: appweb[1031]: DEBUG: openshr: Unable to open file '/tmp/sohoUserEvents.xml' (2)

2009/11/21 15:13:28.229528: appweb[1031]: DEBUG: loadXmlFile: Unable to open file '/tmp/sohoUserEvents.xml' (-1)

2009/11/21 15:13:28.229597: appweb[1031]: TRACE: Unlocked file '/etc/sohoConfig.xml'

2009/11/21 15:13:34.120864: appweb[1031]: TRACE: Locked file '/etc/sohoConfig.xml'

2009/11/21 15:13:34.120971: appweb[1031]: DEBUG: openshr: Unable to open file '/tmp/sohoUserEvents.xml' (2)

2009/11/21 15:13:34.121004: appweb[1031]: DEBUG: loadXmlFile: Unable to open file '/tmp/sohoUserEvents.xml' (-1)

2009/11/21 15:13:34.121038: appweb[1031]: DEBUG: openshr: Unable to open file '/tmp/sohoUserEvents.xml' (2)

2009/11/21 15:13:34.121068: appweb[1031]: DEBUG: loadXmlFile: Unable to open file '/tmp/sohoUserEvents.xml' (-1)

2009/11/21 15:13:34.121453: appweb[1031]: TRACE: Unlocked file '/etc/sohoConfig.xml'

2009/11/21 15:13:40.004403: appweb[1031]: TRACE: Locked file '/etc/sohoConfig.xml'

2009/11/21 15:13:40.004861: appweb[1031]: DEBUG: openshr: Unable to open file '/tmp/sohoUserEvents.xml' (2)

2009/11/21 15:13:40.004901: appweb[1031]: DEBUG: loadXmlFile: Unable to open file '/tmp/sohoUserEvents.xml' (-1)

2009/11/21 15:13:40.004935: appweb[1031]: DEBUG: openshr: Unable to open file '/tmp/sohoUserEvents.xml' (2)

2009/11/21 15:13:40.004965: appweb[1031]: DEBUG: loadXmlFile: Unable to open file '/tmp/sohoUserEvents.xml' (-1)

2009/11/21 15:13:40.005037: appweb[1031]: TRACE: Unlocked file '/etc/sohoConfig.xml'

2009/11/21 15:13:45.896199: appweb[1031]: TRACE: Locked file '/etc/sohoConfig.xml'

2009/11/21 15:13:45.896295: appweb[1031]: DEBUG: openshr: Unable to open file '/tmp/sohoUserEvents.xml' (2)

2009/11/21 15:13:45.896329: appweb[1031]: DEBUG: loadXmlFile: Unable to open file '/tmp/sohoUserEvents.xml' (-1)

2009/11/21 15:13:45.896363: appweb[1031]: DEBUG: openshr: Unable to open file '/tmp/sohoUserEvents.xml' (2)

2009/11/21 15:13:45.896392: appweb[1031]: DEBUG: loadXmlFile: Unable to open file '/tmp/sohoUserEvents.xml' (-1)

2009/11/21 15:13:45.896454: appweb[1031]: TRACE: Unlocked file '/etc/sohoConfig.xml'

2009/11/21 15:13:51.788070: appweb[1031]: TRACE: Locked file '/etc/sohoConfig.xml'

2009/11/21 15:13:51.788166: appweb[1031]: DEBUG: openshr: Unable to open file '/tmp/sohoUserEvents.xml' (2)

2009/11/21 15:13:51.788199: appweb[1031]: DEBUG: loadXmlFile: Unable to open file '/tmp/sohoUserEvents.xml' (-1)

2009/11/21 15:13:51.788234: appweb[1031]: DEBUG: openshr: Unable to open file '/tmp/sohoUserEvents.xml' (2)

Comments (0)

You don't have permission to comment on this page.