# Ordersdb error: database disk image is malformed

**URL:** <https://forum.storj.io/t/ordersdb-error-database-disk-image-is-malformed/2701>\
**Category:** troubleshooting\
**Tags:** docker, database, unraid\
**Created:** [November 20, 2019, 5:49am UTC](https://forum.storj.io/t/ordersdb-error-database-disk-image-is-malformed/2701 "2019-11-20T05:49:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [November 20, 2019, 9:07am UTC](https://forum.storj.io/t/ordersdb-error-database-disk-image-is-malformed/2701/4 "2019-11-20T09:07:36Z")

</div>

Unfortunately, the problem is in the Unraid platform, your databases will be corrupted again and again, until you downgrade the Unraid to v6.6.7 or moved from it to any other system.

> [@Database disk image is malformed - Error coming from nowhere](https://forum.storj.io/t/database-disk-image-is-malformed-error-coming-from-nowhere/1968):
>
> I’ve had this problem before when stopping the Storj docker with to low timeout and getting the Database disk image is malformed error, but recently i got it from nowhere. Here’s some logs when it happened: 2019-09-27T21:54:03.339Z e[34mINFOe[0m piecestore downloaded {"Piece ID": "L5WA75AKNLXV4EFN5EIV5HB4TWDE7MKPDRKAOQSIC5EZKSAXRZ6Q", "SatelliteID": "118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW", "Action": "GET"} 2019-09-27T21:54:31.519Z e[34mINFOe[0m piecestore upload started {"Piece ID"…

About timeout option it should be `-t 300`, not `t-300`. For example, to graceful stop the container:

```auto
docker stop -t 300 storagenode

```

In case of Unraid you should use their package manager, the `apt` only for Debian-based. So the more simple way is to use a docker-way, which described in the same article.

---

_[View the full topic](https://forum.storj.io/t/ordersdb-error-database-disk-image-is-malformed/2701)._