also sprach Daniel Bareiro daniel-lis...@gmx.net [2010.08.02.1510 +0200]:
When I tried to add sdb3 was because the disk for some reason did not
appear with cat /proc/mdstat (not even like it was failed), although
when using mdadm --detail /dev/md2 appear as both sdd3 and sdb3 as
removed. To
also sprach Daniel Bareiro daniel-lis...@gmx.net [2010.08.02.0420 +0200]:
md2 : active raid5 sda3[0] sdd3[4](F) sdc3[2]
2136170880 blocks level 5, 64k chunk, algorithm 2 [4/2] [U_U_]
[…]
That is to say, the RAID has four disks and failed both the spare
disk and other disk from array.
Hi, Martin.
On Monday, 02 August 2010 08:30:03 +0200,
martin f krafft wrote:
also sprach Daniel Bareiro daniel-lis...@gmx.net [2010.08.02.0420 +0200]:
md2 : active raid5 sda3[0] sdd3[4](F) sdc3[2]
2136170880 blocks level 5, 64k chunk, algorithm 2 [4/2] [U_U_]
[…]
That is to say,
Hi all!
On the day I found this e-mail notification of fail event from mdadm:
-
This is an automatically generated mail message from mdadm
running on antares
A Fail event had been detected on md device /dev/md2.
It could be
4 matches
Mail list logo
