Need better support for NVME ephemeral temp disks
- Dominant language
- Python
- Stars
- 11
- Forks
- 24
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 1
Description
The new D/E_v6 SKU come with NVME controller and an updated mechanism how ephemeral discs are handled.
https://learn.microsoft.com/en-us/azure/virtual-machines/enable-nvme-temp-faqs
The approach to simply now ask the customer to handle the initialization of temp disks is not well prepared.
Most OS images - which are flagged NVME ready - still simply cause a delay at startup and failure for the temp-disk-dataloss-warning.service .
systemctl status temp-disk-dataloss-warning.service
temp-disk-dataloss-warning.service - Azure temporary resource disk dataloss warning file creation
Loaded: loaded (/etc/systemd/system/temp-disk-dataloss-warning.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2025-06-30 09:51:40 EDT; 1h 3min ago
Process: 2610 ExecStart=/usr/local/sbin/temp-disk-dataloss-warning (code=exited, status=1/FAILURE)
Main PID: 2610 (code=exited, status=1/FAILURE)
Jun 30 09:51:40 azloranvmetest systemd[1]: Starting Azure temporary resource disk dataloss warning file creation...
Jun 30 09:51:40 azloranvmetest temp-disk-dataloss-warning[2610]: There is no mountpoint of /dev/disk/cloud/azure_resource-part1 in /etc/fstab
Jun 30 09:51:40 azloranvmetest systemd[1]: temp-disk-dataloss-warning.service: Main process exited, code=exited, status=1/FAILURE
Jun 30 09:51:40 azloranvmetest systemd[1]: temp-disk-dataloss-warning.service: Failed with result 'exit-code'.
Jun 30 09:51:40 azloranvmetest systemd[1]: Failed to start Azure temporary resource disk dataloss warning file creation.
It would be helpful if the there is an extension or separate file similiar as /usr/lib/udev/rules.d/66-azure-ephemeral.rules where the user can easily recreate the old behaviour and define that the first NVME temporary disk shows up as /dev/disk/cloud/azure_resource_part1 .
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading /usr/lib/udev/rules.d/66-azure-ephemeral.rules and /usr/local/sbin/temp-disk-dataloss-warning, then compare NVMe disk behavior with the linked Azure FAQ. Check how the service uses /etc/fstab; done should let users configure the first NVMe temporary disk as /dev/disk/cloud/azure_resource_part1 and avoid the reported service failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, linux, python
- Domain
- cloud, infrastructure, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100