# Connected Cache Ubuntu preparation — partial notes

Review the captured Ubuntu preparation sequence for a new cache VM. The source cites different Ubuntu versions and uses /dev/sdb as an example disk, so it does not establish the correct target disk or version for another host.

!!!warning Source-derived reference
These notes were recovered from OneNote. Configuration, permissions and operating results have not been freshly verified. Confirm the applicable authority and environment before acting.
!!!

- Download the Ubuntu ISO (documentation calls for 22.04 but the installation scripts call out 24.04 as supported too)
- Create a new VM meeting the requirements above.
- If you need assistance creating a Ubuntu VM please contact CCM IT for help
- Strongly consider enabling guest integration services to simplify the deployment of your keypair for ssh authentication, and ease deployment of the configuration script files.

## Installing and Configuring Ubuntu

- Follow the normal installer steps to install the server.
- Assign a static IP (or DHCP reservation)
- Install all updates.
- Sudo apt update –y
- Sudo apt upgrade –y
- Switch to the linux-azure kernel for best performance and SR-IOV support.
- Sudo apt install linux-azure
- Format and mount your cache data disk.
- You can select the data disk, format and mount it during the server installation - this will be much faster and more straightforward than the commands below
- Find your disk logical name
- sudo lshw -C disk and note the logical name of disk1
- The source uses /dev/sdb in the example commands; it does not establish the correct disk on another host. The subsequent format operation applies to that example target.
- Format and Partition the entire disk
- sudo mkfs -t ext4 /dev/sdb
- Mount the partition
- sudo mkdir /mnt/mccdata
- sudo mount /dev/sdb /mnt/mccdata
- Mount the partition at boot time.
- Sudo lsblk –f. (Note down the UUID)
- Sudo vi /etc/fstab
- Add the following on a new line in fstab
- UUID=\<UUID from lsblk –f command\> /mnt/mccdata ext4 defaults 0 0
- Reboot Server and make sure partition is mounted at boot.

## Related guidance

- [Topic overview](Introduction.md)
- [Source review status](../../review/Review-status.md)