Comment 2 for bug 1936752

Hi @wallyworld,

I know it is a bit vague, but it happens some times. I can deploy several times in a day and not see it happening, or see it once.

I've collected the logs you've requested for one of the broken runs: https://drive.google.com/drive/folders/1II5SCglZahH-UE3UKUYLCysLl4OV7NT4

That run corresponds to this bundle: https://pastebin.canonical.com/p/dJFb2JGMsm/
The logs .0, .1 ... .3 corresponds to the 4x minio units, respectively.

In that specific run, all 4x units broke with the same issue.

Whenever that happens, the device (e.g. /dev/disk/by-uuid/7flWaV-Rxiv-mGF6-p9sk-sEe1-mwnl-7zjOd3) will not be a symlink

The only exception I've noticed was on: LP #1936876
where I saw that same naming by-uuid but it resolved to an actual device.