# Boot Volume Selection During Instance Creation for Local Storage

During Morpheus instance creation, the provisioning workflow will **delete existing logical volumes**, **create a boot volume**, and then **identify the correct disk device** using the device’s unique identifier (UID).

The boot volume is determined by matching the device UID found in the storage controller to the corresponding Linux device path.

## Log Details

When creating a Morpheus instance, you may see the following log entries:

```
```
[2026-02-09 02:45:39,023] ... Deleting all logical volumes on server  
[2026-02-09 02:45:42,887] ... Attempting to create boot volume  
[2026-02-09 02:45:43,470] ... Waiting for device discovery complete. Success  
[2026-02-09 02:45:44,442] ... GET /redfish/v1/.../Drives/2556 -> error: ResourceMissingAtURI ... Retrying in 10 seconds...  
[2026-02-09 02:45:44,442] ... Boot volume for server created with unique identifier: 600508B1001C40706B7600592D4A5C5A
```
```

The logs show:

- Logical volumes are cleared on the server.
- Morpheus creates a new boot volume.
- The system waits for Redfish device discovery to complete.
- If a drive is not yet visible, it may return `ResourceMissingAtURI` and retry.
- Once the boot volume is created, it logs the unique device identifier.
- How Boot Volume is Determined.

For OS installation, the boot volume is identified based on the **device UID**. Depending on the server storage controller, the device UID format differs

Table 1. UID Format

       | Storage Device | Name | RAID Type | Identifiers.DurableNameFormat | Identifiers.DurableName |
| --- | --- | --- | --- | --- |
| HPE MegaRAID (MR216i-o) Storage Controller | BootVolume | RAID1 | NAA | 600508B1001C40706B7600592D4A5C5A |
| HPE NVMe SHIELD (NS204i) Boot Device | BootVolume | RAID1 | EUI | 1234:5678:9ABC:DEF0 |

## Finding the Device Path

Once the device UID is known (from the storage controller), the provisioning script searches for the matching device in `/dev/disk/by-id/`

The script looks for the **first entry that contains the UID** (or a stripped version of the UID). These entries are **stable identifiers** that point to the actual Linux block device.

Once a match is found, the script resolves the symbolic link to determine the real boot device path, which will be in the form: `/dev/sdX`

This `/dev/sdX` path is then used for OS installation.
