All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: IW News <news@imagedworld.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: SAS disk from RAID card (no RAID mode) problems
Date: Fri, 23 Dec 2016 09:21:35 -0500	[thread overview]
Message-ID: <wrfja8bmiv4g.fsf@redhat.com> (raw)
In-Reply-To: <2326bdf0-2948-5cbf-3033-27ed41803e23@imagedworld.com> (IW News's message of "Fri, 23 Dec 2016 09:01:40 +0100")

IW News <news@imagedworld.com> writes:
> Hello,
>
> First message here.
>
> After looking for a solution without any luck I have found this
> list. I hope someone can help me with this.
>
> I have an ASUS P6T Deluxe with a MARVELL 88SE63xx SAS RAID controller.
> There are to identical 400GB SAS SSD drives attached to it. One of
> them has a Windows 10 installation, the other one Linux.
> Grub is installed on the second disk.
>
> Windows works as expected, but I have problems with the Linux
> installation: the desktop environment freezes for some second once in
> a while. This occurs with Mint Cinnamon, OpenSuSe KDE, Ubuntu and
> Manjaro KDE. All of them are current installations. I'm now working in
> up to date Manjaro KDE (kernel 4.9.0).
> When the temporary freezes occur the mouse pointer moves, some windows
> are updated correctly, other do not and DE stops working.
> When this happens always I have a system log like this:
>
> ______________________________________________________
> 23/12/16 8:29    kernel    sas: Enter sas_scsi_recover_host busy: 6
> failed: 6
> 23/12/16 8:29    kernel    sas: trying to find task 0xffff8bda8d2bd900
> 23/12/16 8:29    kernel    sas: sas_scsi_find_task: aborting task
> 0xffff8bda8d2bd900
> 23/12/16 8:29    kernel    sas: task done but aborted
> 23/12/16 8:29    kernel    sas: sas_scsi_find_task: task
> 0xffff8bda8d2bd900 is done
> 23/12/16 8:29    kernel    sas: sas_eh_handle_sas_errors: task
> 0xffff8bda8d2bd900 is done
[snip]
> Sometimes shorter sometimes larger.
> It looks like a controller/drive/cable problem?
> Any thoughts?

Doesn't look like a Linux RAID issue, but much more like a driver
problem. Possibly caused by cables or controller issues.

You probably want to reach out to the linux-scsi list.

Jes

  reply	other threads:[~2016-12-23 14:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23  8:01 SAS disk from RAID card (no RAID mode) problems IW News
2016-12-23 14:21 ` Jes Sorensen [this message]
     [not found]   ` <CAFCYAseg=UJbRpXp=miq+nmydkrMfd+xG2rUEWrmrG9OjR_ZgA@mail.gmail.com>
     [not found]     ` <3695b4a6-e221-9081-b8e7-756047d6bb39@imagedworld.com>
     [not found]       ` <CAFCYAse2Bq3dYXDrmC6dxdh4L435552crv2sDuZDb3pngZi8=A@mail.gmail.com>
2016-12-24  7:49         ` IW News
2016-12-26 18:55           ` Andrew Ryder
2016-12-26 21:25 ` Thomas Fjellstrom
     [not found]   ` <ed04b869-cc0f-b099-95a8-fc1ce08a1427@imagedworld.com>
2016-12-27  8:01     ` Fwd: " IW News
2017-01-05 16:41       ` Emmanuel Florac
     [not found]     ` <2822438.YHxX6ucKrv@natasha>
2016-12-27 16:57       ` IW News
2016-12-27 17:09         ` Joe Landman
2016-12-28  1:06           ` Thomas Fjellstrom
2016-12-28 21:28           ` John Stoffel
     [not found] <S1758417AbcLWSxj/20161223185339Z+7534@vger.kernel.org>
2016-12-23 18:59 ` IW News

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=wrfja8bmiv4g.fsf@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=news@imagedworld.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 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.