# Node sync fails and cluster goes to "red" **URL:** \ **Category:** Elasticsearch\ **Created:** [May 29, 2021, 7:27pm UTC](https://discuss.elastic.co/t/node-sync-fails-and-cluster-goes-to-red/274409 "2021-05-29T19:27:54Z")\ **Posts on this page:** 1\ **Showing post:** 13
**Author:** ![parthmaniar](https://avatars.discourse-cdn.com/v4/letter/p/71e660/32.png) [@parthmaniar](https://discuss.elastic.co/u/parthmaniar)\ **Post date:** [May 30, 2021, 7:06am UTC](https://discuss.elastic.co/t/node-sync-fails-and-cluster-goes-to-red/274409/13 "2021-05-30T07:06:47Z")
Thanks David. Thank you for the advise, in my case data.path and data.logs both were on separate disk that on a VM that I deleted by mistake so I reckon they were empty and waiting for be synced. I suspect disk errors would have come when I attached a new disk which took up /dev/sdb. I've run badblocks to see if I can get additional data. should I remove `cluster.initial_master_nodes` from all the nodes now or wait for full recovery before thouching those settings? Could I ask you to have a look at this: [Recent unsafe memory access operation in compiled Java code - #7 by jprante](https://discuss.elastic.co/t/recent-unsafe-memory-access-operation-in-compiled-java-code/41372/7). I feel it maybe the size of the indices that is causing the sync issue? --- _[View the full topic](https://discuss.elastic.co/t/node-sync-fails-and-cluster-goes-to-red/274409)._