Solved

Single Node Cluster SATADOM Repair

  • 15 September 2022
  • 4 replies
  • 659 views
V

Is it possible to recover single node cluster after SATADOM crash? How can I reimage it?

icon

Best answer by Vyacheslav 19 September 2022, 08:26

View original
This topic has been closed for comments

4 replies

Moustafa Hindawi
Userlevel 5
Badge +6

Hello,

This KB would help

https://portal.nutanix.com/page/documents/kbs/details?targetId=kA03200000098YlCAI (support portal login required)

Moustafa Hindawi | Blogger | Nutanix Technology Champion | NCSE | NCM-MCI | VMCE | 2xVCAP-DTM & DCV | 2xVCP-NV & CMA | LinkedIn: https://www.linkedin.com/in/moustafaadelmoustafa/ | My Blog: https://cloudwhales.co.uk/author/mhindawi/
V

Thanks, but I don’t have access

V

I have recovered crashed cluster, special thanks to Alexander (@Kargozia).


recovery instructions:

  1. deploy single node nutanix ce cluster on the same hardware, get boot device img
  2. write boot device img to ssd (do not use usb flash for boot), boot crashed single node cluster from this ssd
  3. fix AHV network settings (fix ifcfg scripts, fix open vswitch bridge). Make sure the network is working and you have ssh access to AHV
  4. fix CVM xml config (/etc/libvirt/qemu/NTNX-xxx-CVM.xml). You need to fix block devices info (all info in tags <disk device="disk" type="block">, fix count of disks and their id’s).
    Disk info:
    - lsblk
    - ls -la /dev/disk/by-id/
    - udevadm info --query=all --name=/dev/sdx
  5. Reload changes - virsh define /etc/libvirt/qemu/NTNX-xxx-CVM.xml. Boot CVM, make sure you have ssh access to CVM (192.168.5.2)
  6. Get ssh access to CVM, fix open vswitch uplinks.
  7. Exec genesis start from CVM, check that everything is ok (if not - just read the logs and fix something)
  8. Create boot device backup
V

Keep in mind that for some reason nutanix installer truncate disk serial number (tag <serial></serial> in CVM xml config) to 16 characters.

Terms & Conditions