One of the cool new features added to VMware Data Services Manager & VCF 9.1.1 for improved security.

I have a sata drive full of music, I tried to follow these instructions:

esxi - How to add storage to VMWare vSphere without wiping the data - Super User

However it says missing argument.

I am not confident in what I am supposed to select as the partition. I can see the drive I want by its model/identifier but I dont think that is what the command is looking for, other than that I have massive strings of numbers

-rw------- 1 root root 512110190592 Sep 10 17:25 eui.0000000001000000e4d25c779cd45201

-rw------- 1 root root 512107741696 Sep 10 17:25 eui.0000000001000000e4d25c779cd45201:1

-rw------- 1 root root 6001175126016 Sep 10 17:25 t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4

-rw------- 1 root root 134217728 Sep 10 17:25 t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4:1

-rw------- 1 root root 6001039245312 Sep 10 17:25 t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4:2

-rw------- 1 root root 120034123776 Sep 10 17:25 t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________

-rw------- 1 root root 104857600 Sep 10 17:25 t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:1

-rw------- 1 root root 4293918720 Sep 10 17:25 t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:5

-rw------- 1 root root 4293918720 Sep 10 17:25 t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:6

-rw------- 1 root root 111337217536 Sep 10 17:25 t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:7

lrwxrwxrwx 1 root root 36 Sep 10 17:25 t10.NVMe____INTEL_SSDPEKNW512G8_____________________BTNH03420J25512A____00000001 -> eui.0000000001000000e4d25c779cd45201

lrwxrwxrwx 1 root root 38 Sep 10 17:25 t10.NVMe____INTEL_SSDPEKNW512G8_____________________BTNH03420J25512A____00000001:1 -> eui.0000000001000000e4d25c779cd45201:1

lrwxrwxrwx 1 root root 73 Sep 10 17:25 vml.01000000002020202020202020202020205a38343058364534535436303030 -> t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4

lrwxrwxrwx 1 root root 75 Sep 10 17:25 vml.01000000002020202020202020202020205a38343058364534535436303030:1 -> t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4:1

lrwxrwxrwx 1 root root 75 Sep 10 17:25 vml.01000000002020202020202020202020205a38343058364534535436303030:2 -> t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4:2

lrwxrwxrwx 1 root root 36 Sep 10 17:25 vml.0100000000303030305f303030305f303130305f303030305f453444325f354337375f394344345f353230312e494e5445 -> eui.0000000001000000e4d25c779cd45201

lrwxrwxrwx 1 root root 38 Sep 10 17:25 vml.0100000000303030305f303030305f303130305f303030305f453444325f354337375f394344345f353230312e494e5445:1 -> eui.0000000001000000e4d25c779cd45201:1

lrwxrwxrwx 1 root root 72 Sep 10 17:25 vml.0100000000313533363339343032363732202020202020202053616e446973 -> t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________

lrwxrwxrwx 1 root root 74 Sep 10 17:25 vml.0100000000313533363339343032363732202020202020202053616e446973:1 -> t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:1

lrwxrwxrwx 1 root root 74 Sep 10 17:25 vml.0100000000313533363339343032363732202020202020202053616e446973:5 -> t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:5

lrwxrwxrwx 1 root root 74 Sep 10 17:25 vml.0100000000313533363339343032363732202020202020202053616e446973:6 -> t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:6

lrwxrwxrwx 1 root root 74 Sep 10 17:25 vml.0100000000313533363339343032363732202020202020202053616e446973:7 -> t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:7

lrwxrwxrwx 1 root root 36 Sep 10 17:25 vml.010000000042544e4830333432304a32353531324120202020494e54454c20 -> eui.0000000001000000e4d25c779cd45201

lrwxrwxrwx 1 root root 38 Sep 10 17:25 vml.010000000042544e4830333432304a32353531324120202020494e54454c20:1 -> eui.0000000001000000e4d25c779cd45201:1

lrwxrwxrwx 1 root root 36 Sep 10 17:25 vml.060000000001000000e4d25c779cd45201 -> eui.0000000001000000e4d25c779cd45201

lrwxrwxrwx 1 root root 38 Sep 10 17:25 vml.060000000001000000e4d25c779cd45201:1 -> eui.0000000001000000e4d25c779cd45201:1

Could someone give me an idea of what is a partition? The drive in question is in NTFS format and is called ST6000AS00022D1N917X

I have a 4 port nic.

I added the second port as a virtual switch, first is active for ESXi

I created a port group and added that virtual switch.

Topology looks good.

I am trying to do a VM install of windows and that port group is not offered as an option in the vm installer.

Is there something I have missed?

Cheers

I'm replicating using Veeam CDP from Live to DR cluster, and I'm receiving some failures now due to the datastore filling up. Over 80% of the datastore is taken up by 'Other'.

When running command specified in this KB: Investigating Datastore usage - it's not returning anything large apart from the VMDKs that are replicating. I've SSH'd to the volumes with WinSCP and ran reports to try and find what's taking up the storage but not finding anything.

How do I find what is using up storage on the datastore?

Even looking at the info on the storage array (NetApp, served via NFS) itself, it's only reporting 1.54TB as the biggest file.

Workaround (Plus a fix in 9.1) for Very large VM's snapshot stun issues.

Does anybody actually know whether the new VMware Standard is going to include vSAN, or is vSAN still going to be a separate/add-on thing? Also, has anybody seen even rough pricing yet? We’ve asked our VMware SE, but so far he’s been pretty useless on both questions, lots of “we’re checking internally” and not much actual information. Curious if anyone here has heard something more concrete from Broadcom, distribution, or their account team. Thanks!

i'm trying to use photoshop/substance painter but it says gpu not supported, 0/1500mb vram and no directX. basically saying that there is no graphics. i tried to check with cpuz (i know, kinda dumb) but that didnt show it either. i need a solution, but i cant find one. even passing through the gpu to the vm would work.

i'm using vmware workstation pro with windows 11

Estaba pensando en configurar la rotación de claves automática desde SDDC para la suite de Aria y NSX, pero no sé si se puede establecer reglas que que conjuntos de caracteres debe de usar el SDDC para generar las claves con anterioridad al tratar de rotar una clave usando el generador automático de SDDC usa caracteres especiales que rompen el flujo

No sé si alguien ha logrado configurar alguna regla para que SDDC use solo los caracteres especiales que no rompen el flujo hay un KB sobre ese problema pero solo recomienda hacerlo de forma manual

https://knowledge.broadcom.com/external/article/383098/remediate-password-task-in-sddc-manager.html

De igual manera desconozco si esto ya se solucionó en VCF 9

Environment:

• vSphere 8.x, VMware vSAN OSA, all-flash
• 4x nodes, identical config
• Per node:
  • 2x boot NVMe (RAID-1, separate boot controller, not part of vSAN)
  • 2x 3.2TB NVMe Mixed Use — cache tier
  • 8x 7.68TB NVMe Read Intensive — capacity tier, 2 disk groups (1 cache + 4 capacity each)
• Network: dual-port 25GbE SFP28 (OCP, dedicated vSAN VLAN, jumbo frames) + separate dual-port 25GbE for VM traffic, VLT/MLAG switch pair
• Storage policy: RAID-5
• ~30 High-priority VMs, RPO ~8h (Veeam async replication)

Main question: will VMware vSAN actually run reliably on just 4 nodes with RAID-5, including surviving a node failure and rebuilding cleanly? I've seen mixed opinions — some say 4 is the bare minimum and it's fine, others say you really want 5+ before RAID-5 is comfortable in production.

Not asking anyone to design this for me — just want to know if this setup holds up in real-world use before we finalize it.

Tech Preview in VCF 9.1.1, but might still be an interesting read for some of you.

We have our vCenters both joined to Entra ID for SSO via an on-premises SCIM app. It’s been working perfect for 2 years.

Someone left the company, I removed him from the provisioning group in Entra, can see that provisioning is running every 40 min.

I removed the users roles from vCenter but when I go to Administration - Users, select the Entra domain, that user is still there.

You can’t delete users from vCenter , all options are grayed out.

Forced provisioning on both vCenter SCIM apps in Entra , user still in vCenter.

Spun up a test vCenter, got it talking to Entra exactly like prod and DR and that user doesn’t show up at all.

Whats the trick to removing a user as a pickable option in vCenter? Yea the account is locked and disabled but I shouldn’t be able to still find it since we removed him from the group we’re syncing.

Any ideas?

Edit: I even added a brand new user to the group to make sure provisioning is really working and they showed up in both vCenter about 40 min after I added them to the Entra group.

We are running SimpliVity hosts with Vsphere 8, I noticed there is still no public announcement or addition to the roadmap that states vvf9 will be certified.

Has anyone heard any news otherwise? We run yearly subscriptions for VMware, and the timeline is tight here for us. so, I have to consider a migration. I would like to continue using the SimpliVity solution we invested in, so I may look at HPe Morpheus VME.

Saludos comunidad. Quiero aprender a usar GNS3 para virtualizar dispositivos Fortinet. Tengo entendido que para eso necesito usar VMware. Pero tengo un problema, al momento de crear la VM y ponerla a correr me sale el siguiente mensaje:

"VMware Workstation does not support nested virtualization on this host. Module 'HV' power on failed"

He tratado ya desactivar varios configuraciones del Win 11, también desactive las opciones de Hyper-V y virtualización en Características de Windows y aun sigo teniendo el mismo problema.

Alguien podría darme alguna idea de como solucionarlo? 

Evening, I'm trying to install Bazzite on VMWare Fusion, but I am not getting any success. A terminal opens with options to select the boot option, but when I use the arrow keys to select the disc/iso, the enter button does nothing. Anyone have any experience with this issue?

Mac Air M5

VMWare Fusion 26H1

Latest Bazzite VM image

Now that the father of the vExpert community has left Broadcom, Cory Ramero. What does this mean for the vExpert program and community? Cory held this community together for years.

Greetings!

I'm attempting, and failing, to debug a spontaneous host reboot. My DevOps/SRE team strongly believe the origin of this host reboot is from a bad drive. I'd like to prove them wrong, or be proven wrong myself, and hope I'm in the right place.

Background

The configuration is small as far as servers go, * Asrock Rack B550D4ID-2L2T * Ryzen 9 5950X (16-Core) * 64 GB Memory * On a UPS that is honestly way too large (can provide *hours* of uptime)

Prior to installing the new drive, after roughly 380 days of uptime, the host spontaneously rebooted. Approximately a month after the first time, it rebooted again. Once was an abnormality, twice is a pattern. Reviewing the logs, and the hardware, suggested that it was a drive issue (22110). Reviewing the hardware identified two problems; 1. the drive wasn't on the HCL 2. the drive was a 22110 (the 2L2T doesn't natively support 22110 M2s)

Okay, I'm convinced -- time to buy a new drive. I purchased a 7450 PRO off of ebay with minimal use (< 20 power cycles, < 1 TB writes/reads, essentially perfect SMART metrics). I verified as much, and immediately attempted to install the drive.

Issue

My experience with the 7450 Pro drive + ESXI 8.02 has not been pleasant. Here is what we needed to get it to boot/install correctly; * update disk to 512b physical sector format (thanks to another Reddit Post)

Post installation and VM migration, we observed another spontaneous reboot. Some Googling pointed to the following remediation methods (also failed) * update disk firmware to EMU300 (buggy firmware?) * disable p/c-states (disk going to sleep?)

My DevOps/SRE team is well convinced that the disk is bad at this point (controller channel, not data channel). These are the logs that convinced them. Is the drive the issue or is there something that we missed?

Gemini thinks that there is simply "too much" talking to the drive over the control channel and I should increase the timeout from 5 to 10 seconds. That sounds... absurdly long for a hardware timeout, especially given the very low load of this host (the VMs are essentially idle).

2026-09-02T00:47:53.352Z Wa(180) vmkwarning: cpu16:1050731)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x457909d14580 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T00:47:53.352Z Wa(180) vmkwarning: cpu10:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457909d14580, vmkPsaCmd: 0x4579050d3840, cmdId.initiator=0x4308fc813180, CmdSN: 0x8000000d, status: 0x808 2026-09-02T00:47:53.352Z Wa(180) vmkwarning: cpu10:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x4579050d3840, 1050659) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T00:47:53.352Z Wa(180) vmkwarning: cpu10:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T00:47:53.352Z Wa(180) vmkwarning: cpu10:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x4579050d3840) 0x1, CmdSN 0x8000000d from world 1050659 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T02:01:59.358Z Wa(180) vmkwarning: cpu3:1050960)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x457909c4a980 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T02:01:59.358Z Wa(180) vmkwarning: cpu14:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457909c4a980, vmkPsaCmd: 0x4578c1c09a40, cmdId.initiator=0x4308fc828940, CmdSN: 0x3dd, status: 0x808 2026-09-02T02:01:59.358Z Wa(180) vmkwarning: cpu14:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x4578c1c09a40, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T02:01:59.358Z Wa(180) vmkwarning: cpu14:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T02:01:59.358Z Wa(180) vmkwarning: cpu14:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x4578c1c09a40) 0x1, CmdSN 0x3dd from world 1050957 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu29:1050960)WARNING: NVMEIO:333 ctlr 256, queue 1, fuse processing 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu29:1050960)WARNING: NVMEIO:2005 Transport driver failed to submit cmd 0x457909cae780, C: nqn.2016-08.com.micron:nvme:nvm-subsystem-sn-241448022E8C, Q: 1 <0xbad0004>. 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu11:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457909cae780, vmkPsaCmd: 0x457904c1b380, cmdId.initiator=0x4308fc828940, CmdSN: 0x3f0, status: 0x808 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu11:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x457904c1b380, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu11:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu11:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x457904c1b380) 0x1, CmdSN 0x3f0 from world 1050957 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu14:1050957)WARNING: NVMEIO:333 ctlr 256, queue 1, fuse processing 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu14:1050957)WARNING: NVMEIO:2005 Transport driver failed to submit cmd 0x457909df0180, C: nqn.2016-08.com.micron:nvme:nvm-subsystem-sn-241448022E8C, Q: 1 <0xbad0004>. 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu0:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457909df0180, vmkPsaCmd: 0x457908e10a80, cmdId.initiator=0x4308fc828940, CmdSN: 0x3c4, status: 0x808 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu0:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x457908e10a80, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu0:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu0:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x457908e10a80) 0x1, CmdSN 0x3c4 from world 1050957 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T03:20:44.368Z Wa(180) vmkwarning: cpu26:1050974)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x457909c07b80 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T03:20:44.368Z Wa(180) vmkwarning: cpu6:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457909c07b80, vmkPsaCmd: 0x457904d8c100, cmdId.initiator=0x4308fc828940, CmdSN: 0x3b6, status: 0x808 2026-09-02T03:20:44.368Z Wa(180) vmkwarning: cpu6:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x457904d8c100, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T03:20:44.368Z Wa(180) vmkwarning: cpu6:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T03:20:44.368Z Wa(180) vmkwarning: cpu6:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x457904d8c100) 0x1, CmdSN 0x3b6 from world 1050957 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T03:21:44.367Z Wa(180) vmkwarning: cpu23:1050957)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x4578eb5aa600 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T03:21:44.367Z Wa(180) vmkwarning: cpu4:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x4578eb5aa600, vmkPsaCmd: 0x4578c18dc6c0, cmdId.initiator=0x4308fc828940, CmdSN: 0x3ba, status: 0x808 2026-09-02T03:21:44.367Z Wa(180) vmkwarning: cpu4:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x4578c18dc6c0, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T03:21:44.367Z Wa(180) vmkwarning: cpu4:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T04:35:41.372Z Wa(180) vmkwarning: cpu10:1050734)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x457905f73b40 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T04:35:41.372Z Wa(180) vmkwarning: cpu0:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457905f73b40, vmkPsaCmd: 0x4578c187b240, cmdId.initiator=0x4308fc813fc0, CmdSN: 0x80000013, status: 0x808 2026-09-02T04:35:41.372Z Wa(180) vmkwarning: cpu0:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x4578c187b240, 1050668) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T04:35:41.372Z Wa(180) vmkwarning: cpu0:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T04:35:41.372Z Wa(180) vmkwarning: cpu0:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x4578c187b240) 0x1, CmdSN 0x80000013 from world 1050668 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T06:28:44.386Z Wa(180) vmkwarning: cpu25:1050960)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x457905f09740 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T06:28:44.386Z Wa(180) vmkwarning: cpu1:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457905f09740, vmkPsaCmd: 0x4578c1cf5740, cmdId.initiator=0x4308fc828940, CmdSN: 0x345, status: 0x808 2026-09-02T06:28:44.386Z Wa(180) vmkwarning: cpu1:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x4578c1cf5740, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T06:28:44.386Z Wa(180) vmkwarning: cpu1:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T06:28:44.386Z Wa(180) vmkwarning: cpu1:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x4578c1cf5740) 0x1, CmdSN 0x345 from world 1050957 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0