linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Nathan Peterson <nathan@uwgrads.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Unable to mount an ext4 RAID6 array
Date: Thu, 18 Oct 2018 20:18:49 -0400	[thread overview]
Message-ID: <20181019001849.GC2407@thunk.org> (raw)
In-Reply-To: <CAAQ4vX3a5RrD_Dt7tFJ23cof=FAK3fd5jrF+c45YujbjwNcKmw@mail.gmail.com>

Hi,

Sorry I didn't get back to you sooner.  This e-mail thread got lost in
my inbox, so thanks for pinging me about it.

These lines in the logs clearly show that it is a hardware problem.
It could be an issue with the SATA controller, or cables, or even
something in the motherboard.

[  +0.000006] ata1: irq_stat 0x00400040, connection status changed
[  +0.000004] ata1: SError: { HostInt PHYRdyChg 10B8B DevExch }
[  +0.000005] ata1: hard resetting link
[  +5.634542] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  +0.001809] ata1.00: configured for UDMA/133
[  +0.000003] ata1: EH complete
[Sep13 19:47] ata1: exception Emask 0x50 SAct 0x0 SErr 0x4090800

The following article (found via Google) on Serverfault might be
helpful:

https://serverfault.com/questions/749433/hard-resetting-link-exception-emask-0x50-sact-0x0-serr-0x4090800-action-0xe-froz

Good luck,

					- Ted

  reply	other threads:[~2018-10-19  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAQ4vX2wrzxzP6=bP9Bbt89Hvs_JRJuZxSQGfPw2vUrtOqh3UA@mail.gmail.com>
     [not found] ` <20180913223252.GD30588@thunk.org>
     [not found]   ` <CAAQ4vX2nujND+s7mK-3EztS+MtLeNsNgmd=kwFQmVSa1ABjrKQ@mail.gmail.com>
2018-10-18 19:43     ` Unable to mount an ext4 RAID6 array Nathan Peterson
2018-10-19  0:18       ` Theodore Y. Ts'o [this message]
2019-01-16 18:48         ` Nathan Peterson

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=20181019001849.GC2407@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=nathan@uwgrads.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).