[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Mon Mar 1 00:34:49 2004 -->
- <!--x-from-r13: ehazna ng fcrrqsnpgbel.arg (Uert) -->
- <!--x-message-id: 000401c3ff4e$72869360$0a00a8c0@atlas -->
- <!--x-reference: 50CB86E4-6B23-11D8-A505-[email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] Software RAID Problems -->
- <li><em>date</em>: Mon Mar 1 00:34:49 2004</li>
- <li><em>from</em>: runman at speedfactory.net (Greg)</li>
- <li><em>in-reply-to</em>: <[email protected]></li>
- <li><em>subject</em>: [ale] Software RAID Problems</li>
Google gave up some links that talk about this
<a rel="nofollow" href="http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=Software+RAID+ide+cab";>http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=Software+RAID+ide+cab</a>
les&spell=1
Greg
> -----Original Message-----
> From: ale-bounces at ale.org [<a rel="nofollow" href="mailto:ale-bounces";>mailto:ale-bounces</a> at ale.org]On Behalf Of Jason
> Vinson
> Sent: Sunday, February 29, 2004 8:54 PM
> To: Atlanta Linux Enthusiasts
> Subject: Re: [ale] Software RAID Problems
>
>
> I looked in the BIOS and I don't see a setting for toggling DMA.
>
> But here's what I see from dmesg:
>
> (this is my onboard ide controller)
> ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:DMA
> ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA
>
> (and these are the Promise IDE channels)
> ide2: BM-DMA at 0xdf50-0xdf57, BIOS settings: hde:pio, hdf:pio
> ide3: BM-DMA at 0xdf58-0xdf5f, BIOS settings: hdg:pio, hdh:pio
>
> hde and hdg are my potential RAID devices, and they are set to pio. So
> is pio conflicting with DMA somehow, or should this not be affected by
> DMA at all? And isn't there a way to turn off DMA via hdparm, or will
> that not work here?
>
> Jason
>
>
> On Feb 29, 2004, at 8:28 PM, Greg wrote:
>
> > Is DMA enabled in the BIOS ? I am not sure, but perhaps you could
> > check the
> > BIOS and see if changing it would help (I have funny problems with my
> > Promise controller cards and RAID also - both under RH 7.3 and Debian
> > on the
> > same machine.).
> >
> > Greg
> >
> >> -----Original Message-----
> >> From: ale-bounces at ale.org [<a rel="nofollow" href="mailto:ale-bounces";>mailto:ale-bounces</a> at ale.org]On Behalf Of
> >> Jason
> >> Vinson
> >> Sent: Sunday, February 29, 2004 8:17 PM
> >> To: ale at ale.org
> >> Subject: [ale] Software RAID Problems
> >>
> >>
> >> I recently purchased a Promise IDE controller and I am trying to set
> >> up
> >> a 2 drive RAID set on it, but it's not cooperating. I have tried to
> >> to
> >> build the raid a few times and this is what I see, followed by a hard
> >> lockup.
> >>
> >> Feb 29 20:05:31 shosta md0: max total readahead window set to 508k
> >> Feb 29 20:05:31 shosta md0: 1 data-disks, max readahead per data-disk:
> >> 508k
> >> Feb 29 20:05:31 shosta raid1: device ide/host2/bus1/target0/lun0/part1
> >> operational as mirror 1
> >> Feb 29 20:05:31 shosta raid1: device ide/host2/bus0/target0/lun0/part1
> >> operational as mirror 0
> >> Feb 29 20:05:31 shosta raid1: raid set md0 not clean; reconstructing
> >> mirrors
> >> Feb 29 20:05:31 shosta raid1: raid set md0 active with 2 out of 2
> >> mirrors
> >> Feb 29 20:05:31 shosta md: updating md0 RAID superblock on device
> >> Feb 29 20:05:31 shosta md: ide/host2/bus1/target0/lun0/part1 [events:
> >> 00000001]<6>(write) ide/host2/bus1/target0/lun0/part1's sb offset:
> >> 78148096
> >> Feb 29 20:05:31 shosta md: ide/host2/bus0/target0/lun0/part1 [events:
> >> 00000001]<6>(write) ide/host2/bus0/target0/lun0/part1's sb offset:
> >> 78150592
> >> Feb 29 20:05:31 shosta md: syncing RAID array md0
> >> Feb 29 20:05:31 shosta md: minimum _guaranteed_ reconstruction speed:
> >> 100 KB/sec/disc.
> >> Feb 29 20:05:31 shosta md: using maximum available idle IO bandwith
> >> (but not more than 100000 KB/sec) for reconstruction.
> >> Feb 29 20:05:31 shosta md: using 508k window, over a total of 78148096
> >> blocks.
> >> Feb 29 20:05:57 shosta hde: dma_intr: status=0x51 { DriveReady
> >> SeekComplete Error }
> >> Feb 29 20:05:57 shosta hde: dma_intr: error=0x40 { UncorrectableError
> >> }, LBAsect=1139948, sector=1139840
> >> Feb 29 20:05:57 shosta end_request: I/O error, dev 21:01 (hde), sector
> >> 1139840
> >> Feb 29 20:05:57 shosta raid1: Disk failure on
> >> ide/host2/bus0/target0/lun0/part1, disabling device.
> >> Feb 29 20:05:57 shosta Operation continuing on 1 devices
> >> Feb 29 20:05:57 shosta raid1: mirror resync was not fully finished,
> >> restarting next time.
> >> Feb 29 20:05:57 shosta md: updating md0 RAID superblock on device
> >> Feb 29 20:05:57 shosta md: ide/host2/bus1/target0/lun0/part1 [events:
> >> 00000002]<6>(write) ide/host2/bus1/target0/lun0/part1's sb offset:
> >> 78148096
> >> Feb 29 20:05:57 shosta md: recovery thread got woken up ...
> >> Feb 29 20:05:57 shosta md0: no spare disk to reconstruct array! --
> >> continuing in degraded mode
> >> Feb 29 20:05:57 shosta md: recovery thread finished ...
> >> Feb 29 20:05:57 shosta md: (skipping faulty
> >> ide/host2/bus0/target0/lun0/part1 )
> >> Feb 29 20:06:01 shosta hde: dma_intr: status=0x51 { DriveReady
> >> SeekComplete Error }
> >> Feb 29 20:06:01 shosta hde: dma_intr: error=0x40 { UncorrectableError
> >> }, LBAsect=1139948, sector=1139848
> >> Feb 29 20:06:01 shosta end_request: I/O error, dev 21:01 (hde), sector
> >> 1139848
> >> Feb 29 20:06:05 shosta hde: dma_intr: status=0x51 { DriveReady
> >> SeekComplete Error }
> >> Feb 29 20:06:05 shosta hde: dma_intr: error=0x40 { UncorrectableError
> >> }, LBAsect=1139948, sector=1139856
> >> Feb 29 20:06:05 shosta end_request: I/O error, dev 21:01 (hde), sector
> >> 1139856
> >> Feb 29 20:06:25 shosta hde: dma_timer_expiry: dma status == 0x21
> >> Feb 29 20:06:35 shosta hde: error waiting for DMA
> >> Feb 29 20:06:35 shosta hde: dma timeout retry: status=0x51 {
> >> DriveReady
> >> SeekComplete Error }
> >> Feb 29 20:06:35 shosta hde: dma timeout retry: error=0x40 {
> >> UncorrectableError }, LBAsect=1139948, sector=1139864
> >> Feb 29 20:06:35 shosta end_request: I/O error, dev 21:01 (hde), sector
> >> 1139864
> >> Feb 29 20:06:45 shosta hde: irq timeout: status=0xd0 { Busy }
> >> Feb 29 20:06:45 shosta
> >> Feb 29 20:06:45 shosta PDC202XX: Primary channel reset.
> >> Feb 29 20:06:45 shosta ide2: reset: success
> >>
> >> The ide2: reset is what is most likely causing the hard lockup, but I
> >> have no idea what to do to fix this. I have tried multiple drives and
> >> different ribbon cables, and no luck. Has anyone else seen this?
> >>
> >> Jason
> >>
> >> _______________________________________________
> >> Ale mailing list
> >> Ale at ale.org
> >> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
> >>
> >
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
>
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00026" href="msg00026.html">[ale] Software RAID Problems</a></strong>
<ul><li><em>From:</em> hbbs at comcast.net (Jeff Hubbs)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Next by Date:
<strong><a href="msg00001.html">[ale] OT: One time use Digital cameras</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00026.html">[ale] Software RAID Problems</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00000"><strong>Date</strong></a></li>
<li><a href="threads.html#00000"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>