Question

Creating Nutanix Cluster using Hyperflex M5 Server Failed

  • 18 April 2024
  • 5 replies
  • 59 views

Im trying to install nutanix on Cisco Hyperflex M5 Server and  I get the following errors.

Has anyone experienced this and how to solve it?

2024-04-17 05:23:04,932Z INFO installation_device: -drive file=/dev/sdj,cache=writethrough,format=raw
2024-04-17 05:23:04,959Z DEBUG Using AHV-metadata iso for AHV installation
2024-04-17 05:23:04,966Z INFO Executing /usr/bin/qemu-system-x86_64 -m 32G -machine q35 -enable-kvm -drive file=/dev/sdj,cache=writethrough,format=raw -drive file=/phoenix/imaging_helper/installer.iso,media=cdrom -netdev user,id=net0,net=192.168.5.0/24 -device e1000,netdev=net0,id=net0,mac=00:25:b5:a0:f3:01 -vnc :1 -boot order=d -pidfile installer_vm.pid -daemonize -smp 4 -serial file:/tmp/installer_vm.log -drive file=/phoenix/imaging_helper/installer.iso-meta.iso,media=cdrom
2024-04-17 05:23:05,074Z INFO Installer VM is now running the installation
2024-04-17 05:23:05,082Z INFO Installer VM running with PID = 5172
2024-04-17 05:23:05,105Z DEBUG svm_rescue:
Unable to read /etc/nutanix/release_version: [Errno 2] No such file or directory: '/etc/nutanix/release_version'
2024-04-17 05:41:02,172Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,182Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,182Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,183Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,183Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,183Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,184Z CRITICAL svm_rescue:914 No suitable SVM boot disk found.
2024-04-17 05:41:02,184Z INFO svm_rescue:117 exec_cmd: sync; sync; sync
2024-04-17 05:41:02,197Z INFO svm_rescue:117 exec_cmd: umount -R /mnt/disk
2024-04-17 05:41:02,205Z INFO svm_rescue:117 exec_cmd: umount -R /mnt/data
2024-04-17 05:23:05,118Z INFO Output of lsblk command.
 NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sdd    8:48   0 894.3G  0 disk 
sde    8:64   0 894.3G  0 disk 
sdf    8:80   0 894.3G  0 disk 
sdg    8:96   0 894.3G  0 disk 
sdh    8:112  0 894.3G  0 disk 
sdi    8:128  0 894.3G  0 disk 
sdj    8:144  0 223.6G  0 disk
2024-04-17 05:23:05,130Z INFO Output of mdstat command.
 Personalities : [raid1] 
unused devices: <none>
2024-04-17 05:23:05,139Z ERROR SVM rescue failed with reason [Unable to read /etc/nutanix/release_version: [Errno 2] No such file or directory: '/etc/nutanix/release_version'
2024-04-17 05:41:02,172Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,182Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,182Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,183Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,183Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,183Z ERROR layout.py:46 Failed to parse factory_config.json:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/util/hardware/layout.py", line 40, in should_use_layout
IOError: [Errno 2] No such file or directory: '/etc/nutanix/factory_config.json'
2024-04-17 05:41:02,184Z CRITICAL svm_rescue:914 No suitable SVM boot disk found.
2024-04-17 05:41:02,184Z INFO svm_rescue:117 exec_cmd: sync; sync; sync
2024-04-17 05:41:02,197Z INFO svm_rescue:117 exec_cmd: umount -R /mnt/disk
2024-04-17 05:41:02,205Z INFO svm_rescue:117 exec_cmd: umount -R /mnt/data]
2024-04-17 05:23:05,147Z INFO Imaging thread 'svm' failed with reason [None]
2024-04-17 05:23:05,155Z CRITICAL Imaging thread 'svm' failed with reason [None]
2024-04-17 05:23:05,269Z ERROR Exception in running <InstallHypervisorKVM(<NodeConfig(192.200.110.121) @ae50>) @33a0>
Traceback (most recent call last):
  File "foundation/imaging_step.py", line 160, in _run
  File "foundation/imaging_step_hypervisor.py", line 47, in run
  File "foundation/imaging_step.py", line 349, in wait_for_event
Exception: Received "fatal" in waiting for event "Installing AHV": Imaging thread 'svm' failed with reason [None]
2024-04-17 05:23:05,269Z DEBUG Setting state of <InstallHypervisorKVM(<NodeConfig(192.200.110.121) @ae50>) @33a0> from RUNNING to FAILED
2024-04-17 05:23:05,612Z ERROR Exception in <ImagingStepPhoenix(<NodeConfig(192.200.110.121) @ae50>) @32b0>
Traceback (most recent call last):
  File "foundation/decorators.py", line 78, in wrap_method
  File "foundation/imaging_step_phoenix.py", line 537, in run
  File "foundation/imaging_step.py", line 349, in wait_for_event
Exception: Received "fatal" in waiting for event "Rebooting node. This may take several minutes": Imaging thread 'svm' failed with reason [None]
2024-04-17 05:23:05,628Z ERROR Exception in running <ImagingStepPhoenix(<NodeConfig(192.200.110.121) @ae50>) @32b0>
Traceback (most recent call last):
  File "foundation/imaging_step.py", line 160, in _run
  File "foundation/decorators.py", line 78, in wrap_method
  File "foundation/imaging_step_phoenix.py", line 537, in run
  File "foundation/imaging_step.py", line 349, in wait_for_event
 

 


5 replies

Badge +1

What model Hyperflex?  Have you validated it will support?

Using HXC240-M5SX, yep already checked on compatibility matrix and successfully install on another cluster with the same type and spec of the node

 

actually i try with 2 cluster (1 cluster with 3 node hxc240-m5sx) all same spec 

lets say Cluster A deployed sucessfully without any issue at all but the another cluster hv an issue like my posting above and im new with nutanix still dont know how to solve or throubleshoot the issue

please help/ advice for get the clue thanks 

 

Badge +1

Have you validated that the internal components are all the same?  Like is there a difference in disks, disk firmware, etc that would make it not install?  Otherwise if it works on some but not others, I’d open a support case

Hi Bcrill,

not all spec meet with whats on document. like HDD and Memory

My disk : 6x 960GB UCS-SD960G61X-EV (with type not in list compatibility matrix) 

M.2 Disk (boot) : 1x240 Gb UCS-M2-240GB

Memory : 6x 32 Gb (UCS-MR-X32G2RT-H)

The others is same, and firmware adusted with recommended version from nutanix documentation

refference :

https://portal.nutanix.com/page/documents/details?targetId=Cisco-UCS-Hardware-Firmware-Compatibility:Cisco-UCS-Hardware-Firmware-Compatibility

 

is it because of the disk not in compatibility matrix?

Badge +1

I can’t say for sure but I would be willing to bet that yes without the disks on the compatibility list the installer doesn’t know how to handle everything

Reply