# New data not being stored

**URL:** <https://forum.storj.io/t/new-data-not-being-stored/26098>\
**Category:** troubleshooting\
**Tags:** docker, database\
**Created:** [May 6, 2024, 2:51am UTC](https://forum.storj.io/t/new-data-not-being-stored/26098 "2024-05-06T02:51:07Z")\
**Posts on this page:** 1\
**Showing post:** 13

<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:** [May 7, 2024, 5:07am UTC](https://forum.storj.io/t/new-data-not-being-stored/26098/13 "2024-05-07T05:07:06Z")

</div>

This is sounds like your databases either corrupted or it’s a permissions issue.  
Could you please check your logs regarding errors related to the databases?  
I would also recommend to check them all for integrity:

> **[How to fix a "database disk image is malformed"](https://support.storj.io/hc/en-us/articles/360029309111-How-to-fix-a-database-disk-image-is-malformed)**
>
> Problem
> Sometimes a Storage Node Operator may encounter the "database disk image is malformed" error in their log. This could happen during unplanned shutdown or reboot. The error indicates that on...

Also check permissions, is your docker user able to write to them?

Regarding not updating databases on trash deletion when the lazy mode is enabled - this seems a bug:

> [@When will trash update?](https://forum.storj.io/t/when-will-trash-update/26107):
>
> My trash on many of my dashboard wont decrease even when alot of trash has been deleted. [image] Which results that i dont get any incoming data cause the nodes thinks its full. Its been over 120TB trash for over 3 weeks now.

> [@Eleos](#):
>
> This is the only type of error I am seing in the logs I believe:
> 
> ```auto
> 2024-05-06T04:28:16Z ERROR piecestore upload failed {"Process": "storagenode", "Piece ID": "7UG46IJLU3QFQP2FM47VFILTVOSCQUA7WJREXHHBR2YSLLNJIQUQ", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Remote Address": "79.127.226.102:49790", "Size": 196608, "error": "manager closed: unexpected EOF", "errorVerbose": "manager closed: unexpected EOF\n\tgithub.com/jtolio/noiseconn.(*Conn).readMsg:225\n\tgithub.com/jtolio/noiseconn.(*Conn).Read:171\n\tstorj.io/drpc/drpcwire.(*Reader).read:68\n\tstorj.io/drpc/drpcwire.(*Reader).ReadPacketUsing:113\n\tstorj.io/drpc/drpcmanager.(*Manager).manageReader:229"}
> 
> ```

this is usual the long tail cancelation, your node is slower than others. In this case this piece will be deleted and the usage will reman the same or reducing when some pieces are deleted on a TTL expiration or from the trash.

> [@Eleos](#):
>
> The screenshot shows that the average disk usage has fallen to nearly nothing. Trash also is changing since data was delete today as well. New used data still does not go up despite ingress going up.  
> ![Capture](https://storj-s3.bcdn.literatehosting.net/original/3X/5/3/53fa1e3d71692d6813da8a3938ecbb7d4cde816f.jpeg)

this info is reported by the satellites and sent to nodes with a delay up to 12 hours, please wait until tomorrow.

---

_[View the full topic](https://forum.storj.io/t/new-data-not-being-stored/26098)._