[PVE-User] Disk recognition order

Uwe Sauter uwe.sauter.de at gmail.com
Tue Aug 29 13:44:43 CEST 2017

I thought so but when setting up new VMs where the disks don't have partitions yet, there is yet nothing that you could use
(especially when using automation for deployment, e.g. Ansible).

As you can see from my config the disks have different sizes and it's really unintuitive when the second configured device (which
I expected to be /dev/sdb) has the wrong size…

On hardware you usually can count on the order of connected SATA/SAS ports where empty ones are just skipped. And if using HBAs or
RAID cards they usually initialize first before presenting the detected disks (in order) to the OS.

Having a look at the dmesg output it seems to be a timing issue: highest LUN is recognized as first.

Am 29.08.2017 um 13:30 schrieb Lindsay Mathieson:
> On 29/08/2017 9:17 PM, Uwe Sauter wrote:
>> Is there any way to force scsi1 to /dev/sdb, scsi2 to /dev/sdc, etc. so that the order inside the VM is the same as in the
>> configuration?
> I don't believe so, thats really a general linux device issue, not a VM or proxmox one - dev ienries shuffling on bot is a issue
> for all linux based systems.
> You really should be using guid's or /dev/disk/by-id for your device entries in the vm.

More information about the pve-user mailing list