# Anyone has any idea how to deal with AWS nitro randomizing disk names at reboots?

**URL:** <https://forums.linbit.com/t/anyone-has-any-idea-how-to-deal-with-aws-nitro-randomizing-disk-names-at-reboots/975>\
**Category:** DRBD\
**Tags:** drbd\
**Created:** [August 9, 2025, 10:39pm UTC](https://forums.linbit.com/t/anyone-has-any-idea-how-to-deal-with-aws-nitro-randomizing-disk-names-at-reboots/975 "2025-08-09T22:39:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rvencu](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/rvencu/32/249_2.png) [@rvencu](https://forums.linbit.com/u/rvencu)\
**Post date:** [August 9, 2025, 10:39pm UTC](https://forums.linbit.com/t/anyone-has-any-idea-how-to-deal-with-aws-nitro-randomizing-disk-names-at-reboots/975/1 "2025-08-09T22:39:43Z")

</div>

I provision storage optimized instances to get the OS on an EBS volume and get a nvme volume for DRBD.

Except the problems appear at reboots. Nitro is randomly switching the order of the disks so nvme0n1 becomes nvme1n1 and the other way around. This blows up the DRBD config unless there is another way to deal with this problem in the config.

Hopefuly someone else bumped into this already.

---

<div class="post-metadata">

**Author:** ![robin-checkmk](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/robin-checkmk/32/45_2.png) [@robin-checkmk](https://forums.linbit.com/u/robin-checkmk)\
**Post date:** [August 11, 2025, 6:37am UTC](https://forums.linbit.com/t/anyone-has-any-idea-how-to-deal-with-aws-nitro-randomizing-disk-names-at-reboots/975/2 "2025-08-11T06:37:38Z")

</div>

Blind man speaking of color here, but shouldn’t you be able to just use another identifier to identify your disks?

---

<div class="post-metadata">

**Author:** ![candlerb](https://avatars.discourse-cdn.com/v4/letter/c/c5a1d2/32.png) [@candlerb](https://forums.linbit.com/u/candlerb)\
**Post date:** [August 11, 2025, 6:38am UTC](https://forums.linbit.com/t/anyone-has-any-idea-how-to-deal-with-aws-nitro-randomizing-disk-names-at-reboots/975/3 "2025-08-11T06:38:20Z")

</div>

Have you tried `/dev/disk/by-id/XXXXX` ? Or `by-uuid`, `by-partuuid`?

---

<div class="post-metadata">

**Author:** ![Ryan](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/ryan/32/42_2.png) [@Ryan](https://forums.linbit.com/u/Ryan)\
**Post date:** [August 12, 2025, 3:16pm UTC](https://forums.linbit.com/t/anyone-has-any-idea-how-to-deal-with-aws-nitro-randomizing-disk-names-at-reboots/975/4 "2025-08-12T15:16:25Z")

</div>

These days I tend to just default to using LVM and logical volumes, even if I intend to consume the entire backing disk for DRBD with a single logical volume.

Why? It keeps the DRBD resource configurations a little cleaner, no need to define each unique device for each host’s backing disk. Plus, the added flexibility of LVM is there if or when it’s needed.