# Unassigned primary shards not found **URL:** \ **Category:** Elasticsearch\ **Created:** [June 6, 2016, 9:27am UTC](https://discuss.elastic.co/t/unassigned-primary-shards-not-found/51917 "2016-06-06T09:27:15Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![anon45667325](https://avatars.discourse-cdn.com/v4/letter/a/d78d45/32.png) [@anon45667325](https://discuss.elastic.co/u/anon45667325)\ **Post date:** [June 6, 2016, 9:27am UTC](https://discuss.elastic.co/t/unassigned-primary-shards-not-found/51917/1 "2016-06-06T09:27:15Z")
Hello, I'm actively trying to move from Elasticsearch 1.6 to 2.3. I was trying to snapshot my indices to prepare the migration but my backup system failed at the wrong time and my ES cluster had to be stopped due to non-stop timeouts. After a full cluster restart, some of my indices are red and I can't seem to find them again: All of them are primary shards. { "status" : "red", "timed\_out" : false, "number\_of\_nodes" : 5, "number\_of\_data\_nodes" : 5, "active\_primary\_shards" : "active\_shards" :, "relocating\_shards" : 0, "initializing\_shards" : 0, **"unassigned\_shards" : 54,** "number\_of\_pending\_tasks" : 0, "number\_of\_in\_flight\_fetch" : 0 } Shard allocation is correctly enabled on all the machines I've tried to POST a reroute but without success. When trying the \_recovery option on the bad indices, the missing shards do not even appear on the returned JSON. Is there something I'm missing ? Best regards UPDATE: The data is definitely on the nodes, I can see the folders with the id of the missing shards. Is there an API call to verify data on disks to force check the shards availability ? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:46pm UTC](https://discuss.elastic.co/t/unassigned-primary-shards-not-found/51917/2 "2017-07-05T22:46:00Z")