Historically there have been a number of other different places used to mount removable media This directory contains subdirectories which are used as mount points for removable media such as floppy The content of this directory is a local issue and should not affect the manner in which any program is run."ģ.11. This directory is provided so that the system administrator may temporarily mount a filesystem as needed. This also breaks functionality with other Azure products, like ADE that still uses /mnt/azure_bek_disk and assumes that the resource drive needs to be mounted on /mnt/resource when it is encrypted, which overrides and sometimes duplicates the entries on /etc/fstab, which at the same time causes systemd to try to mount everything without having dependencies between those mount points. Looking for any help from anyone here that better understands how this process works from start to end here - especially as MicrosoftDocs/azure-docs#68844 was since closed. However, attempts to then run cloud-init clean remove all other Azure-specifics and knowledge from the VM - such that cloud-id now returns none instead of azure, for example. It seems that editing the Base64-encoded details within /var/lib/waagent/ovf-env.xml is where this needs to start. However, there has to be a way to get this to effectively re-run cloud-init - though I'm currently coming up short. mentions that "For single VMs, custom data in the VM model cannot be updated". I'm now finding a need to fix this on an Azure VM that has already been provisioned, in-use, and not otherwise easily re-created - while ensuring the fix will remain even after a redeploy, etc., and receiving a new temporary disk from Azure. Mounting the ephemeral disk at /mnt/resource resolved all of these possibilities in a consistent way. If /mnt/data1 is created as persistent (the ephemeral disk is unmounted), it will be maskedĪnd appear not to exist if the ephemeral disk is mounted at /mnt again. Of the ephemeral disk when /mnt/data1 was created and the current mount state of the ephemeralĭisk. The recreation of /mnt/data1 is not required under typical circumstances as the directory isĪnother consideration is that /mnt/data1 may or may not exist, depending on the mount state mnt/data1 no longer exists so data disk can no longer be mounted until /mnt/data1 is recreated Mount data disk at /mnt/data1 and add entry to /etc/fstab Create directory /mnt/data1 (it will not be persistent) Ephemeral disk is automagically mounted at /mnt mnt without jumping through additional hoops (like creating the new directory in the ephemeralĭisk every time the system boots in order to mount another file system): The ephemeral disk is mounted at /mnt prevents other filesystems from being mounted under
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |