From owner-freebsd-questions Thu May 17 0:41: 9 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 84C3837B422 for ; Thu, 17 May 2001 00:41:01 -0700 (PDT) (envelope-from tedm@toybox.placo.com) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f4H7eqk52556; Thu, 17 May 2001 00:40:53 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Bill Desjardins" Cc: Subject: RE: ida0: soft error ? Date: Thu, 17 May 2001 00:40:52 -0700 Message-ID: <001401c0dea4$b2c176c0$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal In-Reply-To: <20010516233737.X23426-100000@mail.carracing.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yep - there's nothing like getting a replacement part and sticking it in and finding out that the replacement is bad, too. You can end up on quite a wild goose chase troubleshooting that. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Bill Desjardins >Sent: Wednesday, May 16, 2001 4:50 PM >To: Ted Mittelstaedt >Cc: freebsd-questions@FreeBSD.ORG >Subject: RE: ida0: soft error ? > > >Ted, > >sorry for the late delay in getting back to this. The drive was just >swapped out as a hot replacement as it was the same size and I did not >bother with the compaq ACU. after the rebuild, I still had the same >errors and figured one more shot at a different drive just to see what >would happen. after rebuilding and rebooting, all the soft errors went >away and things are good now :) > >I suspect that the original errors with the first replacement were due to >the rebuilding process as they still occured during the last hot-swap >rebuilding phase. the first replacement drive spit out the errors >after rebuilding, and I have verified as bad since I have since built >other array configs with it on identical machines and it still shows the >same errors. the second replacement has been working flawlessly since >installation as I said with no soft errors. > >Thanks for your help. > >Bill > >-- >Bill Desjardins - bill@carracing.com - (USA) 305.205.8644 >Unix/Network Consulting - perl/mod_perl/SQL development >http://CarRacing.com - Powered by FreeBSD/mod_perl >http://www.FreeBSD.org - The Best OS money cant buy! > >On Mon, 14 May 2001, Ted Mittelstaedt wrote: > >> How did you replace it? Did you just stick it in or did you run the >> Compaq raid utility after doing this? >> >> Ted Mittelstaedt tedm@toybox.placo.com >> Author of: The FreeBSD Corporate Networker's Guide >> Book website: http://www.freebsd-corp-net-guide.com >> >> >> >-----Original Message----- >> >From: owner-freebsd-questions@FreeBSD.ORG >> >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Bill Desjardins >> >Sent: Sunday, May 13, 2001 10:10 AM >> >To: freebsd-questions@FreeBSD.ORG >> >Subject: ida0: soft error ? >> > >> > >> >Hello, >> > >> >couldnt find a good answer for this in the archives, so here goes. >> > >> >I have a copmpaq 2500 with a smart-2/p array controller and 5 9gig >> >drives. today the controller reported that one of the drives had >> >an 'iminent failure' that was going to happen to one of them. I replaced >> >that drive with another drive that has not previously given >problems, and >> >since installing it, I get tons of ida0: soft error. from what I did see >> >in the archives, a soft error appears to be when the controller tries to >> >write to the disk and is unsuccessful the first time, but a 2nd try >> >works. Is this the case? if so, is it due to the new drive >rebuilding and >> >does that error go away after the rebuilding process? If it >doesnt go away >> >after the rebuilding process, where do I look to diagnose the problem? >> > >> >I am just getting to learning and using raid so any help or >direction you >> >can give is appreciated. >> > >> >TIA, >> > >> >Bill > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message