Date: Mon, 1 Oct 2007 15:07:12 -0500 From: "Dan Borello" <dborello@uiuc.edu> To: freebsd-current@freebsd.org Subject: Accessing bad hard drive causes panic Message-ID: <b10a8f1a0710011307w7b6b1d06j63617601256f1e7d@mail.gmail.com> In-Reply-To: <b10a8f1a0710011236y6340a8car413058f4dd4919d6@mail.gmail.com> References: <b10a8f1a0710011236y6340a8car413058f4dd4919d6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
A few months ago I installed 7.0-CURRENT in order to migrate to zfs. At the time when I was copying files from a geo concat volume to the zfs pool the server would freeze (unresponsive to pings). I figured this was the nature of CURRENT and moved on. Yesterday I recompiled the kernel from the latest source and the issue persists. The issue is that one of the old drives is experiencing a hardware failure. When ever it is accessed (from geo concat or added to the zfs pool and scurbed) the server freezes, requiring a power cycle. I know that current isn't for the average user, which I am. But I figured I would report this and am willing to help diagnose the issue. The drive passes SMART selftests and returns healthy status, but has reported over 500 errors. I am going to send the drive in for replacement soon. Let me know what I can do to help. -Dan -- Dan Borello dborello@uiuc.edu Structural Engineering Graduate Student University of Illinois - Urbana Champaign P: 847-877-6287
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b10a8f1a0710011307w7b6b1d06j63617601256f1e7d>