Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Dec 2008 12:21:31 +0300
From:      Artem Kuchin <matrix@itlegion.ru>
To:        Mel <fbsd.questions@rachie.is-a-geek.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: 3ware array access lock up on 7.1-RC
Message-ID:  <4958969B.8000404@itlegion.ru>
In-Reply-To: <200812271041.39903.fbsd.questions@rachie.is-a-geek.net>
References:  <49551091.5000009@itlegion.ru> <200812271041.39903.fbsd.questions@rachie.is-a-geek.net>

next in thread | previous in thread | raw e-mail | index | archive | help


Mel =D0=C9=DB=C5=D4:
> On Friday 26 December 2008 08:12:49 Artem Kuchin wrote:
>  =20
>> I am not even sure that it is related to freebsd, but maybe someone co=
uld
>> point out the problem.
>>
>> We wanted to upgrade our hosting server from
>> FreeBSD 6.2, 3ware 8506-4LP SATA RAID, raid 5
>> to
>> FreeBSD 7.1 (RC for now), 9550SXU-4LP, raid 10
>>
>> We have tested the new installation on ASUS P5K WS motherboard
>> with PCI-X slot while the server kept running.
>>
>> The server has Supermicro X5DPE-G2  (pretty old one, 2004).
>>
>> So, when everything was ready, i just took out the old controller and
>> disks and installed the new controller and the array disks.
>>
>> The system booted up, but when i started very intense file operations
>> the file
>> system just froze. The weird thing is that any open program which does=

>> not use
>> filesystem kept running fine. For example, i could type and edit in op=
en
>> ee editor,
>> but copying progress bar in midnight commander just stood still. If i
>> tried to save file
>> or open file or do anything disk related from ee in another console th=
e
>> program froze too,
>> apparently waiting for disk system to reply forever (i tried waiting f=
or
>> 20 minutes).
>> I could even connect to ssh port, but it does not auth because sshd
>> needs to read something
>> from the disk.
>> I put everything back into Asus P5K WS and tested it. Everything worke=
d
>> fine again.
>>
>> Any idea what might going on here?
>>    =20
>
> OS bugs aside, a dead disk that keeps getting IO request explains all=20
> symptoms. Dead can also mean, faulty cable, buggy connector. I would ex=
pect=20
> the hardware raid controller to pick up on it though and remove it from=
 the=20
> array.
>  =20
No, not the case here. As i said, the same controller with the same=20
disks work perfectly on ASUS motherboard.


--
Artem




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4958969B.8000404>