Date: Thu, 01 Jul 2004 19:32:27 -0400 From: Vladimir Zhurov <vzhurov@uwo.ca> To: freebsd-stable@freebsd.org Subject: Re: dscheck(#ar/2): negative b_blkno error on FreeBSD-4.10-STABLE - SOLVED Message-ID: <40E49F0B.5010005@uwo.ca> In-Reply-To: <20040630190707.T66769@carver.gumbysoft.com> References: <40DEDCD2.3020606@uwo.ca> <20040628172309.D43333@carver.gumbysoft.com> <40E31C35.9020307@uwo.ca> <20040630190707.T66769@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you for suggestions. Finally, I have solved the problem. It was in fact hardware failure. One of the drives in array failed (despite the "no error found" verdict of WD DLG utility). I discovered it by deleting array and initializing drives individually. But it raises another question. Obviously fsck was right reporting errors, atacontrol and WD DLG were wrong reporting that everything was fine (I am not sure that atacontrol is designed to detect such errors anyway), but how would one figure out which drive failed in such a case without actually going into complete re-formating of array? Vlad.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40E49F0B.5010005>