9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: arisawa@ar.aichi-u.ac.jp
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work
Date: Wed,  6 Feb 2008 11:01:08 +0900	[thread overview]
Message-ID: <5DFC3899-70F3-4B08-A4CB-3875746B8DC2@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <47A81BCD.9040109@gmx.de>

Hello,

I had a similar phenomenon with VB7001G using two SATAs(IDE mode).
Second SATA is unstable but I don't know where the problem comes from.
Plan 9 under single SATA(IDE mode) works fine.

Kenji Arisawa


On 2008/02/05, at 17:18, Kernel Panic wrote:

> Hello,
>
> I purchased an C7 based machine with VIA VT8237 SATA/RAID:
>
> http://www2.digitalo.de/
> deeplink.jsp;jsessionid=0FEFF78E7DE9EC893CD54A5B75AA7B60?
> PROD=948733&EXT=SHOPPING
>
> Have 2 SATA disks attached. They are detected like normal IDE devices.
> The Installation of Plan9 worked fine. Created partitions and #k
> mirror and setup
> venti. I wanted to copy the arenas of my old fileserver to it and
> then later format
> fossil with the last score, but the machine fails before finishing/
> reading the first
> arena. :-(
>
> First, i found that DMA was disabled for both drives, so i forced
> it on with:
> echo dma on >/dev/sdC0/ctl
> echo dma on >/dev/sdD0/ctl
>
> ...then i get i/o errors in venti and plan9 paniced. so this was
> not such a good idea i guess...
> reformated all venti partitions and tried again several times with
> different bios options
> (without DMA, tried both bios SATA IDE and SATA RAID mode):
>
> - after hours of disk activity, sdD0 failed... i tried to read /dev/
> sdD0/data and got i/o error instantly and
> after reboot worked again.
>
> - after hours of disk activity, i see i/o-error that it cant read /
> dev/sdD0/9hal.vtbloom
> (venti bloomfilter partition 64MB). and then crashed with poolpanic.
>
> http://plan9.bell-labs.com/wiki/plan9/Supported_PC_hardware/
> index.html shows that this
> controller should work but it doesnt for me currently.
>
> pci -v shows the as same ids as in the sdata.c driver.
>
> Is anybody using that sata controller? (with multiple SATA disks?)
> Do i miss here something?
> Are here any special BIOS options i need to get this working?
>
> cinap


  parent reply	other threads:[~2008-02-06  2:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05  8:18 Kernel Panic
2008-02-05  8:54 ` Lorenzo Fernando Bivens de la Fuente
2008-02-05 13:20 ` erik quanstrom
2008-02-05 19:48 ` Robert Raschke
2008-02-06  2:01 ` arisawa [this message]
2008-02-05 22:13 cinap_lenrek
2008-02-06  8:41 ` Kernel Panic
2008-02-06  9:45   ` erik quanstrom
2008-02-06 10:43     ` Kernel Panic
2008-02-06 11:03       ` erik quanstrom
2008-02-06 17:58 [9fans] usb ohci support arrives -- another caution Sape Mullender
2008-02-06 19:23 ` [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work cinap_lenrek
2008-02-06 20:04   ` erik quanstrom
2008-02-06 22:29     ` cinap_lenrek
2008-02-06 22:40       ` erik quanstrom
2008-02-06 23:26         ` cinap_lenrek
     [not found] <54b639a7eb08c31e4ef2a6d9fd7b6a62@quanstro.net>
2008-02-08  9:35 ` Kernel Panic
2008-02-08 14:55   ` erik quanstrom
2008-02-08 14:56   ` Robert Raschke
2008-02-08 15:27     ` Robert Raschke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5DFC3899-70F3-4B08-A4CB-3875746B8DC2@ar.aichi-u.ac.jp \
    --to=arisawa@ar.aichi-u.ac.jp \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).