From: Christoph Hellwig <hch@infradead.org>
To: Bryan Gurney <bgurney@redhat.com>
Cc: Jorge Fernandez Monteagudo <jorgefm@cirsa.com>,
Christoph Hellwig <hch@infradead.org>,
"tj@kernel.org" <tj@kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: SATA errors accessing hidden partitions
Date: Tue, 10 Sep 2019 23:34:16 -0700 [thread overview]
Message-ID: <20190911063416.GA25673@infradead.org> (raw)
In-Reply-To: <CAHhmqcTF1wBq037v2dDrKOs8tNhAMzw4_nY_52KY65NvCqWDXw@mail.gmail.com>
On Tue, Sep 10, 2019 at 11:12:36AM -0400, Bryan Gurney wrote:
> Oh, okay. I'm pretty sure that blkid checks regions near the end of a
> device (for example, GPT has what looks like a backup of the "EFI
> PART" boot record near the end of the device). Therefore, it may be
> worthwhile to double-check the size of the partition, in case they're
> not 4 GB, for some strange reason.
Some MD RAID suprblocks also are at the end. Either way I'm pretty
sure this is legitimate probing and not a bug.
> Why is there an "Illegal Request - Unaligned write command" sense
> error from sd, right after the failed ata command "READ FPDMA QUEUED"?
> Is this an expected failure mode for a read to a locked range? (I'm
> not familiar with TCG Opal drives, so unfortunately I don't have
> enough context.)
It could be that we are just having issues translating the errors,
especially given that we don't use sense data in ATA except for ZAC
drives.
prev parent reply other threads:[~2019-09-11 6:34 UTC|newest]
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 ` SATA errors accessing hidden partitions 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
2019-09-10 15:12 ` Bryan Gurney
2019-09-11 6:34 ` Christoph Hellwig [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190911063416.GA25673@infradead.org \
--to=hch@infradead.org \
--cc=bgurney@redhat.com \
--cc=jorgefm@cirsa.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).