Date: Thu, 3 Sep 2009 11:21:03 +0200 From: "Daniel Eriksson" <daniel@toomuchdata.se> To: <freebsd-questions@freebsd.org> Cc: Mark Stapper <stark@mapper.nl> Subject: RE: ZFS and DMA read error Message-ID: <4F9C9299A10AE74E89EA580D14AA10A635E9C3@royal64.emp.zapto.org> In-Reply-To: <4A9CBDBB.3060403@mapper.nl> References: <4A9B731E.9050400@mapper.nl><ade45ae90908311122s685a6aa7o6dcc49a48c08000e@mail.gmail.com> <4A9CBDBB.3060403@mapper.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Stapper wrote:
> People are REALLY pushing spinrite lately... I did get it though, just
to try it.
SpinRite is OK but it hasn't been updated in ages. It does not work on
large drives. 250GB works, 1TB does not. Haven't tried it on 500GB
drives.
If I were you I would 'zpool offline ...' the offending drive, rewrite
the entire drive with 'dd if=3D/dev/zero ...' and then run a SMART
selftest on it using smartmontools ('smartctl -t long /dev/adX'). When
you 'zpool online ...' the drive ZFS will resilver it for you. After
doing all of this I would then run a 'zpool scrub ...'. If the scrub
finishes without checksum errors and without any ATA-related errors the
drive is probably in good enough condition to keep using, but watch out
for more ATA errors. If the drive is dying it won't be long before it
starts to generate more ATA errors.
/Daniel Eriksson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F9C9299A10AE74E89EA580D14AA10A635E9C3>