From: <pt@procomnet2.prograine.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Intel SRCU3-1 RAID (I2O) and 2.4.5-ac18
Date: Wed, 4 Jul 2001 16:11:54 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.33.0107041550300.23057-100000@procomnet2.prograine.net> (raw)
> modprobe i2o_config
> may be needed
Yes of course, why didn't I think about it...
Anyway, the cgi tool doesn't seem to identify any problems with
the controller before the freeze. Then it freezes together with
the copying process. And after reboot I see errors in the
controller's log - they are all exactly same:
Function: Media Unlock
Error Code: Access Violation
User Info: 00000000
Disk Serial No is not set, just no data in the table field
Timestamps are somewhat strange - three erroror logs one after
another then about 3-4 minutes delay and again three messages
The RAID volume sometimes enters a state after reboot where all
three disks are working and the cgi says the volume is
initializing.
Przemek Tomala
next reply other threads:[~2001-07-04 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 14:11 pt [this message]
2001-07-04 14:16 ` Intel SRCU3-1 RAID (I2O) and 2.4.5-ac18 Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-07-02 8:11 pt
2001-07-02 10:18 ` Alan Cox
2001-06-30 5:41 pt
2001-06-30 7:20 ` Alan Cox
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=Pine.LNX.4.33.0107041550300.23057-100000@procomnet2.prograine.net \
--to=pt@procomnet2.prograine.net \
--cc=linux-kernel@vger.kernel.org \
/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).