Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 5 Oct 2013 09:18:04 +0200
From:      "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To:        FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject:   CURRENT: (ada1:ahcich9:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 54 5e 83 40 4e 00
Message-ID:  <20131005091804.62433be1@thor.walstatt.dyndns.org>

next in thread | raw e-mail | index | archive | help
--Sig_/8dZlF=iS6iwabUiPQoHwjy=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable


On a machine running  FreeBSD 10.0-ALPHA4 #0 r256044: Fri Oct  4
11:48:43 CEST 2013 amd64 I get the follwoing message very frequently
when a small tool is extracting data stored on a ZFS JBOD comprised of
two disks:

errors: No known data errors

  pool: POOL00
 state: ONLINE
status: One or more devices has experienced an error resulting in data
        corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
        entire pool from backup.
   see: http://illumos.org/msg/ZFS-8000-8A
  scan: scrub repaired 0 in 12h8m with 1 errors on Tue Sep 24 10:34:26
  2013
config:

        NAME        STATE     READ WRITE CKSUM
        POOL00      ONLINE       0     0     5
          ada1p1    ONLINE       0     0    10  block size: 512B
        configured, 4096B native
          ada2p1    ONLINE       0     0    10  block size: 512B
        configured, 4096B native

errors: 2 data errors, use '-v' for a list

The dmesg on the eroror is:

(ada1:ahcich9:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 54 5e 83 40 4e 00
00 01 00 00 (ada1:ahcich9:0:0:0): CAM status: ATA Status Error
(ada1:ahcich9:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
(ada1:ahcich9:0:0:0): RES: 41 40 f8 5e 83 40 4e 00 00 00 00
(ada1:ahcich9:0:0:0): Retrying command


The error in the POOL00 (ZFS) seems to be sticky, since I tried to
delete the files reported corrupted, but this problem of damaged data
isn't serious and it has been for a while. What really confuses is the
new CAM related message and I'd like to ask whether this could be the
preludium of a serious hardware failure.

Thanks in advance,

Oliver

--Sig_/8dZlF=iS6iwabUiPQoHwjy=
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)

iQEcBAEBAgAGBQJST70xAAoJEOgBcD7A/5N8iVYH/RBr+gSy/6L/6eroGYGjvq8z
12+H2+9L/a6Xt97p/7negyQyQojhOUNl8GZvlR5rb46ptLBZvd8OklQdLtHYnul3
34klpcweWJTulaMgnhDJznUMEzPanvDS/2bkof/QGjAvIvYYG+qgJzbLviOIZI3p
q1AKJc0T1+4z/seEfDsAUWkbdEazaBMaP7g3MlzKqk0Q9tHav+2XaaZjwoQcJhu5
GqbwROBRR0TLRjPeb8KndhGlz21WMe3Oc4kqF4ImoWFH5zmNUJ1MgGLB8CRO66WW
YWDnFvwdQhvqeaAjR81DpCSp3XJ0tsK/+vypTKm1ASJ7o9GWIwWAlZpuwEOphOc=
=ITQG
-----END PGP SIGNATURE-----

--Sig_/8dZlF=iS6iwabUiPQoHwjy=--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131005091804.62433be1>