You have hit a classic Linux catch-22:
sudo scp fails because the root user doesn't know what m2 is. Your SSH configuration (aliases and keys) is stored in your normal user's ~/.ssh/ folder, which root ignores.
scp (without sudo) fails because your normal user doesn't have the permissions to read the MyNode files on that mounted Pi drive.
The quoted sudo "scp..." command fails because the shell thinks the entire sentence inside the quotes is a single program name.
To bypass this, you just need to stage the file in your home directory, take ownership of it, and then run scp as your normal user.
sudo scp fails because the root user doesn't know what m2 is. Your SSH configuration (aliases and keys) is stored in your normal user's ~/.ssh/ folder, which root ignores.
scp (without sudo) fails because your normal user doesn't have the permissions to read the MyNode files on that mounted Pi drive.
The quoted sudo "scp..." command fails because the shell thinks the entire sentence inside the quotes is a single program name.
To bypass this, you just need to stage the file in your home directory, take ownership of it, and then run scp as your normal user.