# Getting 'Failed mounting RAID volume!' - Is my data gone?

**URL:** <https://forum.scylladb.com/t/getting-failed-mounting-raid-volume-is-my-data-gone/1181>\
**Category:** ScyllaDB\
**Tags:** troubleshooting\
**Created:** [January 11, 2024, 2:21pm UTC](https://forum.scylladb.com/t/getting-failed-mounting-raid-volume-is-my-data-gone/1181 "2024-01-11T14:21:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jasper\_Visser](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/jasper_visser/32/186_2.png) [@Jasper\_Visser](https://forum.scylladb.com/u/Jasper_Visser)\
**Post date:** [January 11, 2024, 2:21pm UTC](https://forum.scylladb.com/t/getting-failed-mounting-raid-volume-is-my-data-gone/1181/1 "2024-01-11T14:21:29Z")

</div>

I am running a single self-managed Scylla instance in AWS. After running 1 week without any problems, I got this message from AWS:

> EC2 has detected degradation of the underlying hardware hosting your Amazon EC2 instance (instance-ID: i-XX).

I needed to stop-and-start my instance. After spinning the instance up again and sshed to the instance, I see it fails to boot because of this error:

> **Failed mounting RAID volume!**
> 
> Scylla has aborted startup because of a missing RAID volume.

Is there anything I can do to restart scylla with the same dataset as before the restart?

---

<div class="post-metadata">

**Author:** ![felipemendes](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/felipemendes/32/11_2.png) [@felipemendes](https://forum.scylladb.com/u/felipemendes)\
**Post date:** [January 15, 2024, 12:46pm UTC](https://forum.scylladb.com/t/getting-failed-mounting-raid-volume-is-my-data-gone/1181/2 "2024-01-15T12:46:21Z")

</div>

As we spoke in [Users Slack](https://scylladb-users.slack.com/archives/C2NLNBXLN/p1704982943777779), no – your data is gone, particularly if you are using locally attached SSDs:

> The data on an SSD instance volume persists only for the life of its associated instance.  
> [SSD instance store volumes - Amazon Elastic Compute Cloud](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ssd-instance-store.html)

---

<div class="post-metadata">

**Author:** ![Guy](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/guy/32/9_2.png) [@Guy](https://forum.scylladb.com/u/Guy)\
**Post date:** [January 16, 2024, 5:38am UTC](https://forum.scylladb.com/t/getting-failed-mounting-raid-volume-is-my-data-gone/1181/3 "2024-01-16T05:38:25Z")

</div>

Thanks @felipemendes, here is the discussion from the Slack channel:  
**Felipe:**  
Nope, AWS allocated you a new set of local SSDs. You can recreate the array and then start the replace node procedure.

**Jasper:**  
_You can recreate the array and then start the replace node procedure._ what do you mean by that? So  
the data is lost?

**Felipe:**  
in that particular node, yes. You do have other replicas, no?

**Jasper:**  
No, no other replica’s atm, it’s just for development though

**Felipe:**

> **[SSD instance store volumes - Amazon Elastic Compute Cloud](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ssd-instance-store.html)**
>
> Some Amazon EC2 instances support solid state drives (SSD) to deliver high random I/O performance.

**Jasper:**  
Ok and do you have any reference to _You can recreate the array and then start the replace node procedure.?_

**Felipe:**  
[https://opensource.docs.scylladb.com/stable/operating-scylla/procedures/cluster-management/rebuild-node.htmlhttps://opensource.docs.scylladb.com/stable/kb/raid-device.htmlDepending](https://opensource.docs.scylladb.com/stable/operating-scylla/procedures/cluster-management/rebuild-node.htmlhttps://opensource.docs.scylladb.com/stable/kb/raid-device.htmlDepending) on your ScyllaDB version you may need to manually delete the systemd `.mount` resources in your /etc and follow with a `systemctl daemon-reload` afterwards.