From nobody Sat Apr 15 03:57:01 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PyzzG66cnz45R6p for ; Sat, 15 Apr 2023 03:57:14 +0000 (UTC) (envelope-from pprocacci@gmail.com) Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PyzzG3TC1z4dF6 for ; Sat, 15 Apr 2023 03:57:14 +0000 (UTC) (envelope-from pprocacci@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oi1-x229.google.com with SMTP id p133so3635790oih.2 for ; Fri, 14 Apr 2023 20:57:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681531033; x=1684123033; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=nWyw7Mv0rYIbeVQXf+py0p1hQZzqrTULM+DraFmDYWE=; b=EHyBGL5uNym1WXY0NSnJgroDRroGtJr2ax5AxjXvbWdESoPM42Va6n56A/lSfdKj6X cSTsqk6A2Zvi5HgNzsl1uwZAOUNDzaT+Q42mIXuWPZd15rM9SMUrHs/fjLjrq/w2seHL J55p6OO8XoQZUSC2/YuhiaVxv3OwfXTBLWDbqJtPrK8BiXINzsdSj6D+Y4d4HEjkfut6 R/3YXtpSPmwXpvdaTpkI0ku28p1YeSwYTk/UnnASU6HXIBtKoxlVWcBLwTYu3UkNlDWo SUGy5Jf0pWPjH81Bj8t3AvCPr4I9yR6yQv1HdrNgQavZaRGN8cUnZqO0/aZF/1y64pUi zlyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681531033; x=1684123033; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=nWyw7Mv0rYIbeVQXf+py0p1hQZzqrTULM+DraFmDYWE=; b=DVl7oQBMm9vWIb+fBb1txJgNoVO1f0SrTOlUTtf+1uQ3luKekHhKH5WHSAFYPp2NEZ b60z8efoS2T7x+RugcMLuGTDdB4Ielqe3IKWUZaJQzFxwgddADrVjZsSrqCgaoWWwEoh N4wJbI/okUSjBRPtCJE+DmQmNgDxxUx6T51aFQNqRMZlnaIpoIDFzfCzXTVIXVkMpnhC fFIvsAo4D3UdaOuEWp6KCKlF0aaKgnFyTKGsJWm6O9HwayxGKwshC5fqE7FRZFkvnI2a dZcE35lwoC018ILkYsvDpkiXrRtf17u2I1/mA+1F7f9bYtfKg52NT2/cCn2onNIdRhdE 7I8w== X-Gm-Message-State: AAQBX9eINnsbdIQ4aBOtZNtvzjJXS8uAsjFFalwdTyjEbb0Ve042/zlv Wzk6ciFD5ChhoRIFQlIsmIz+902xiU9RWKoHJTUI5Og+NA== X-Google-Smtp-Source: AKy350ZZE2eE0C5u0rpJarPSz1BHvzjGvluYKir59j4C0NAImV6pGPfrlRICYGk8p+c1ohpQE8Gh3zZqgtQ1f955fJM= X-Received: by 2002:a05:6808:3a96:b0:38b:2521:7b08 with SMTP id fb22-20020a0568083a9600b0038b25217b08mr1624621oib.6.1681531033448; Fri, 14 Apr 2023 20:57:13 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Paul Procacci Date: Fri, 14 Apr 2023 23:57:01 -0400 Message-ID: Subject: Re: frequent disk error, need guidance To: freebsd@dreamchaser.org Cc: FreeBSD Mailing List Content-Type: multipart/alternative; boundary="000000000000ed775005f957f354" X-Rspamd-Queue-Id: 4PyzzG3TC1z4dF6 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000ed775005f957f354 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Apr 14, 2023 at 11:54=E2=80=AFPM Gary Aitken wrote: > I'm seeing a boatload of the same error: > (ada0:ata2:0:0:0): READ_DMA. ACB: c8 00 e2 c7 73 41 00 00 00 00 40 00 > (ada0:ata2:0:0:0): CAM status: ATA Status Error > (ada0:ata2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC ) > (ada0:ata2:0:0:0): RES: 51 40 e7 c7 73 01 01 00 00 00 00 > (ada0:ata2:0:0:0): Retrying command, 3 more tries remain > repeated, with occasional: > g_vfs_done():ada0p2[READ(offset=3D12474351616, length=3D32768)]error = =3D 5 > > # smartctl --info /dev/da0 > Model Family: Seagate Barracuda 7200.9 > Device Model: ST3808110AS > Serial Number: 4LR1HW1E > Firmware Version: 3.ADH > User Capacity: 80,000,000,000 bytes [80.0 GB] > Sector Size: 512 bytes logical/physical > Device is: In smartctl database 7.3/5319 > ATA Version is: ATA/ATAPI-7 (minor revision not indicated) > Local Time is: Fri Apr 14 09:43:01 2023 MDT > SMART support is: Available - device has SMART capability. > SMART support is: Enabled > # smartctl --health /dev/da0 > SMART overall-health self-assessment test result: PASSED > > # smartctl --test=3Dlong /dev/ada0 > # smartctl --log=3Dselftest /dev/ada0 > Num Test_Description Remaining LBA_of_1st_erro= r > Status LifeTime(hours) > > # 1 Extended offline Completed: read failure 90% 7482 24365031 > # 2 Short offline Completed: read failure 90% 7482 24365031 > # 3 Short offline Completed: read failure 90% 7482 24365031 > # 4 Short offline Completed without error 00% 0 - > > So I presume a bad block/sector on the disk. > I had high hopes this article: > https://www.freebsddiary.org/smart-fixing-bad-sector.php > would show the way, but it seems to quit right at the good stuff. > > Can it be remapped, and if so, pointers to how? > > Thanks, > > Gary > > That is a hardware error. UNC means uncorrectable data error. Either you have a cable going bad or that drive is failing. Maybe it's just intermittent at this stage, but I'd look at trying a new cable/replacing that drive as the very first step. ~Paul --=20 __________________ :(){ :|:& };: --000000000000ed775005f957f354 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Apr 14, 2023 at 11:54=E2=80= =AFPM Gary Aitken <freebsd@dr= eamchaser.org> wrote:
I'm seeing a boatload of the same error:
=C2=A0 =C2=A0(ada0:ata2:0:0:0): READ_DMA. ACB: c8 00 e2 c7 73 41 00 00 00 0= 0 40 00
=C2=A0 =C2=A0(ada0:ata2:0:0:0): CAM status: ATA Status Error
=C2=A0 =C2=A0(ada0:ata2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (= UNC )
=C2=A0 =C2=A0(ada0:ata2:0:0:0): RES: 51 40 e7 c7 73 01 01 00 00 00 00
=C2=A0 =C2=A0(ada0:ata2:0:0:0): Retrying command, 3 more tries remain
repeated, with occasional:
=C2=A0 =C2=A0g_vfs_done():ada0p2[READ(offset=3D12474351616, length=3D32768)= ]error =3D 5

# smartctl --info /dev/da0
=C2=A0 =C2=A0Model Family:=C2=A0 =C2=A0 =C2=A0Seagate Barracuda 7200.9
=C2=A0 =C2=A0Device Model:=C2=A0 =C2=A0 =C2=A0ST3808110AS
=C2=A0 =C2=A0Serial Number:=C2=A0 =C2=A0 4LR1HW1E
=C2=A0 =C2=A0Firmware Version: 3.ADH
=C2=A0 =C2=A0User Capacity:=C2=A0 =C2=A0 80,000,000,000 bytes [80.0 GB]
=C2=A0 =C2=A0Sector Size:=C2=A0 =C2=A0 =C2=A0 512 bytes logical/physical =C2=A0 =C2=A0Device is:=C2=A0 =C2=A0 =C2=A0 =C2=A0 In smartctl database 7.3= /5319
=C2=A0 =C2=A0ATA Version is:=C2=A0 =C2=A0ATA/ATAPI-7 (minor revision not in= dicated)
=C2=A0 =C2=A0Local Time is:=C2=A0 =C2=A0 Fri Apr 14 09:43:01 2023 MDT
=C2=A0 =C2=A0SMART support is: Available - device has SMART capability.
=C2=A0 =C2=A0SMART support is: Enabled
# smartctl --health /dev/da0
=C2=A0 =C2=A0SMART overall-health self-assessment test result: PASSED

# smartctl --test=3Dlong /dev/ada0
# smartctl --log=3Dselftest /dev/ada0
Num=C2=A0 Test_Description=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Remaining=C2=A0 LBA_of_1st_error<= br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 Status=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 LifeTime(hours)

# 1=C2=A0 Extended offline=C2=A0 Completed: read failure=C2=A0 90%=C2=A0 74= 82=C2=A0 24365031
# 2=C2=A0 Short offline=C2=A0 =C2=A0 =C2=A0Completed: read failure=C2=A0 90= %=C2=A0 7482=C2=A0 24365031
# 3=C2=A0 Short offline=C2=A0 =C2=A0 =C2=A0Completed: read failure=C2=A0 90= %=C2=A0 7482=C2=A0 24365031
# 4=C2=A0 Short offline=C2=A0 =C2=A0 =C2=A0Completed without error=C2=A0 00= %=C2=A0 =C2=A0 =C2=A00=C2=A0 -

So I presume a bad block/sector on the disk.
I had high hopes this article:
=C2=A0 =C2=A0https://www.freebsddiary.org/sm= art-fixing-bad-sector.php
would show the way, but it seems to quit right at the good stuff.

Can it be remapped, and if so, pointers to how?

Thanks,

Gary


=09 =09 =09 =09 =09 =09 =09 =09 =09
=09 =09 =09 =09 =09 =09
That is a hardware error. UNC means=20 uncorrectable data error. Either you have a cable going bad or that=20 drive is failing.
Maybe it's just=20 intermittent at this stage, but I'd look at trying a new cable/replacin= g that drive as the very first step.
=09
=C2=A0
=09 =09 =09 =09 =09 =09
=09 =09 =09 =09 =09 =09 =09 =09 =09 =09
~Paul

-= -
__________________<= br>
:(){ :|:& };:
--000000000000ed775005f957f354--