Well, there is a potential impact RefindPlus v0.13.2.AN might have although if it was the case, it should have shown up before the incident. On Macs, it basically does not rescan for newly revealed DXE drivers. This means that disks with non-native filesystems (skipped a chunk of your post, so not sure if this is the case here) might not show up on Macs.
Yes, didn’t show up. When booting Linux the drive initialization times out. I added more timeout with a kernel module parameter and it seems as though more blocks are detected each time. I’m hoping it will eventually show up. Only a few 100,000 blocks to go! :|Have you tried checking it (in Windows) with Samsung's own software?
Tool & Software Download | Samsung Semiconductor Global
Download various software related to your product, including Samsung Magician, designed for use with Samsung's memory products, and find related information.semiconductor.samsung.com
I have augmented my bootrom with APFS jumpstart and NVME.ffs so unlikely the issue. I was deleting Monterey Partition and resizing Mojave partition from Monterey Recovery USB when it froze for some time. Unresponsive mouse, kbd, etc...Seems you somewhat reduced the random question marks
Good thing as it meant I was able to hang in there long enough get to this:
Well, there is a potential impact RefindPlus v0.13.2.AN might have although if it was the case, it should have shown up before the incident. On Macs, it basically does not rescan for newly revealed DXE drivers. This means that disks with non-native filesystems (skipped a chunk of your post, so not sure if this is the case here) might not show up on Macs.
As said, this should have manifested before your incident if this was a factor but regardless, you might want to eliminate this by building the current code base on GitHub or waiting for the next release.
RP issue I pointed out is not related to the presence or absence of APFS and/or NVME.
Kudos!