[DSS6] Primary Disk Activity HALTS when Secondary crashes

[Roeller]

Thanks for the info Todd,

I'm trying to remember the situation:
- Customer was using version 6.0up95.xxxx.6156 (2012-04-05)
- The Primary was master and the Secondary was slave.
- The secondary was had a RAID-5 volume and 2 disks were pulled out, so the volume 'Failed'. The Areca card probably gave 'failed' back to the Operating System and you couldn't see any volumes in Open-E.

What I am saying is: The secondary was still running but it's raid-set failed so the volumes were gone. Could this trigger a situation in which the Primary would stay waiting for an acknowledge? (The heartbeat and all other processes were still running and successfull I guess). I am just thinking about a 'secondary is half alive' scenario..

-Roel

[To-M]

We would have to look at the logs but most likely the Primary noticed that the secondary was dead and placed itself in a degraded state. Also I recommend to use build 6335 6135 was pulled off, not due to the Auto Failover.