From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: IW News <news@imagedworld.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: SAS disk from RAID card (no RAID mode) problems
Date: Mon, 26 Dec 2016 14:25:11 -0700 [thread overview]
Message-ID: <1567104.jAPptYD2GZ@natasha> (raw)
In-Reply-To: <2326bdf0-2948-5cbf-3033-27ed41803e23@imagedworld.com>
On Friday, December 23, 2016 9:01:40 AM MST IW News wrote:
> 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:
If thats the mvsas driver, god help you. I had nothing but troubles with it
for a good year or two or possibly more and it was never fixed or really
acknowledged, so I sold that card (a supermicro aoc-saslp-mv8) and picked up a
IBM m1015 (LSI 9211-8i a-like) and haven't looked back.
Basically it would reset a lot, and lock up. AND I believe it caused a lot of
silent corruption as well.
> ______________________________________________________
> 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
> 23/12/16 8:29 kernel sas: trying to find task 0xffff8bda8d2bce00
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: aborting task
> 0xffff8bda8d2bce00
> 23/12/16 8:29 kernel sas: task done but aborted
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: task
> 0xffff8bda8d2bce00 is done
> 23/12/16 8:29 kernel sas: sas_eh_handle_sas_errors: task
> 0xffff8bda8d2bce00 is done
> 23/12/16 8:29 kernel sas: trying to find task 0xffff8bda8d2bd700
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: aborting task
> 0xffff8bda8d2bd700
> 23/12/16 8:29 kernel sas: task done but aborted
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: task
> 0xffff8bda8d2bd700 is done
> 23/12/16 8:29 kernel sas: sas_eh_handle_sas_errors: task
> 0xffff8bda8d2bd700 is done
> 23/12/16 8:29 kernel sas: trying to find task 0xffff8bda8d2bde00
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: aborting task
> 0xffff8bda8d2bde00
> 23/12/16 8:29 kernel sas: task done but aborted
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: task
> 0xffff8bda8d2bde00 is done
> 23/12/16 8:29 kernel sas: sas_eh_handle_sas_errors: task
> 0xffff8bda8d2bde00 is done
> 23/12/16 8:29 kernel sas: trying to find task 0xffff8bda8d2bdc00
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: aborting task
> 0xffff8bda8d2bdc00
> 23/12/16 8:29 kernel sas: task done but aborted
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: task
> 0xffff8bda8d2bdc00 is done
> 23/12/16 8:29 kernel sas: sas_eh_handle_sas_errors: task
> 0xffff8bda8d2bdc00 is done
> 23/12/16 8:29 kernel sas: trying to find task 0xffff8bdcb0298800
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: aborting task
> 0xffff8bdcb0298800
> 23/12/16 8:29 kernel sas: task done but aborted
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: task
> 0xffff8bdcb0298800 is done
> 23/12/16 8:29 kernel sas: sas_eh_handle_sas_errors: task
> 0xffff8bdcb0298800 is done
> 23/12/16 8:29 kernel sas: --- Exit sas_scsi_recover_host: busy: 0
> failed: 6 tries: 1
> 23/12/16 8:29 kernel drivers/scsi/mvsas/mv_sas.c 1694:reuse same
> slot, retry command.
> 23/12/16 8:29 kernel drivers/scsi/mvsas/mv_sas.c 1694:reuse same
> slot, retry command.
> 23/12/16 8:29 kernel drivers/scsi/mvsas/mv_sas.c 1694:reuse same
> slot, retry command.
> 23/12/16 8:29 kernel sas: Enter sas_scsi_recover_host busy: 2
> failed: 2
> 23/12/16 8:29 kernel sas: trying to find task 0xffff8bdb9453ae00
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: aborting task
> 0xffff8bdb9453ae00
> 23/12/16 8:29 kernel sas: task done but aborted
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: task
> 0xffff8bdb9453ae00 is done
> 23/12/16 8:29 kernel sas: sas_eh_handle_sas_errors: task
> 0xffff8bdb9453ae00 is done
> 23/12/16 8:29 kernel sas: trying to find task 0xffff8bdb9453b000
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: aborting task
> 0xffff8bdb9453b000
> 23/12/16 8:29 kernel sas: task done but aborted
> 23/12/16 8:29 kernel sas: sas_scsi_find_task: task
> 0xffff8bdb9453b000 is done
> 23/12/16 8:29 kernel sas: sas_eh_handle_sas_errors: task
> 0xffff8bdb9453b000 is done
> 23/12/16 8:29 kernel sas: --- Exit sas_scsi_recover_host: busy: 0
> failed: 2 tries: 1
> ____________________________________________________________________________
> ______________
>
> Sometimes shorter sometimes larger.
> It looks like a controller/drive/cable problem?
> Any thoughts?
>
> Thanks in advance.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Thomas Fjellstrom
thomas@fjellstrom.ca
next prev parent reply other threads:[~2016-12-26 21:25 UTC|newest]
Thread overview: 9+ 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
[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 [this message]
[not found] ` <ed04b869-cc0f-b099-95a8-fc1ce08a1427@imagedworld.com>
[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
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=1567104.jAPptYD2GZ@natasha \
--to=thomas@fjellstrom.ca \
--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 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).