From: Emmanuel Florac <eflorac@intellique.com>
To: Dragon <Sunghost@gmx.de>
Cc: xfs@oss.sgi.com
Subject: Re: XFS Filesystem is broken and cant repair and mount!
Date: Fri, 10 Oct 2014 12:17:11 +0200 [thread overview]
Message-ID: <20141010121711.5ca3ce44@harpe.intellique.com> (raw)
In-Reply-To: <trinity-439c7424-8997-4a12-ad12-2c1aa0e49227-1412930857944@3capp-gmx-bs24>
Le Fri, 10 Oct 2014 10:47:38 +0200
Dragon <Sunghost@gmx.de> écrivait:
> buffer i/o error on device md2
This is an error from md2. Probably bad hardware.
I'm looking at your past messages and see this:
[ 184.894882] ata1: exception Emask 0x10 SAct 0x0 SErr 0x90202 action
0xe frozen
[ 184.895036] ata1: irq_stat 0x00400000, PHY RDY changed
[ 184.895142] ata1: SError: { RecovComm Persist PHYRdyChg 10B8B }
[ 184.895266] ata1: hard resetting link
[ 191.412128] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 191.416411] ata1.00: configured for UDMA/133
[ 191.416425] ata1: EH complete
[ 193.180043] ata1.00: exception Emask 0x10 SAct 0x40000 SErr 0x90202
action 0xe frozen
[ 193.180218] ata1.00: irq_stat 0x00400000, PHY RDY changed
[ 193.180329] ata1: SError: { RecovComm Persist PHYRdyChg 10B8B }
[ 193.180455] ata1.00: failed command: READ FPDMA QUEUED
[ 193.180567] ata1.00: cmd 60/60:90:00:00:b9/00:00:03:00:00/40 tag 18
ncq 49152 in
[ 193.180570] res 40/00:90:00:00:b9/00:00:03:00:00/40 Emask
0x10 (ATA bus error)
[ 193.180862] ata1.00: status: { DRDY }
[ 193.180942] ata1: hard resetting link
[ 199.716173] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 199.717582] ata1.00: configured for UDMA/133
[ 199.717610] ata1: EH complete
This isn't normal. This shouldn't happen. Something doesn't look right
in your SATA setup. Check your cables, update your mobo BIOS...
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-10 10:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 8:47 XFS Filesystem is broken and cant repair and mount! Dragon
2014-10-10 10:17 ` Emmanuel Florac [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-12 20:54 Dragon
2014-10-12 20:56 ` Eric Sandeen
2014-10-12 22:16 ` Dave Chinner
2014-10-12 20:26 Dragon
2014-10-12 20:39 ` Eric Sandeen
2014-10-10 10:28 Dragon
2014-10-09 22:42 Dragon
2014-10-10 10:07 ` Emmanuel Florac
2014-10-09 21:37 Dragon
2014-10-09 21:48 ` XFS " Dave Chinner
2014-10-09 13:15 Dragon
2014-10-09 15:09 ` Eric Sandeen
2014-10-09 21:20 ` Dave Chinner
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=20141010121711.5ca3ce44@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=Sunghost@gmx.de \
--cc=xfs@oss.sgi.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