Merge pull request #4967 from vin-yu/patch-4

Adding Note for setting new masterdb file location if mdf/ldf cannot be found

Author: PRMerger13

docs/linux/sql-server-linux-configure-mssql-conf.md

@@ -193,6 +193,9 @@ To change these settings, use the following steps:
    ```bash
    sudo systemctl start mssql-server
    ```
+   
+> [!NOTE]
+> If SQL Server cannot find master.mdf and mastlog.ldf files in the specified directory, a templated copy of the system databases will be automatically created in the specified directory, and SQL Server will successfully start up. However, metadata such as user databases, server logins, server certificates, encryption keys, SQL agent jobs, or old SA login password will not be updated in the new master database. You will have to stop SQL Server and move your old master.mdf and mastlog.ldf to the new specified location and start SQL Server to continue using the existing metadata. 
 
 
 ## <a id="masterdatabasename"></a> Change the name of master database files.
@@ -216,7 +219,7 @@ The **filelocation.masterdatafile** and **filelocation.masterlogfile** setting c
 
    ```bash
    sudo mv /var/opt/mssql/data/master.mdf /var/opt/mssql/data/masternew.mdf
-   sudo mv /var/opt/mssql/data/mastlog.ldf /var/opt/mssql/data /mastlognew.ldf
+   sudo mv /var/opt/mssql/data/mastlog.ldf /var/opt/mssql/data/mastlognew.ldf
    ```
 
 1. Start the SQL Server service:
@@ -226,6 +229,7 @@ The **filelocation.masterdatafile** and **filelocation.masterlogfile** setting c
    ```
 
 
+
 ## <a id="dumpdir"></a> Change the default dump directory location
 
 The **filelocation.defaultdumpdir** setting changes the default location where the memory and SQL dumps are generated whenever there is a crash. By default, these files are generated in /var/opt/mssql/log.