Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]

[Tom Yan]

On 14 August 2016 at 11:10, Pavel Machek <pavel@xxxxxx> wrote:
>
> It is the case in v4.6. We had change hda->sda for SATA drives long
> time ago, it was stable since that.

Not for me. It has been like forever (even if it wasn't the fact) that
the disk order is not consistent among boots. Only that would
logically make sense anyway. How do you think we can sanely make sure
that the SCSI disk driver starts enumerating "SCSI disks" from
usb-storage/uas only when all of those from libata probed? Wait for 1
second? 1 minute? or 1 hour? It's an irrational thing to do no matter
how long or how short it is.

>
> I'd rather not mess with initrd, and initrd was not required in the
> past.

Well, that's your choice, use PARTUUID then.

>
> kernel-parameters.txt only mentions UUID= in connection with
> resume. Is the documentation correct?

That's `PARTUUID=`. See what PARTUUID is referring to in the linked
comment below. (Note that when we say UUID instead of PARTUUID, we are
usually referring to the filesystem UUID.)

...

resume= [SWSUSP]
Specify the partition device for software suspend
Format:
{/dev/<dev> | PARTUUID=<uuid> | <int>:<int> | <hex>}

...

root= [KNL] Root filesystem
See name_to_dev_t comment in init/do_mounts.c.

...

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/init/do_mounts.c?h=v4.8-rc1#n182