Date: Tue, 26 Jul 2011 16:00:14 +0200 From: Andrea Venturoli <ml@netfence.it> To: freebsd-questions@freebsd.org Subject: Re: ATA troubles Message-ID: <4E2EC86E.5010401@netfence.it> In-Reply-To: <4E2CBCAB.1070209@dichotomia.fr> References: <4E2CB198.9010601@netfence.it> <4E2CBCAB.1070209@dichotomia.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/25/11 02:45, Jerome Herman wrote: > On 25/07/2011 01:58, Andrea Venturoli wrote: So, for the records... >> Now it looks like one drive is not working fine anymore... >>> Jul 24 23:48:36 mydavid kernel: ad6: FAILURE - READ_DMA48 >>> status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=1671887488 >>> Jul 24 23:48:36 mydavid kernel: >>> g_vfs_done():stripe/backup[READ(offset=1712012836864, >>> length=131072)]error = 5 >>> Jul 24 23:48:39 mydavid kernel: ad6: FAILURE - READ_DMA48 >>> status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=1671897856 >>> Jul 24 23:48:39 mydavid kernel: >>> g_vfs_done():stripe/backup[READ(offset=1712023420928, >>> length=131072)]error = 5 >>> Jul 24 23:48:41 mydavid kernel: ad6: FAILURE - READ_DMA48 >>> status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=1671897888 >>> Jul 24 23:48:41 mydavid kernel: >>> g_vfs_done():stripe/backup[READ(offset=1712023486464, >>> length=131072)]error = 5 >> Also, smartd is complaining: >>> Jul 24 23:41:59 mydavid smartd[2630]: Device: /dev/ad6, 38 Currently >>> unreadable (pending) sectors >>> Jul 24 23:50:56 mydavid smartd[538]: Device: /dev/ad6, 39 Currently >>> unreadable (pending) sectors >> >> After a reboot, I've got back to the NID_NOT_FOUND errors... Altough smartd says the drive is overall PASSing the tests, WD DLG tools found it bad. (Thanks WD for creating such good HDs that go wild in a few days...) I'll keep testing with the other one to find out whether the NID_NOT_FOUND errors are just noise in the logs or what. bye & Thanks to anyone who replied av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E2EC86E.5010401>