You're referring to MultiBeast, a popular software tool for creating bootable USB drives and configuring EFI Bootloaders on Macs!
You can download MultiBeast 11.3.0 from the official website. Follow the installation instructions to install and use the software.
Here's a detailed feature overview of MultiBeast 11.3.0, specifically for macOS Mojave:
Multibeast 11.3.0 - Mojave -
You're referring to MultiBeast, a popular software tool for creating bootable USB drives and configuring EFI Bootloaders on Macs!
You can download MultiBeast 11.3.0 from the official website. Follow the installation instructions to install and use the software. multibeast 11.3.0 - mojave
Here's a detailed feature overview of MultiBeast 11.3.0, specifically for macOS Mojave: You're referring to MultiBeast, a popular software tool
This could have to do with the pathing policy as well. The default SATP rule is likely going to be using MRU (most recently used) pathing policy for new devices, which only uses one of the available paths. Ideally they would be using Round Robin, which has an IOPs limit setting. That setting is 1000 by default I believe (would need to double check that), meaning that it sends 1000 IOPs down path 1, then 1000 IOPs down path 2, etc. That’s why the pathing policy could be at play.
To your question, having one path down is causing this logging to occur. Yes, it’s total possible if that path that went down is using MRU or RR with an IOPs limit of 1000, that when it goes down you’ll hit that 16 second HB timeout before nmp switches over to the next path.