Disk problems?
Ted Mittelstaedt
tedm at toybox.placo.com
Fri May 11 16:46:34 UTC 2007
check to see if the drive mfgr has a firmware update for your disks
Ted
> -----Original Message-----
> From: owner-freebsd-questions at freebsd.org
> [mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Jack Barnett
> Sent: Wednesday, May 09, 2007 1:15 AM
> To: freebsd-questions at 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 <jackbarnett at gmail.com> 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 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
>
More information about the freebsd-questions
mailing list