storeonce catalyst store:E0805001b : The system has detected a potential filesystem issue

[TheSeeker]

We ran into this error on Catlyst store after a power outage/lightining strike; caused it to reboot.  

storeonce catalyst store:E0805001b : The system has detected a potential filesystem issue

However, 2 stores are not starting.  already tried rebooting the server gracefully 

Ran into an artilce that says to check "The store was taken offline due to a bad integrity flag." however the resolution involves accessing the shell using  log in to root using the HPsupport password

- these devices are out of support at the moment.  I wanted to login to the linux shell; and I cant find the password for this account.  Is there a way to reset this.  Unfortunelty the catalyst stores have data which shows up when I manually look at it via the webportal however cant restore the data via the backup software.

[sbhat09]

Hello @TheSeeker,

Which Generation and which model of StoreOnce system it is?

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[TheSeeker]

@sbhat09 Version : 3.18.7-1841.1

got these steps as well

1. Stop the serviceset gracefully from the admin cli (serviceset stop all).
2. Check the services status until they are stopped gracefully by using the command "serviceset show status all"
3. Once the services are stopped and shown as "Not Started", log in to root using the HPsupport password. Type hps or hp and hit enter. Then key in the 2 day or 20days password. Once service level is reached. Type 'shell" to get to the Linux prompt.
4. Proceed to the path of the store in question in this case. cd /ifs1/d2d/ssid1/data/dedupe/co/st/s.d/s_0X/ - Where X is the store with integrity. Also try 'ls /ifs1/d2d/ssid1/data/dedupe/co/st/s.d/s*' (without quotes) to find out the folder with s.bad_integrity file.
5. Rename/remove the s.bad_integrity file by using rm or mv command. (mv s.bad_integrity s.bad_integrity.old)
6. Go to the ifs1/d2d/ssid1/config folder to check if there is a recover.me or ibdircheck.request file. This is only needed if the store fails for the first time. Do a 'touch recover.me' (cd /ifs1/d2d/ssid1/config) to enable IBD check. Inform customer that IBD Check is a time consuming process and no ETA can be provided. 
7. Start the services. The file system check will be triggered and once finished, the services and the store will come online. (From admin cli do serviceset start all)

[Mohamed_I]

Hi TheSeeker,
Good day, We have storence  G3 and G4 units and G4+
For G3 you can log in to cli , For G4 only HPE engineer will have access.
For G4 you need to log a case with HPE support and our engineer will generate Temp Root password and will check the status.

Thank you. HPE Community team.

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.