From nobody Sat Apr 15 05:33:15 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 4Pz26L2Y3zz45Zy9 for ; Sat, 15 Apr 2023 05:33:30 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.kundenserver.de", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pz26K1Crbz3k3G for ; Sat, 15 Apr 2023 05:33:28 +0000 (UTC) (envelope-from freebsd@edvax.de) Authentication-Results: mx1.freebsd.org; none Received: from r56.edvax.de ([178.5.230.5]) by mrelayeu.kundenserver.de (mreue106 [212.227.15.183]) with ESMTPA (Nemesis) id 1N8XDT-1qRaCj0vT7-014VrL; Sat, 15 Apr 2023 07:33:16 +0200 Date: Sat, 15 Apr 2023 07:33:15 +0200 From: Polytropon To: freebsd@dreamchaser.org Cc: FreeBSD Mailing List Subject: Re: frequent disk error, need guidance Message-Id: <20230415073315.7adfdddd.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:ppGodkiTCVXIfUb9gSPYkiUzf74cDXMP9FRO3z14mA5YPvka39V WWI/uI6f/LHEOFwanyhDZRjUpZjkX24SEpk0oo+AoR5Q4NmW7vweD8cmNiCSOIk4V4KIIVX 6hkAUREEXDUhzo38tPAE2JJLeiL4+7XZyWYabOGpHYtN8Z87RrmjeIC+5t9l59USszXN0O9 X8W8n//VX+3hPRyfQA4fA== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:cJ/7tw15MKg=;ZjhzLWu6X67XNZkKRSJwoiIDH+/ +ZpWx+g71t8idJEn81OLizAc+sU0bDqt0IEbJEEj6AL+7Vy7jSoicr0aKdXqAalhhg7GGNq3b Z2eK2mP9Qc04C0NpOZbnqdOCjoMg4e2bh2mjVg2stgrV3EnaLkSirSxLo6Dfk67do+0Hpbn3R 9eD3SH3Fsw1yowaoTCiEfzvZkW3Wc9JNS0uZzVWF7Pl6DDiL73VogKkYG5jHJljpotEi0XSMO 4aFSzdEDei2Vxlcm+/XbEwVaJQNzkHHaQAWUlWM7PqJYMcyoHWwJbalDpr8ixO4TL6wFftNjk 0XsvTdNwzer2LGoj2GpTo4tk9bXwZfmsbtj6nOglibPBsVKOgqyhk4sFkyq3JtAoyz88SIQDI oRviDR+gO5VH6yYd3y/7Ufg52qPuhXAj/VQMgBuVCpjUe6SnOh/V4Pf31bES6BrvzNew/kj2o lrtV2CzgRv8oIa0oTVtY4hTxr4JhS1hdWTr7aRRkbkzrv+/T/8okT8t6e7+LNRvs4vH7dEpPX 0NEEcezApptaKmVCD+nLk7BuuegvQ3Yah8QU2JoR+/aFzSmWpPjrF0/PeS1mp7cFL25zRDQqj W+U8SvNu02Y1z7K9l+F4KshqF+1fJqP6q6Iqr6TkXnQKGrKFUsBORsjGxxj2mfIIRKyKnwLrs O2CRfewK8XC/aWuARQdk0nB2/A0Vie4tSioF6m9aug== X-Rspamd-Queue-Id: 4Pz26K1Crbz3k3G X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8560, ipnet:217.72.192.0/20, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Fri, 14 Apr 2023 20:53:05 -0700, 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=12474351616, length=32768)]error = 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=long /dev/ada0 > # smartctl --log=selftest /dev/ada0 > Num Test_Description Remaining LBA_of_1st_error > 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. Probably too many bad blocks. The disks's firmware will remap defective blocks to spare ones, and as soon as you receive errors on OS level, it ran out of spare blocks. This means it is not the beginning of a problem, but the problem now is significant, and the disk probably has arrived its end of life. There is another option: Check all cables. Power to be sure, but data is most important. In worst case, try replacing the data cable. Check that it sits as inteded on both sides. Yes - sometimes it is that simple. ;-) > 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? As I said, the disk will do that by itself, internally. However, you _can_ use the "badblocks" utility for diagnostics, along with "smartctl" (SMARTmon tools). On OS level, you cannot really fix hardware problems though. Anyway: Make sure to backup your data and prepare to replace the disk, it's probably the safest thing to do (after you've ruled out bad cabling, that is). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...