From owner-freebsd-questions@FreeBSD.ORG  Sun Mar 16 05:28:32 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 24C205D3
 for <freebsd-questions@freebsd.org>; Sun, 16 Mar 2014 05:28:32 +0000 (UTC)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com
 [IPv6:2607:f8b0:400e:c03::235])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id F1368F74
 for <freebsd-questions@freebsd.org>; Sun, 16 Mar 2014 05:28:31 +0000 (UTC)
Received: by mail-pa0-f53.google.com with SMTP id ld10so4337313pab.40
 for <freebsd-questions@freebsd.org>; Sat, 15 Mar 2014 22:28:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=hDE1ZNJ4+uYiPg3tEEtQa4EkbmIE05w0Hw0EqGjL0Pw=;
 b=GAr/eKDz2+mvoieFNJd4qZ7JRRa6MRcma6QK6RyEWuK0fiKVAn0CwHtrbQScOW9W42
 MGjESlu1rNrbYsva0/YwRWK5Q0PDIi6QIlQ6PsIoq+8O2w8l+BCa0oBEe+8yoU11EnJY
 /jFXdUskkzvt4ICKc2R0Igp6RpDsFiWjwFoMJ0ONFC8X/J14jCLwuaITL39GT6Llm1Ds
 MTwR/JMX5MNbbt5VnyVAD091fqvTd4PEp1LgoQCNcVbFIPGWW7PnhxKAT03XnIk1qF9n
 s/+z1sz5iH/5/xVUzP2HSfjkwiZ02hxRr1sVT7pCXn/0+ZPDHJe4QQaxsDtSFMKd5BIR
 UW4Q==
MIME-Version: 1.0
X-Received: by 10.67.5.7 with SMTP id ci7mr18099993pad.99.1394947711335; Sat,
 15 Mar 2014 22:28:31 -0700 (PDT)
Received: by 10.68.157.73 with HTTP; Sat, 15 Mar 2014 22:28:31 -0700 (PDT)
In-Reply-To: <20140316130936.3f2d18e0@X220.alogt.com>
References: <CAPYfQ9z-YUzKDAh3=V3_m1wmDtds4NzcewTq0wLUD9LWt3VaGA@mail.gmail.com>
 <20140316130936.3f2d18e0@X220.alogt.com>
Date: Sun, 16 Mar 2014 00:28:31 -0500
Message-ID: <CAPYfQ9ycxEr+-qPBC6qY6tvLrTMqT3guU+8q+bK2_RAj=WH1tw@mail.gmail.com>
Subject: Re: Another case of the vanishing disk
From: cruxpot <cruxpot@gmail.com>
To: Erich Dollansky <erichsfreebsdlist@alogt.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Mar 2014 05:28:32 -0000

All four disks have similar smartctl stats as far as those alarms go.
Are you trying to tell me that all four of my disks are about to die?
The sudden crashes have already been happening.

On Sun, Mar 16, 2014 at 12:09 AM, Erich Dollansky
<erichsfreebsdlist@alogt.com> wrote:
> Hi,
>
> get a new disk as fast as possible.
>
> On Sat, 15 Mar 2014 23:48:58 -0500
> cruxpot <cruxpot@gmail.com> wrote:
>
>> messages:Mar 13 03:03:11 bsdbox kernel: ata4: port is not ready
>> (timeout 15000ms) tfd = 0000ffff
>
> First alarm bell is on.
>
>> UPDATED  WHEN_FAILED RAW_VALUE
>>   1 Raw_Read_Error_Rate     0x000f   100   099   006    Pre-fail
>> Always       -       1476032
>
> Second alarm bell.
>
>>   7 Seek_Error_Rate         0x000f   078   060   030    Pre-fail
>> Always       -       64570250
>
> Third alarm bell.
>
>>   9 Power_On_Hours          0x0032   077   077   000    Old_age
>> Always       -       20524
>
> Warranty should be still on then.
>
>> 188 Command_Timeout         0x0032   100   097   000    Old_age
>> Always       -       50
>
> Fourth alarm bell.
>
>> 195 Hardware_ECC_Recovered  0x001a   037   004   000    Old_age
>> Always       -       1476032
>
> I think I cannot count that far.
>
> A disk with raw errors is not dead yet but it is a clear sign that
> something is wrong. Be prepared for a sudden crash.
>
> Erich