kelsiersghost

(Edited to make a better argument) TL;DR: MPIO (Multi-Path I/O) offers redundancy and performance improvements by using multiple physical paths between Unraid and storage devices. It's already supported by the Linux kernel and standard on platforms like TrueNAS and Proxmox, providing benefits without adding complexity. Adding MPIO to Unraid would improve reliability, scalability, and performance for advanced users while keeping Unraid competitive with other storage solutions. I'd like to request native support for Multi-Path I/O (MPIO) in Unraid. MPIO allows multiple physical paths between a server and its storage devices. It’s already supported by the Linux kernel and widely used in enterprise systems. This feature provides two key advantages: redundancy and better performance. Redundancy is a key advantage, and it’s not just for worst-case scenarios—it’s for real-world reliability. Components like HBA cards or cables can and do fail unexpectedly. I recently had the EEPROM on my 9400-16i card fry out of nowhere, which immediately took my storage offline. With MPIO, if one card or cable fails, traffic is automatically rerouted through another path, meaning no downtime and no immediate panic. This kind of failover protection ensures your system stays running even when hardware fails, which is something many users will encounter eventually. Performance is another significant benefit. MPIO can leverage multiple active paths to balance data traffic, resulting in faster transfers and reduced latency. For example, imagine a server with an HDD backplane that supports 24 drives. By connecting two HBA cards, you prevent the drives from throttling due to a lack of bandwidth, spreading the data load across both cards for higher throughput and fewer bottlenecks. Now, imagine rebuilding drives or completing large Mover operations in half the time! As Unraid users scale their systems, MPIO ensures that performance scales with them. Adding MPIO is really a no-brainer when you look at what other platforms are doing. Systems like TrueNAS, Proxmox, and even more enterprise-focused options like VMware have supported MPIO for years. These platforms recognize that MPIO isn’t some niche feature — it’s essential for anyone working with SANs, iSCSI, or just looking for more reliability in high-performance environments. And since Unraid already uses a Linux kernel that supports MPIO, it’s a matter of exposing and integrating a feature that’s already available. While Unraid’s focus on simplicity is great, ignoring a feature like this limits its potential. The ability to improve performance and reliability with minimal configuration overhead would appeal to users across the board, from advanced home setups to those running Unraid in professional environments. Used Supermicro chassis are getting cheaper and more available on Ebay by the day. As people talk about them on reddit more and more, people are going to be looking for the OS that supports their growing libraries. I even feel like this could be a feature worthy of being listed on the Label: "unRAID 7.0! Now with MPIO!" What do you think?

I'm having the same issue on version 7 as well. When I type in > which mover It tells me /usr/local/sbin/mover It looks like a spelling error - move vs mover. When I look in the /sbin folder, there are files BOTH called move and mover. For some reason the call is looking for move, so changing the file name isn't going to work. Should I just downgrade?