public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 205107] No HDD spindown/parking on shutdown
Date: Fri, 17 Jan 2020 23:14:21 +0000	[thread overview]
Message-ID: <bug-205107-11633-41xW8TZM6z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205107-11633@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=205107

--- Comment #11 from Kaur Männamaa (kaurman@outlook.com) ---
(In reply to Hélder from comment #9)


> If I umount  but do not unplug the HDD, the problem does not occur.
> 

I contacted Mark Lord, the main dev behind hdparm, and he had some thoughts.
Among other things, he asked us to clarify whether just unmounting (instead of
unmounting and powering off, e.g. by using 'udisksctl power-off ...') the drive
before shutdown really solves the problem. I'm asking as 'unplugging' can be
misinterpreted and that could lead to misunderstandings. In short, does the
problem occur if you unmount the drive, and then just shut down your computer?
And don't forget to disable your script while testing :)

In my case shutting down with an unmounted drive did not solve the problem. If
it does indeed work in your case then we may have different scenarios here.
Mark had other ideas as well but I'd like to clear the unmounting part up first
to plan the next steps better.


Kaur

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-01-17 23:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-06 23:18 [Bug 205107] New: No HDD spindown/parking on shutdown bugzilla-daemon
2019-10-10  3:49 ` [Bug 205107] " bugzilla-daemon
2019-10-11 23:31 ` bugzilla-daemon
2019-10-11 23:32 ` bugzilla-daemon
2019-10-11 23:35 ` bugzilla-daemon
2019-10-11 23:45 ` bugzilla-daemon
2019-10-18 20:16 ` bugzilla-daemon
2019-10-18 20:51 ` bugzilla-daemon
2019-10-18 21:38 ` bugzilla-daemon
2020-01-06 21:31 ` bugzilla-daemon
2020-01-16 22:37 ` bugzilla-daemon
2020-01-17 14:20 ` bugzilla-daemon
2020-01-17 23:14 ` bugzilla-daemon [this message]
2020-01-18 23:39 ` bugzilla-daemon
2020-01-18 23:45 ` bugzilla-daemon
2020-01-18 23:47 ` bugzilla-daemon
2020-01-19  0:27 ` bugzilla-daemon
2020-02-04  1:41 ` bugzilla-daemon
2020-11-09 22:18 ` bugzilla-daemon
2020-11-09 22:33 ` bugzilla-daemon
2020-11-09 22:34 ` bugzilla-daemon
2020-11-09 22:39 ` bugzilla-daemon
2020-12-23 11:46 ` bugzilla-daemon
2024-11-13 11:53 ` bugzilla-daemon
2024-11-13 12:28 ` bugzilla-daemon

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=bug-205107-11633-41xW8TZM6z@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ide@vger.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