archive mirror
 help / color / mirror / Atom feed
Subject: Re : Query on UFS Lun detection
Date: Thu, 10 Jun 2021 18:58:04 +0530	[thread overview]
Message-ID: <> (raw)

Hi Community,

We are using UFS as a boot device, and we encountered an error, 
mentioned below while booting through UFS.

APPS Crash - Kernel panic - not syncing: VFS: Unable to mount root fs on 

Here in Kernel command line we are passing "root=sda7", this is our 
Filesystem partition to be mounted.

While debugging the same we observed the partition which is suppose to 
be mounted as Filesystem is not enumerated  itself.
The reason behind not enumerating of partition is, the other Lun got 
detected first instead of one which is having FS partition.

We are using async probe, hence we know the detection will happen in 
async way,

In working case :  it looks like below

sd 0:0:0:0: sda1 sda2 sda3 sda4 …..sda8

sd 0:0:0:1: sdb1 sdb2
Here, sd 0:0:0:0 Lun got detected first and enumerated as "sdaN", we 
have FS partition as "sda7" and so we don’t see above mentioned error.

In non working case : it looks like below

sd 0:0:0:0: sdb1 sdb2 sdb3 sdb4 …..sdb8

sd 0:0:0:1: sda1 sda2
Here, sd 0:0:0:1 Lun got detected first and enumerated as "sdaN" but we 
don’t have FS partition in this Lun. Instead FS partition now became 

Observation here is, which ever Lun gets detected first it will have 
"sda" enumeration and so on.
However, sdx’s driver scsi/sd.c uses async probe to improve performance, 
meaning sdx disks are created in parallel. Whoever calls 
device_add_disk() first becomes sda, the next become sdb….

Is there any way, where we can fix this in the Lun detection part of 

Thank You,
Hiren Gohel

             reply	other threads:[~2021-06-10 13:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 13:28 vhiren [this message]
2021-06-10 14:51 ` Re : Query on UFS Lun detection Rob Clark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).