From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Tolpin <dvd@davidashen.net>
Message-Id: <200403030918.i239IhWc097684@adat.davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] i/o error: wrenwrite
In-Reply-To: <ab9f30bf73186d530b4911d392e0640a@hamnavoe.com>
Content-Type: text/plain; charset=KOI8-R
Date: Wed,  3 Mar 2004 13:18:43 +0400
Topicbox-Message-UUID: 0f011726-eacd-11e9-9e20-41e7f4b1d025

> > When I've seen wrenwrite complaints, it has always been due to
> > about-to-fail disks.
>
> An "i/o error" report from wrenwrite is not necessarily a hardware
> problem.  It may be a failed seek because a block address in the
> filesystem has been corrupted.  This should be repairable (with some
> loss of data) by kfscmd chk.

I don't get a chance to run kfscmd check since wrenwrite are 
endlessly repeating each time I reboot system.

And when I just reboot from CD, and then c-a-d to boot from the
hard disk, everything is normal. I can reproduce it easily 
by pressing power button.

It is something to do with the state of hardware not properly
initialized. 

Is there a way to get more debugging information?

David Tolpin