Add note not to use root volume group of LVM for HANA volumes

Author: msjuergent

articles/virtual-machines/workloads/sap/get-started.md

@@ -110,6 +110,8 @@ For information on integration of Azure services into SAP components, see:
 
 ## Change Log
 
+- 05/19/2020: Add important message not to use root volume group when using LVM for HANA related volumes in [SAP HANA Azure virtual machine storage configurations](https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-vm-operations-storage)
+- 05/19/2020: Add new supported OS for HANA Large Instance Type II in [Compatible Operating Systems for HANA Large Instances](https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/os-compatibility-matrix-hana-large-instance)
 - 05/12/2020: Change in [Public endpoint connectivity for VMs using Azure Standard ILB in SAP HA scenarios](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-standard-load-balancer-outbound-connections) to update links and add information for 3rd party firewall configuration
 - 05/11/2020: Change in [High availability of SAP HANA on Azure VMs on SLES](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/sap-hana-high-availability) to set resource stickiness to 0 for the netcat resource, as that leads to more streamlined failover 
 - 05/05/2020: Changes in [Azure Virtual Machines planning and implementation for SAP NetWeaver](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/planning-guide) to express that Gen2 deployments are available for Mv1 VM family

articles/virtual-machines/workloads/sap/hana-vm-operations-storage.md

@@ -14,7 +14,7 @@ ms.service: virtual-machines-linux
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure
-ms.date: 03/10/2020
+ms.date: 05/19/2020
 ms.author: juergent
 ms.custom: H1Hack27Feb2017
 
@@ -54,6 +54,9 @@ In the on-premises world, you rarely had to care about the I/O subsystems and it
 
 Given that low storage latency is critical for DBMS systems, even as DBMS, like SAP HANA, keep data in-memory. The critical path in storage is usually around the transaction log writes of the DBMS systems. But also operations like writing savepoints or loading data in-memory after crash recovery can be critical. Therefore, it is **mandatory** to leverage Azure Premium Disks for **/hana/data** and **/hana/log** volumes. In order to achieve the minimum throughput of **/hana/log** and **/hana/data** as desired by SAP, you need to build a RAID 0 using MDADM or LVM over multiple Azure Premium Storage disks. And use the RAID volumes as **/hana/data** and **/hana/log** volumes. 
 
+> [!IMPORTANT]
+>The three SAP HANA FileSystems /data, /log and /shared must not be put in a default or root volume group.  It is highly recommended to follow the Linux Vendors guidance which is typically to create individual Volume Groups for /data, /log and /shared.
+
 **Recommendation: As stripe sizes for the RAID 0 the recommendation is to use:**
 
 - 256 KB for **/hana/data**