A user reports that their Micron 7450 Pro NVMe drive is generating numerous errors and is the primary suspect for causing spontaneous host reboots in a VMware ESXi 8.02 environment.

{
  "signal_id": "174ccf7a-fff7-56ea-a6d1-a51b227af328",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-09-05T03:59:11+00:00",
  "company": {
    "name": "Micron",
    "domain": "micron.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "in_progress",
    "topics": [
      "nvme",
      "ssd",
      "reliability",
      "firmware",
      "hardware compatibility"
    ],
    "post_id": "1w7q0o2",
    "summary": "A user reports that their Micron 7450 Pro NVMe drive is generating numerous errors and is the primary suspect for causing spontaneous host reboots in a VMware ESXi 8.02 environment.",
    "category": "integration",
    "comments": [
      {
        "url": "https://www.reddit.com/r/vmware/comments/1w7q0o2/comment/p87hjbg/",
        "depth": 0,
        "score": 2,
        "author": "SGalbincea",
        "excerpt": "None of this hardware is on (or ever was on) the HCL, and those NVMe errors are typical of unsupported driver/firmware combinations.\n\n If this is for anything other than a non-prod lab, it's time to get supported hardware my friend.",
        "posted_at": "2026-09-06T18:22:10.000Z",
        "author_url": "https://www.reddit.com/user/SGalbincea/"
      },
      {
        "url": "https://www.reddit.com/r/vmware/comments/1w7q0o2/comment/p7wycs3/",
        "depth": 0,
        "score": 1,
        "author": "Kokotewa",
        "excerpt": "Ah -- we also monitored the device thermals for a week.  They're consistently 45 C (not thermal throttling).",
        "posted_at": "2026-09-05T04:29:55.000Z",
        "author_url": "https://www.reddit.com/user/Kokotewa/"
      },
      {
        "url": "https://www.reddit.com/r/vmware/comments/1w7q0o2/comment/p9v10zn/",
        "depth": 0,
        "score": 1,
        "author": "Kokotewa",
        "excerpt": "I have a tentative RCA -- for those invested and for those who find this in the future.\n\n What I omitted from the original post was I observed from IPMI timeouts during my initial investigation. I didn't think they were relevant until I failed to access BMC a few days later. I then found a BMC self-test failure within the BIOS, and it all clicked.\n\n BMC runs in memory and would persist host reboot",
        "posted_at": "2026-09-15T00:17:01.000Z",
        "author_url": "https://www.reddit.com/user/Kokotewa/"
      },
      {
        "url": "https://www.reddit.com/r/vmware/comments/1w7q0o2/comment/p7wwia6/",
        "depth": 0,
        "score": 1,
        "author": "CompetitiveConcert93",
        "excerpt": "All components like board and CPU on VMware HCL?",
        "posted_at": "2026-09-05T04:16:30.000Z",
        "author_url": "https://www.reddit.com/user/CompetitiveConcert93/"
      },
      {
        "url": "https://www.reddit.com/r/vmware/comments/1w7q0o2/comment/p82auy2/",
        "depth": 0,
        "score": 1,
        "author": "L0rd_OverKill",
        "excerpt": "There is a bug that sounds just like this for those drives. When they reach 65535 hours there is an overflow error and they panic. There is a firmware update from Micron",
        "posted_at": "2026-09-05T23:19:24.000Z",
        "author_url": "https://www.reddit.com/user/L0rd_OverKill/"
      },
      {
        "url": "https://www.reddit.com/r/vmware/comments/1w7q0o2/comment/p98udoe/",
        "depth": 0,
        "score": 1,
        "author": "kachunkachunk",
        "excerpt": "A few things to unpack, it seems. Do you have any watchdog timers enabled in the BIOS or system setup? And any vendor or monitoring agents installed? Unlikely and I don't expect any from Asrock either, but asking anyway.\n\n H:0x9 and status 808s are what I would look more into if you notice I/O hitching and responsiveness issues, but documentation isn't deep on this, from an initial googling, so ma",
        "posted_at": "2026-09-11T22:23:51.000Z",
        "author_url": "https://www.reddit.com/user/kachunkachunk/"
      }
    ],
    "evidence": [
      "[post] 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.",
      "[post] WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x4579050d3840, 1050659) to dev \"t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000\" on path \"vmhba0:C0:T0:L0\" Failed:",
      "[comment u/L0rd_OverKill] There is a bug that sounds just like this for those drives. When they reach 65535 hours there is an overflow error and they panic. There is a firmware update from Micron"
    ],
    "virality": "low",
    "post_date": "2026-09-05T03:59:11.000Z",
    "post_kind": "text",
    "post_text": "Greetings!\n\nI'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.\n\nBackground\n\nThe configuration is small as far as servers go,\n\nAsrock Rack B550D4ID-2L2T\n\nRyzen 9 5950X (16-Core)\n\n64 GB Memory\n\nOn a UPS that is honestly way too large (can provide *hours* of uptime)\n\nPrior 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;\n\nthe drive wasn't on the HCL\n\nthe drive was a 22110 (the 2L2T doesn't natively support 22110 M2s)\n\nOkay, 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.\n\nIssue\n\nMy 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;\n\nupdate disk to 512b physical sector format (thanks to another Reddit Post)\n\nPost installation and VM migration, we...",
    "sentiment": "negative",
    "subreddit": "vmware",
    "post_title": "VMware 8.02 + Micron 7450 Pro 960GB NVMe M.2 2280",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/vmware/comments/1w7q0o2/vmware_802_micron_7450_pro_960gb_nvme_m2_2280/",
    "entity_role": "vendor",
    "post_author": "Kokotewa",
    "upvote_ratio": 0.8333333333333334,
    "mention_count": 1,
    "mention_surge": false,
    "subreddit_url": "https://www.reddit.com/r/vmware/",
    "total_upvotes": 4,
    "comments_total": 9,
    "total_comments": 9,
    "other_companies": [
      {
        "name": "VMware",
        "role": "partner",
        "domain": "vmware.com"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/Kokotewa/",
    "signal_category": "feedback",
    "comments_included": 6,
    "products_mentioned": [
      "7450 Pro"
    ]
  }
}

curl https://signals.autobound.ai/v1/signals/174ccf7a-fff7-56ea-a6d1-a51b227af328 \
  -H "X-API-KEY: $AUTOBOUND_API_KEY"

curl -X POST https://signals.autobound.ai/v1/companies/enrich \
  -H "X-API-KEY: $AUTOBOUND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"micron.com","limit":20}'