From owner-freebsd-questions@FreeBSD.ORG Fri May 11 16:46:34 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 96C8B16A400 for ; Fri, 11 May 2007 16:46:34 +0000 (UTC) (envelope-from tedm@toybox.placo.com) Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [65.75.192.90]) by mx1.freebsd.org (Postfix) with ESMTP id 581C813C455 for ; Fri, 11 May 2007 16:46:34 +0000 (UTC) (envelope-from tedm@toybox.placo.com) Received: from TEDSDESK (nat-rtr.freebsd-corp-net-guide.com [65.75.197.130]) by mail.freebsd-corp-net-guide.com (8.13.8/8.13.8) with SMTP id l4BGkWM7070032; Fri, 11 May 2007 09:46:33 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Jack Barnett" , Date: Fri, 11 May 2007 09:47:26 -0700 Message-ID: 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 IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896 Importance: Normal X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (mail.freebsd-corp-net-guide.com [65.75.192.90]); Fri, 11 May 2007 09:46:33 -0700 (PDT) Cc: Subject: RE: Disk problems? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2007 16:46:34 -0000 check to see if the drive mfgr has a firmware update for your disks Ted > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Jack Barnett > Sent: Wednesday, May 09, 2007 1:15 AM > To: freebsd-questions@freebsd.org > Subject: Re: Disk problems? > > > hrm... ? > > Doing it again: > > twa0: INFO: (0x04: 0x000B): Rebuild started: unit=0 > > twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 > > twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=1 > > twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 > > twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=1 > > twa0: INFO: (0x04: 0x0005): Rebuild completed: unit=0 > > twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0 > > twa0: ERROR: (0x04: 0x0002): Degraded unit: unit=0, port=0 > > twa0: ERROR: (0x04: 0x0009): Drive timeout detected: port=1 > > twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=1 > > twa0: ERROR: (0x04: 0x000A): Drive error detected: unit=0, port=1 > > now says both disks are having problems (I removed the other two disks > and just keeping the two root drives in array unit 1): > > Unit UnitType Status %RCmpl %V/I/M Port Stripe Size(GB) > ------------------------------------------------------------------------ > u0 RAID-1 DEGRADED* - - - - 74.4951 > u0-0 DISK WARNING - - p1 - 74.4951 > u0-1 DISK DEGRADED - - p0 - 74.4951 > > > What the ? > > I tested both of these under WinXP and they come up fine. No errors, > nothing when running windows. Under FreeBSD, it throws those errors > above and then sets them degraded (and then the bios flags them on > reboot) - but if I run windows, it never flags them and everything is > fine. > > Another thing I noticed is that under FreeBSD the drives will starts > "clicking" and making god awful noises, really loud clicking like the > heads are jerking back and forth really fast. Doesn't happen in > windows, they run really quite and smooth. Is this some sort of bad > driver messing up my disks? I don't know what the hell it's doing to > my drives, but it sounds god awful... I have it booted in windows now > and it doesn't do that. I've never seen this before. > > Why does it keep clicking my drives like that and why is it throwing > errors? I've rebuild this array about a half dozen times already. > > I synced to 6.2 rel and rebuild both kernel and world, but something > doesn't seem right :( > > > > > > > > > > > > > > > > > > > > > > > > > > On 5/7/07, Jack Barnett wrote: > > > > I have a 3ware (AMCC) 9500S-4LP RAID card and 4 disks in 2 > Mirror 1 arrays: > > Unit 1: 2 x 80 gigs > > Unit 2: 2 x 400 gigs > > > > Under windows this was working fine. Both disks where > "healthy" and running (I could test this by unplugging one or the other): > > > > Under FreeBSD though, it says it's not working: > > May 7 13:57:37 fire kernel: twa0: INFO: (0x04: 0x000B): > Rebuild started: unit=0 > > May 7 13:57:37 fire kernel: twa0: INFO: (0x04: 0x000B): > Rebuild started: unit=1 > > May 7 13:57:48 fire kernel: twa0: ERROR: (0x04: 0x003A): Drive > power on reset detected: port=0 > > > > The rebuild message is fine, but keeps getting "Drive power on > reset detected: port=0" > > > > In the 3ware BIOS, it shows all drives as "active" (ie. powered > on and connected), so don't know why the kernel thinks it's > powered down? Does it mean something else? > > > > If I just "wait" for about 20 minutes, the drives start rebuilding: > > > > Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) > Cache AVrfy > > > ------------------------------------------------------------------ > ------------ > > u0 RAID-1 REBUILDING 37 - - 74.4951 > OFF OFF > > u1 RAID-1 REBUILDING 13 - - 372.519 > OFF OFF > > > > > > (it's in Unit one above, 37% complete). So even though it's > getting this "Drive power on reset detected" it eventually > rebuilds it's self. ? > > > > Any ideas what this message means? I thought it was an error, > but seems fine since it's rebuilding it's self. ? > > > > Thanks. > > > > > > > > > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" >