5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
@JohanITG It looks like you are trying to repair the host boot disk not the CVM boot disk. You need to select the replaced drive in the UI and then you will see the Repair boot disk option. This option is for repairing CVM boot disk.
@JohanITG Looks like the disk is not detected as failed, there is an ID for the disk which means the system knows about the disk already. Did you replace the disk or just re-seat it?
@JohanITG I believe the failure is due to partition detected on the SSD. In the same screen please run the following commands, lscssi # the above command will list the drives detected, find the ssd drive and look for the device name like sda,sdb fdisk -l <device_name_from_above_command> If you see a partition listed delete the partition by following the article below, https://www.cyberciti.biz/faq/linux-how-to-delete-a-partition-with-fdisk-command/ After all partitions are deleted on the drive, run the following command to start phoenix again phoenix/phoenix
@JohanITG not required to choose the hypervisor. What option did you choose in phoenix prompt? The CVM is installed in Vmware using a process called Configure Hypervisor. Did you just try Install cvm?
@JohanITG can you run the following command on the Esxi host? ls -la /bootbank/Nutanix/firstboot/*firstboot*
ok i see an .firstboot_fail marker file which means the firstboot scripts failed. Can you check first_boot.log to see where is the failure?
The failure will be above those lines, please send me the logs as private message.
@JohanITG can you check if the lsi controller is marked as passthru for the CVM? You can compare it with working cvm vmx file or settings
Can you mount the Phoenix is again and when it prompts for installation just select cancel. It will take you to Shell. In the Shell run fdisk -l /dev/sd? Confirm there is 4 partitions on the ssd, mount the first two partitions of the ssd and then do an ls -la on the mount point. By the way is the replacement ssd same model as the ssd on other nodes?
ok that’s seems to be the problem. The SSD model detected is unsupported for boot drive. We have a list of supported SSDs to be used for boot drive and i can’t find this model in the list. I’m not able to see any Western digital drives in our supported list.
We don’t support ignoring the compatibility list since this node with an unqualified ssd can cause performance issues to other nodes. Also in the initial picture you shared with us the model says Intel SSD. Was it the old drive? Your sales engineer should be able to provide you the list of supported SSDs
@pso9968 Have you also removed disk_size_bytes and disk_size_mib from the CDROM spec? It works for me.
Here is curl and jq combo that works in unmounting the cd rom for a single cdrom attached vm. url='https://<pc_ip>:9440/api/nutanix/v3/vms/<vm_uuid>'curl -k -s -u admin "$url" | jq 'del(.status)|del(.spec.resources.disk_list[]|select(.device_properties.device_type == "CDROM") | .data_source_reference,.disk_size_bytes,.disk_size_mib)' | curl -k -s -u admin "$url" -H "Content-type:application/json" -XPUT -d @- Replace pc_ip and vm_uuid with appropriate values
@SeanLittle In the powershell script you can ignore the -Credential since the header you are passing has the basic authorization info. The following script works for me add-type @" using System.Net; using System.Security.Cryptography.X509Certificates; public class TrustAllCertsPolicy : ICertificatePolicy { public bool CheckValidationResult( ServicePoint srvPoint, X509Certificate certificate, WebRequest request, int certificateProblem) { return true; } }"@[System.Net.ServicePointManager]::CertificatePolicy = New-Object TrustAllCertsPolicy[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12$cred = Get-Credential$header = @{"Authorization" = "Basic "+[System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes($cred.UserName+":"+$cred.GetNetworkCredential().Password))}$url = "https://<pc_ip>:9440/api/nutanix/v3/vms/list"$data = "{}"$response = Invoke-RestMethod $url -Method POST -Body $data -Headers $header -ContentType "application/json"
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.