# Raid 5 failed. 3TB node dead. Recovered partially and going through GE thanks to forum

**URL:** <https://forum.storj.io/t/raid-5-failed-3tb-node-dead-recovered-partially-and-going-through-ge-thanks-to-forum/6914>\
**Category:** Node Operators\
**Tags:** raid\
**Created:** [May 18, 2020, 6:02pm UTC](https://forum.storj.io/t/raid-5-failed-3tb-node-dead-recovered-partially-and-going-through-ge-thanks-to-forum/6914 "2020-05-18T18:02:17Z")\
**Posts on this page:** 1\
**Showing post:** 72

<div class="post-metadata">

**Author:** ![SGC](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/sgc/32/1132_2.png) [@SGC](https://forum.storj.io/u/SGC)\
**Post date:** [May 20, 2020, 10:59am UTC](https://forum.storj.io/t/raid-5-failed-3tb-node-dead-recovered-partially-and-going-through-ge-thanks-to-forum/6914/72 "2020-05-20T10:59:02Z")

</div>

deleting the database is recommend procedure in many cases… such as

> [@Database disk image malformed after a crash](https://forum.storj.io/t/database-disk-image-malformed-after-a-crash/5708/4):
>
> Make sure that you used version of sqlite3 not older than v3.25.2.  
> If it’s, then your `orders.db` is heavily corrupted. In such case we will recreate it.
> 
> 1. Stop the storagenode
> 2. Remove the `orders.db`
> 3. Execute either with a local sqlite3 or with a docker:
> 
> ```auto
> sqlite3 orders.db
> CREATE TABLE unsent_order (
> satellite_id BLOB NOT NULL,
> serial_number BLOB NOT NULL,
> 
> order_limit_serialized BLOB NOT NULL, -- serialized pb.OrderLimit
> order_serialized BLOB NOT NULL, -- serialized pb.Order
> order_limit_expiration TIMESTAMP NOT NULL, -- when is the deadline for sending it
> 
> uplink_cert_id INTEGER NOT NULL,
> 
> FOREIGN KEY(uplink_cert_id) REFERENCES certificate(cert_id)
> );
> CREATE TABLE order_archive_ (
> satellite_id BLOB NOT NULL,
> serial_number BLOB NOT NULL,
> 
> order_limit_serialized BLOB NOT NULL,
> order_serialized BLOB NOT NULL,
> 
> uplink_cert_id INTEGER NOT NULL,
> 
> status INTEGER NOT NULL,
> archived_at TIMESTAMP NOT NULL,
> 
> FOREIGN KEY(uplink_cert_id) REFERENCES certificate(cert_id)
> );
> CREATE UNIQUE INDEX idx_orders ON unsent_order(satellite_id, serial_number);
> CREATE TABLE versions (version int, commited_at text);
> CREATE INDEX idx_order_archived_at ON order_archive_(archived_at);
> .exit
> 
> ```
> 
> 1. Try to start storagenode
> 2. Look into logs

so yes @BrightSilence is most certainly right that the database can be deleted if need be…  
ofc one will need to recreate it afterwards and i’m pretty sure i’ve also seen little skunk recommend removal of the database in certain cases.

---

_[View the full topic](https://forum.storj.io/t/raid-5-failed-3tb-node-dead-recovered-partially-and-going-through-ge-thanks-to-forum/6914)._