Install problem on NVMe (nvme0: async event occurred)

[Jwidess]

Hi all,
I have been struggling the last few hours trying to figure out how to suppress messages I am getting during the install on my Mini PC. During the install, after I boot normally into multi-user mode, the console is spammed with the following lines,

Code Select Expand

nvme0: async event occurred (type 0x1, info 0x01, page 0x02)They are spammed at such a rate I cannot get through the installer as even the end GUI when run with installer and opnsense is overwritten by the console messages.
The only other post I can find referencing a similar issue is here, but @MattD76 reported they were still getting the async messages. Please let me know if anyone has a solution to this problem; it would be much appreciated!
NOTE: I tested this with another model of NVMe drive (WD Blue) and this issue completely disappeared, so if I can't get this resolved, I will return my current drive and get another WD, but I'd prefer not to.

Computer: Generic Amazon "MOGINSOK Mini PC 2.5Gbe Intel Celeron N5095 Quad Core, 4*Intel I225-V"
Drive with async errors: Silicon Power 128GB NVMe M.2 PCIe Gen3x4 2280 SSD (SP128GBP34A60M28)
Install: OPNsense-25.7-vga-amd64.img.bz2

[meyergru]

As it seems, there are now many more no-name NVMEs build into those chinese units, probably because of the price raise in SSD storage.

Under FreeBSD, they can show such effects, because their manufacturers do not care about FreeBSD (and FreeBSD does not care about circumventing NVME protocol problems).

I would change the NVME for a known brand with high TBW.

P.S.: That now made it to https://forum.opnsense.org/index.php?topic=42985, point 14.

[pfry]

A real Silicon Power unit should be OK, from a brand/manufacturer standpoint. The device itself is a tiny cacheless unit - very cheap, but likely no bargain.

[Jwidess]

As it seems, there are now many more no-name NVMEs build into those chinese units, probably because of the price raise in SSD storage.

Under FreeBSD, they can show such effects, because their manufacturers do not care about FreeBSD (and FreeBSD does not care about circumventing NVME protocol problems).

I would change the NVME for a known brand with high TBW.

P.S.: That now made it to https://forum.opnsense.org/index.php?topic=42985, point 14.

Thanks for the reply, however I've had good experiences with Silicon Power in the past and thought they where at least a decent drive brand, however trying to use another SP branded 128GB Model (P34A60 SP128GBP34A60M28) resulted in the mini PC not even posting, so maybe they're a mediocre brand after all.

And yeah @pfry they appear to be real SP drives, don't know who'd bother making clone SP drives lol.

I might go digging around in the kernel to understand how and why these async events are getting generated, but for now we'll get a different brand drive.

[meyergru]

It does not have to be the drive, see https://forum.opnsense.org/index.php?topic=42985.0, point 23.

[Jwidess]

It does not have to be the drive, see https://forum.opnsense.org/index.php?topic=42985.0, point 23.

Well when repeating the install with a WD branded 500GB NVMe drive, these async messages disappeared. Additionally I did follow point 23 from that link and applied the tweaks from here, but that changed nothing unfortunately. And I appreciate the help!