HANA One Instance not running

[Former Member]

Hi all,

We recently launched an SAP HANA One instance, but unable to start it using ./HDB start.

When looking at the lnameserver ogs we see the /hanadata mount was not found:

hanaserver:/usr/sap/HDB/SYS/exe/hdb> ./hdbnameserver
unclean shutdown of service instance with pid 50730.
service startup...
accepting requests at *:30001
service started
searching for master nameserver hanaserver:30001 ...
assign as master nameserver. assign to volume 1 started
checking for recovery request ...
loading topology ...
persistence does not exist @ /hanadata/HDB/data/mnt00001/hdb00001/

persistence initialization failed -> stopping instance ...
cannot send signal. (2, No such file or directory)
prepare for shutting service down...
stop ClockMonitor thread...

Here is a list of the mounts I see, normally you should see a /hanadata mount as well:

hanaserver:/usr/sap/HDB/SYS/exe/hdb> df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 9.9G 2.7G 6.8G 29% /
devtmpfs 30G 128K 30G 1% /dev
tmpfs 30G 0 30G 0% /dev/shm
/dev/md0 119G 2.5G 110G 3% /hanalog
/dev/xvdj 60G 11G 46G 19% /usr/sap

The HANA One that we are using is standard package from Amazon; It is the latest SAP HANA One revision 52.1 package.  We don’t have exposure to the H/W vendor or any install / config at the H/W or O/S level, so please assist with what could have gone wrong during the instance deployment.  Is it advisable to delete the instance, and re-launch?  Or is there something we missed since this was a standard AWS Image?

Thanks for any advice!

[Former Member]

Hello,

Suggestion is to terminate this instance and start new instance.

Usually, this means that volumes did not get created in AWS.

thanks,

Dhruman

[Former Member]

Hi Dhurman,

Is there a reason for why the volumes did not get created?  If we go through the procedure again, will they get created? Or is there some steps we are missing when launching the instance?

Thanks.

[Former Member]

Hello,

This is a rare aws problem.

Creating a new instance should resolve the issue.

There is nothing missing.

thanks,

dhruman