All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nuno Magalhães" <nunomagalhaes@eu.ipp.pt>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: SATA disks disabled on boot
Date: Tue, 02 Dec 2014 23:15:35 +0000	[thread overview]
Message-ID: <547E4817.8000603@eu.ipp.pt> (raw)
In-Reply-To: <20141202195653.GQ10918@htj.dyndns.org>


[-- Attachment #1.1: Type: text/plain, Size: 1399 bytes --]

On 2014-12-02 19:56, Tejun Heo wrote:
> Hello,
> 
> On Fri, Oct 17, 2014 at 11:02:43PM +0100, Nuno Magalhães wrote:
>> The Toshibas would hold the OS in a RAID1 while the WDs would hold data in ZFS.
>> At the moment T1 has the OS, T2 has a partition, the WDs are empty.
>>
>> My next test will be to move T2 to the bottom of the BIOS boot
>> priority, so it'll become T1, W1, W2, T2 to see if it fails.

I've ran the above tests, the results are the same: every now and then
at least one WD fails (but is recovered if i reset it, although on
occasion i hade to issue the command more than once). Today i even had
the 2 of them fail. I attach the latest results, with the following
configuration:

T1 and T2 are Toshiba DT01ACA100
W1 and W2 are Western Digital"Red" WD10EFRX

physical SATA port , BIOS order , disk
1                  , 1          , T1
2                  , 2          , W1
3                  , 4          , T2
4                  , 3          , W2

kernel parameters: libata.force=dump_id,nohrst

Next will be to move the toshibas to physical ports 3 and 4 and try again.

> If you're still working on it, can you please try to reproduce the
> failure with the debug patch applied and report the dmesg?

What debug patch is that? I assume i'd have to get libata source from
somewhere first (end user here)? Any RTFM links i can use?

Thanks,
Nuno

[-- Attachment #1.2: 02.tar.gz --]
[-- Type: application/x-gzip, Size: 109568 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-12-02 23:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 21:06 SATA disks disabled on boot Nuno Magalhães
2014-07-14 16:36 ` Tejun Heo
2014-07-14 23:24   ` Nuno Magalhães
2014-07-16 20:35     ` Nuno Magalhães
2014-07-16 20:35       ` Nuno Magalhães
2014-08-17 13:39     ` Tejun Heo
2014-08-21 22:40       ` Nuno Magalhães
2014-08-21 22:43         ` Tejun Heo
     [not found]         ` <CADqA9uaj0MrpffnzE8xnhU57Hx9pv7O1sAhB+xS_4hi8z_dkMA@mail.gmail.com>
2014-12-02 19:56           ` Tejun Heo
2014-12-02 23:15             ` Nuno Magalhães [this message]
2014-12-04 17:48               ` Tejun Heo
2014-12-04 23:59                 ` Phillip Susi
2014-12-05 22:12                   ` Nuno Magalhães
2015-01-27 23:03                     ` Nuno Magalhães
2015-01-28 14:05                       ` Phillip Susi
2015-01-29 22:04                         ` Nuno Magalhães
2015-01-30 13:53                           ` Phillip Susi
2015-02-03 19:32                             ` Nuno Magalhães
2015-02-03 19:45                               ` Phillip Susi
2015-02-09 13:02                                 ` Nuno Magalhães
2015-02-09 13:43                                   ` Phillip Susi
2015-02-09 23:52                                     ` Nuno Magalhães

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=547E4817.8000603@eu.ipp.pt \
    --to=nunomagalhaes@eu.ipp.pt \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.