# Reuse old volume in new machine after "irrepairable hardware damage"

**URL:** <https://community.fly.io/t/reuse-old-volume-in-new-machine-after-irrepairable-hardware-damage/21230>\
**Category:** General\
**Tags:** postgres, volumes, login-only\
**Created:** [August 10, 2024, 3:12pm UTC](https://community.fly.io/t/reuse-old-volume-in-new-machine-after-irrepairable-hardware-damage/21230 "2024-08-10T15:12:19Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![mayailurus](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mayailurus/32/17593_2.png) [@mayailurus](https://community.fly.io/u/mayailurus)\
**Post date:** [August 11, 2024, 6:59pm UTC](https://community.fly.io/t/reuse-old-volume-in-new-machine-after-irrepairable-hardware-damage/21230/29 "2024-08-11T18:59:47Z")

</div>

That might actually be progress, though, since this new error is a known, fixable problem:

> [@postgres-flex: database "postgres" has a collation version mismatch](https://community.fly.io/t/postgres-flex-database-postgres-has-a-collation-version-mismatch/14391/1):
>
> Just recently a new release of postgres-flex was published. Because the Debian version of the base image has been updated, you may see a message like this: `database [DATABASE NAME] has a collation version mismatch`.
> 
> There are a few things you need to do here, but in many cases you should be able to resolve this in the following steps:

---

_[View the full topic](https://community.fly.io/t/reuse-old-volume-in-new-machine-after-irrepairable-hardware-damage/21230)._