Skip to content

Commit dcb3003

Browse files
committed
Final updates.
1 parent 62fa285 commit dcb3003

File tree

2 files changed

+6
-10
lines changed

2 files changed

+6
-10
lines changed

articles/virtual-machines/linux/add-disk.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: storage
66
ms.subservice: disks
77
ms.collection: linux
88
ms.topic: how-to
9-
ms.date: 01/06/2023
9+
ms.date: 01/09/2023
1010
ms.author: rogarana
1111
---
1212

@@ -137,6 +137,8 @@ Next, open the */etc/fstab* file in a text editor. In the file, you'll use the U
137137
UUID=33333333-3b3b-3c3c-3d3d-3e3e3e3e3e3e /datadrive xfs defaults,nofail 1 2
138138
```
139139

140+
When you are done editing the file, save and close the editor.
141+
140142
> [!NOTE]
141143
> Later removing a data disk without editing fstab could cause the VM to fail to boot. Most distributions provide either the *nofail* and/or *nobootwait* fstab options. These options allow a system to boot even if the disk fails to mount at boot time. Consult your distribution's documentation for more information on these parameters.
142144
>

articles/virtual-machines/linux/attach-disk-portal.md

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Use the portal to attach new or existing data disk to a Linux VM.
44
author: roygara
55
ms.service: storage
66
ms.topic: how-to
7-
ms.date: 01/06/2023
7+
ms.date: 01/09/2023
88
ms.author: rogarana
99
ms.subservice: disks
1010
ms.collection: linux
@@ -155,19 +155,13 @@ The output looks similar to the following example:
155155
> [!NOTE]
156156
> Improperly editing the **/etc/fstab** file could result in an unbootable system. If unsure, refer to the distribution's documentation for information on how to properly edit this file. You should create a backup of the **/etc/fstab** file is created before editing.
157157
158-
Next, open the **/etc/fstab** file in a text editor as follows:
159-
160-
```bash
161-
sudo vi /etc/fstab
162-
```
163-
164-
In this example, use the UUID value for the `/dev/sdc1` device that was created in the previous steps, and the mountpoint of `/datadrive`. Add the following line to the end of the `/etc/fstab` file:
158+
Next, open the **/etc/fstab** file in a text editor. Use the UUID value for the `/dev/sdc1` device that was created in the previous steps, and the mountpoint of `/datadrive`. Add the following line to the end of the file:
165159

166160
```bash
167161
UUID=33333333-3b3b-3c3c-3d3d-3e3e3e3e3e3e /datadrive xfs defaults,nofail 1 2
168162
```
169163

170-
We used the vi editor, so when you are done editing the file, press `Esc` to enter command mode and `wq` to save and close the editor.
164+
When you are done editing the file, save and close the editor.
171165

172166
> [!NOTE]
173167
> Later removing a data disk without editing fstab could cause the VM to fail to boot. Most distributions provide either the *nofail* and/or *nobootwait* fstab options. These options allow a system to boot even if the disk fails to mount at boot time. Consult your distribution's documentation for more information on these parameters.

0 commit comments

Comments
 (0)