From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 151631] "Synchronizing SCSI cache" fails during(and delays) reboot/shutdown
Date: Sun, 07 Aug 2016 00:29:48 +0000 [thread overview]
Message-ID: <bug-151631-11613-qbaktU4wLc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-151631-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=151631
--- Comment #3 from icanrealizeum <icanrealizeum+bugzillakernelorg@gmail.com> ---
Ok, now that the cache error doesn't happen and reboot works, I've tested
shutdown and it now fails at the "Stopping disk" part, which means this line:
sd_start_stop_device(sdkp, 0);
ata4.00: failed command: STANDBY IMMEDIATE
screenshot: https://i.imgur.com/2yvAMSR.jpg
So now we know that it did in fact not safely shutdown the drive before, when I
thought it's just the drive cache flushing that failed. So the drive is doing
recovery, internally, upon laptop poweron which is why it doesn't identify
itself in time but only on next ctrl+alt+del boot. (see comment #1)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-08-07 0:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 17:17 [Bug 151631] New: "Synchronizing SCSI cache" fails during(and delays) reboot/shutdown bugzilla-daemon
2016-08-06 19:20 ` [Bug 151631] " bugzilla-daemon
2016-08-06 19:57 ` bugzilla-daemon
2016-08-07 0:29 ` bugzilla-daemon [this message]
2016-08-07 15:06 ` bugzilla-daemon
2016-08-07 15:06 ` bugzilla-daemon
2016-11-08 8:11 ` bugzilla-daemon
2016-11-10 6:54 ` bugzilla-daemon
2016-12-04 20:22 ` bugzilla-daemon
2016-12-04 20:26 ` bugzilla-daemon
2017-01-17 20:29 ` bugzilla-daemon
2017-01-17 20:56 ` bugzilla-daemon
2024-01-04 11:45 ` bugzilla-daemon
2024-01-22 8:40 ` 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-151631-11613-qbaktU4wLc@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).