VMware Cloud Community
DDim
Enthusiast
Enthusiast
Jump to solution

SSD raid1 volume - Device: No associated device

Hello,

I am sucessfuly start ESXI 7.0 with Intel RMSP3AD160F hardware RAID controller.

Esxi installed on RAID1 (2 Intel 2Tb NVMe SSD in mirror)

I have a problem when install additional RAID1 volume (two 4Tb NVMe SSD  WD Ultrastar DC SN640 WUS4BB038D7P3E1)

Volume created sucessfuly, I see storage path  in esxcli storage core path list output, but datastore not mounted.

How I can mount new volume in esxi?

Thank you!

[root@localhost:~] esxcli storage core path list

  1. sas.500062b2024d7780-sas.60184a83be394524-

   UID: sas.500062b2024d7780-sas.60184a83be394524-

Runtime Name: vmhba1:C2:T1:L0

   Device: No associated device

   Device Display Name: No associated device

Adapter: vmhba1

   Channel: 2

Target: 1

   LUN: 0

Plugin: NMP

   State: active

Transport: sas

Adapter Identifier: sas.500062b2024d7780

   Target Identifier: sas.60184a83be394524

Adapter Transport Details: 500062b2024d7780

   Target Transport Details: 60184a83be394524

Maximum IO Size: 131072

  1. sas.500062b2024d7780-sas.60b45827b8d55460-naa.600062b2024d778026b45827b8d55460

   UID: sas.500062b2024d7780-sas.60b45827b8d55460-naa.600062b2024d778026b45827b8d55460

Runtime Name: vmhba1:C2:T0:L0

Device: naa.600062b2024d778026b45827b8d55460

   Device Display Name: Local Intel Disk (naa.600062b2024d778026b45827b8d55460)

Adapter: vmhba1

   Channel: 2

Target: 0

   LUN: 0

Plugin: NMP

   State: active

Transport: sas

Adapter Identifier: sas.500062b2024d7780

   Target Identifier: sas.60b45827b8d55460

Adapter Transport Details: 500062b2024d7780

   Target Transport Details: 60b45827b8d55460

   Maximum IO Size: 131072

Reply
0 Kudos
1 Solution

Accepted Solutions
DDim
Enthusiast
Enthusiast
Jump to solution

Thank you, but rescan did not solve the problem.

Now I solve this problem!

I delete VD via storcli, connect drives to Linux desktop via u.2 -> PCIe adapter and reformat SSD to 512e physical sector!

pastedImage_0.png

On Linux desktop ---

# physical sector configuration list

nvme id-ns -H /dev/nvmeXnY

# Reformat

nvme format --lbaf=<number> /dev/nvmeXnY

Then connect to server and create VD

/opt/lsi/storcli/storcli /c0 add vd type=raid1 drives=74:26-27 names=4tb wt

/opt/lsi/storcli/storcli /c0 /v1 start init full

View solution in original post

Reply
0 Kudos
3 Replies
DDim
Enthusiast
Enthusiast
Jump to solution

UPD - when I check  adapter  ->  path

I see this volume, but I can't see them via Adapter - >Devices

Problematic volume has 4k disk sector size.

pastedImage_0.png

Reply
0 Kudos
nachogonzalez
Commander
Commander
Jump to solution

Hey, hope you are doing fine:

Have you tried a rescan of the storage?

VMware Knowledge Base

Reply
0 Kudos
DDim
Enthusiast
Enthusiast
Jump to solution

Thank you, but rescan did not solve the problem.

Now I solve this problem!

I delete VD via storcli, connect drives to Linux desktop via u.2 -> PCIe adapter and reformat SSD to 512e physical sector!

pastedImage_0.png

On Linux desktop ---

# physical sector configuration list

nvme id-ns -H /dev/nvmeXnY

# Reformat

nvme format --lbaf=<number> /dev/nvmeXnY

Then connect to server and create VD

/opt/lsi/storcli/storcli /c0 add vd type=raid1 drives=74:26-27 names=4tb wt

/opt/lsi/storcli/storcli /c0 /v1 start init full

Reply
0 Kudos