On Mon, 22 Nov 2004 19:49:36 +0100 (CET), Marco Beishuizen
<[EMAIL PROTECTED]> wrote:
> On stardate Sun, 21 Nov 2004, the wise Marco Beishuizen entered:
>
>
>
> > On stardate Sun, 21 Nov 2004, the wise Panagiotis Christias entered:
> >
> >> the only hint I could find is from the amr(4) man page:
On stardate Sun, 21 Nov 2004, the wise Marco Beishuizen entered:
On stardate Sun, 21 Nov 2004, the wise Panagiotis Christias entered:
the only hint I could find is from the amr(4) man page:
amr%d: bad slot %d completed
The controller reported completion of a command that the driver did not
issue
On stardate Sun, 21 Nov 2004, the wise Panagiotis Christias entered:
the only hint I could find is from the amr(4) man page:
amr%d: bad slot %d completed
The controller reported completion of a command that the driver did not
issue. This may result in data corruption, and suggests a hardware or
On Sat, 20 Nov 2004 15:18:27 +0100 (CET), Marco Beishuizen
<[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm having some problems with my new dual xeon with an Intel scsi raid
> controller (SRCU42X). I installed FreeBSD 5.3-RELEASE on it.
>
> First I get a message in my dmesg saying: "amr0: bad slot co
Hi,
I'm having some problems with my new dual xeon with an Intel scsi raid
controller (SRCU42X). I installed FreeBSD 5.3-RELEASE on it.
First I get a message in my dmesg saying: "amr0: bad slot completed". After
that fsck_ufs tries to run but it keeps hanging. In top it's state is
"getblk". Whe
