Whizz Kid
Second question: If we rebuild the active primary node, should we stop the replication task? Because if the rebuild fails on primary node and data/raid is completely broken (desaster), is there a side effect on secondary node - broken data on sec. node? Or are data on sec. node absolutely save?
regards,
Lukas
descience.NET
Dr. Lukas Pfeiffer
A-1140 Wien
Austria
www.dotnethost.at
DSS v6 b4550 iSCSI autofailover with Windows 2008 R2 failover cluster (having still some issues with autofailover).
2 DSS: 3HE Supermicro X7DBE BIOS 2.1a, Areca ARC-1261ML FW 1.48, 8x WD RE3 1TB, 1x Intel PRO1000MT Dualport, 1x Intel PRO1000PT Dualport.
2 Windows Nodes: Intel SR1500 + Intel SR1560, Dual XEON E54xx, 32 GB RAM, 6 NICs. Windows Server 2008 R2.
Member
hi,
from my experience you should start failover, never work with open-e storage thats rebuild. shutdown the primary and do the rebuild within the bios setup of your controller.
after that start open-e on the primary and start resync. if there are any errors you must clear the metadata on the primary and to a full sync.
i had very very bad experience with rebuild on open-e with adaptec and raid6...
have a look at this thread
http://forum.open-e.com/showthread.php?t=1991
and this error still exist in open-e/adaptec! and should be fixed in one of the next releases...
greetings
roger
Whizz Kid
thanx for quick reply! ok, I will do failover to sec. DSS first, than I run rebuild on primary via RAID controller console. We don't use Adaptec, we use Areca and I hope that there are no such issues.
BTW: We had also a failed HDD on secondary DSS, we made rebuild without issues on running sec. DSS.
We also use WD RE3 1TB HDDs like you - do you have bad experience with that HDDs? 2 failed HDDs in that short time is not good ...
regards,
Lukas
descience.NET
Dr. Lukas Pfeiffer
A-1140 Wien
Austria
www.dotnethost.at
DSS v6 b4550 iSCSI autofailover with Windows 2008 R2 failover cluster (having still some issues with autofailover).
2 DSS: 3HE Supermicro X7DBE BIOS 2.1a, Areca ARC-1261ML FW 1.48, 8x WD RE3 1TB, 1x Intel PRO1000MT Dualport, 1x Intel PRO1000PT Dualport.
2 Windows Nodes: Intel SR1500 + Intel SR1560, Dual XEON E54xx, 32 GB RAM, 6 NICs. Windows Server 2008 R2.
Whizz Kid
RAID rebuild on prim.. node succeeded in about 4 hours.
Has anyone else troubles with WD RE3 HDDs (WD1002FBYS - 01A6B0)?? Our defective HDDs are production date Sep 2008 and Feb 2009 ...
regards,
Lukas
descience.NET
Dr. Lukas Pfeiffer
A-1140 Wien
Austria
www.dotnethost.at
DSS v6 b4550 iSCSI autofailover with Windows 2008 R2 failover cluster (having still some issues with autofailover).
2 DSS: 3HE Supermicro X7DBE BIOS 2.1a, Areca ARC-1261ML FW 1.48, 8x WD RE3 1TB, 1x Intel PRO1000MT Dualport, 1x Intel PRO1000PT Dualport.
2 Windows Nodes: Intel SR1500 + Intel SR1560, Dual XEON E54xx, 32 GB RAM, 6 NICs. Windows Server 2008 R2.
Member
hi,
sorry for my late reply.
we had 2 defective drives nearly on the same day. the same as you have. first on the primary and second on the slave.
we use 52 drives of these model and 2 defective drives in 36 months, i think thats ok.
and grats to your successfull rebuild :-)
roger
Whizz Kid
I checked both defective drives with the WD Data LifeGuard Diagnostics Tool and both drive are healthy and error-free ...!? Why they failed in RAID? Should I however return the drives to WD (RMA)?
regards,
Lukas
descience.NET
Dr. Lukas Pfeiffer
A-1140 Wien
Austria
www.dotnethost.at
DSS v6 b4550 iSCSI autofailover with Windows 2008 R2 failover cluster (having still some issues with autofailover).
2 DSS: 3HE Supermicro X7DBE BIOS 2.1a, Areca ARC-1261ML FW 1.48, 8x WD RE3 1TB, 1x Intel PRO1000MT Dualport, 1x Intel PRO1000PT Dualport.
2 Windows Nodes: Intel SR1500 + Intel SR1560, Dual XEON E54xx, 32 GB RAM, 6 NICs. Windows Server 2008 R2.
Member
absolutely you should!
we always send them back, there is alway a reason for failure in an raid system.
Posting Permissions
Reply With Quote