Hello Apidesh,

the system most likely encountered a power outage and did automatically "Rescue Node" on both nodes so only manual T3 can help in this situation. You can check under in Service GUI under "Collect logs" if there is a file which is called something like "rescuelogs". if yes, then only Manual T3 can help to retrieve the data on system.

Hello Hammad.

Could you please tell me where I can find Manual T3 procedure, or maybe you could write to me? 

Thanks.

Hello Apidesh,

the system most likely encountered a power outage and did automatically "Rescue Node" on both nodes so only manual T3 can help in this situation. You can check under in Service GUI under "Collect logs" if there is a file which is called something like "rescuelogs". if yes, then only Manual T3 can help to retrieve the data on system.

Hello Zlatko,

manual T3 recovery should be done by IBM support. We need create a sacrificial cluster. Save a config file and delete that cluster again. Then we need to scan all drives per CLI to find the quorum drives. After we identify the drive which contain the latest quorum information, we can dump the information from that drive and then rebuild the cluster. If you have an old config file, at the end we can transfer that file to the node and prepare/execute that file so it rename all vdisks/mdisks and hosts and create call home setting, volume parameters,,all exactly as before.

So i would highly recommend to contact IBM Support so they will guide you to recover the system.

Best regards, Mousa

Hello Hammad.

Could you please tell me where I can find Manual T3 procedure, or maybe you could write to me? 

Thanks.

Hello Apidesh,

the system most likely encountered a power outage and did automatically "Rescue Node" on both nodes so only manual T3 can help in this situation. You can check under in Service GUI under "Collect logs" if there is a file which is called something like "rescuelogs". if yes, then only Manual T3 can help to retrieve the data on system.

Hello Zlatko,

the procedure you found on lenovo website refering to T4 recovery and not T3 which means you recover the config but without the data. regarding your question, if you want to reset the Cluster ID, please try to do that via SSH using the command:

satask chenclosurevpd -resetclusterid

Best regards; mousa

Hello Zlatko,

manual T3 recovery should be done by IBM support. We need create a sacrificial cluster. Save a config file and delete that cluster again. Then we need to scan all drives per CLI to find the quorum drives. After we identify the drive which contain the latest quorum information, we can dump the information from that drive and then rebuild the cluster. If you have an old config file, at the end we can transfer that file to the node and prepare/execute that file so it rename all vdisks/mdisks and hosts and create call home setting, volume parameters,,all exactly as before.

So i would highly recommend to contact IBM Support so they will guide you to recover the system.

Best regards, Mousa

Hello Hammad.

Could you please tell me where I can find Manual T3 procedure, or maybe you could write to me? 

Thanks.

Hello Apidesh,

the system most likely encountered a power outage and did automatically "Rescue Node" on both nodes so only manual T3 can help in this situation. You can check under in Service GUI under "Collect logs" if there is a file which is called something like "rescuelogs". if yes, then only Manual T3 can help to retrieve the data on system.