SQL Server master database

It isn't required but you should do it anyway. The SQL module creates a script in the Resource Group that changes the Active Computer Name (ACN) to that of the primary server. It then starts the services and changes the ACN back to the original name.

In the Master DB there are references to the server name but because of the script mentioned above, they do not need to be changed.

The reason I say to put the master on the mirrored drive is so you don't have to manage the database on each server. Say you add a SQL user account to serverA and the master is NOT being mirrored. If you wanted serverB to have the same users and settings as serverA you would then have to MANUALLY make those changes to serverB as well.

So when I do SQL module installs here is what I typically do:

Install SQL to non-mirrored drive
Put all DB's on mirrored drive
Make sure all drive letters are the same for all parts of the SQL install.

FYI, I've done dozens of these over the past 3 years without issue.

That being said, if you want to leave the master on a non-mirrored drive you can do that as well. You can then simply attach the application databases on the target and things should still work. However, any changes to the local SQL installation that will affect Master must be done on both sides.

Does that help?

Is it correct that MS SQL server writes things like failures of user databases, current SQL sessions, blocked tables or the option to set an user database offline are written to the master database, too?
If so i think there i have no choice - Master must be replicated.