From: Hamish McIntyre-Bhatty <cygwin@hamishmb.com>
To: cygwin@cygwin.com
Subject: Re: Smartctl issues in Cygwin with elevated terminal
Date: Mon, 26 Sep 2022 15:26:36 +0100 [thread overview]
Message-ID: <eed7c579-ef6f-1e25-7a39-a8010c801e6e@hamishmb.com> (raw)
In-Reply-To: <d5922237-d5ee-e82f-f35e-4fad284c7fb5@t-online.de>
On 13/09/2022 18:23, Christian Franke wrote:
> Hamish McIntyre-Bhatty wrote:
>> I recently noticed that smartctl only works when the Cygwin Terminal
>> isn't run as administrator - the opposite way round to Linux where you
>> need superuser privileges to access the disk.
>>
>> With Administrator privileges on Windows 11, I get:
>>
>> "Read Device Identity Failure Input/Output error"
>
> This likely happens because one of the tried pass-through I/O-controls
> returns an error code which does not mean "not implemented". This is a
> limitation or bug in the driver of the disk controller.
>
> For further diagnostics, try for example. 'smartctl -r ioctl,2 -i /dev/sda'
>
>
>>
>> But it continues to work fine as a normal user.
>
> When run without admin rights for a SATA device, smarctl may print:
> "Warning: Limited functionality due to missing admin rights"
> and then prints only limited device identify and SMART DATA information
> returned by IOCTL_STORAGE_QUERY_PROPERTY and IOCTL_STORAGE_PREDICT_FAILURE.
>
> Other functionality requires admin rights and a working pass-through
> I/O-control - try 'smartctl -x /dev/sda'.
>
>
> Please note that the above is not Cygwin specific as it applies to both
> (Cygwin and Mingw-w64) Windows builds of smartctl. Use this ML for
> related support requests:
> https://listi.jpberlin.de/mailman/listinfo/smartmontools-support
>
>
>>
>> Does anyone know why? In my case, this actually matters because I'm
>> not sure how to elevate and/or drop privileges in Cygwin, as sudo
>> doesn't work due to it not being Unixy underneath.
>
> To drop privileges, try 'cygdrop' tool from 'cygutils-extra' package.
>
>
Thanks.
I can confirm that this only seems to be an issue in QEMU - it's a disk
controller and/or driver issue as you suggested it might be.
cygdrop will hopefully resolve my issue.
Hamish
prev parent reply other threads:[~2022-09-26 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 9:11 Hamish McIntyre-Bhatty
2022-09-13 11:46 ` Hamish McIntyre-Bhatty
2022-09-13 17:23 ` Christian Franke
2022-09-26 14:26 ` Hamish McIntyre-Bhatty [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=eed7c579-ef6f-1e25-7a39-a8010c801e6e@hamishmb.com \
--to=cygwin@hamishmb.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).