Linux-ide Archive on
 help / color / Atom feed
From: Jorge Fernandez Monteagudo <>
To: Bryan Gurney <>
Cc: Christoph Hellwig <>,
	"" <>,
	"" <>
Subject: RE: SATA errors accessing hidden partitions
Date: Tue, 10 Sep 2019 14:03:47 +0000
Message-ID: <AM6PR10MB3399036D93B32666191730D1A1B60@AM6PR10MB3399.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <>

Hi Bryan! Thanks for your detailed answer!

>Notice that logical block 524272 on devices sda3, sda4, and sda5 are
>cited.  This is a blind guess, but are these partitions 524288 sectors
>(256 MB) in size?

No, they're 4GB partitions.

>You can notice that the first few reads are near the "end" of the
>partition.  In fact, the first two read completions are 128 sectors
>before the end, and 16 sectors before the end.  I'm guessing that this
>"-16" read is the one that's failing in these three partitions.

Then, there is an inconsistency in the blkid and kernel communication? Why the kernel
tries to access to a locked range? It seems that blkid ask for a sector and the kernel try
to read it back ignoring its locked, reducing speed and trying again with no luck until
the error is returned. This is consistent with our workaround removing blkid from the
udev rule to avoid the error.

Maybe the OPAL is not clear enough about locked ranges and kernel thinks is an error,
or it's an error in the disk's firmware I don't know, but under windows or MacOS X no
error is displayed.

Is there some way to ask a disk for their locked ranges and patch blkid to avoid accesing them?


  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AM6PR10MB33991CE19828429C676C0296A1C40@AM6PR10MB3399.EURPRD10.PROD.OUTLOOK.COM>
2019-09-09  6:25 ` Jorge Fernandez Monteagudo
2019-09-10  5:53   ` Christoph Hellwig
2019-09-10  8:03     ` Jorge Fernandez Monteagudo
2019-09-10 11:40       ` Christoph Hellwig
2019-09-10 13:08       ` Bryan Gurney
2019-09-10 14:03         ` Jorge Fernandez Monteagudo [this message]
2019-09-10 15:12           ` Bryan Gurney
2019-09-11  6:34             ` Christoph Hellwig

Reply instructions:

You may reply publically 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 \
    --in-reply-to=AM6PR10MB3399036D93B32666191730D1A1B60@AM6PR10MB3399.EURPRD10.PROD.OUTLOOK.COM \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-ide Archive on

Archives are clonable:
	git clone --mirror linux-ide/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-ide linux-ide/ \
	public-inbox-index linux-ide

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone