<p>This is the right procedure, although you could have tried a <code>reindex-chainstate</code> first since the corruption looks related to the chainstate. It is faster since it only rebuilds the UTxOs index, without the blocks index.</p>
<p>It's to be expected that the reindex takes in the order of hours or days depending on your machine. The number of <code>blk*****.dat</code> varies, but after 11 hours and being at the <code>3375</code>th <code>blk</code> file you are probably close to completion. A more accurate way of tracking the progress would be to look at the <code>debug.log</code>'s <code>UpdateTip</code> messages.</p>

CC BY-SA 4.0
2023-05-02T12:56:34.013Z
2023-05-02T12:56:34.013Z
Antoine Poinsot
<p>After a power outage, starting bitcoind I recieved this errors (circled in the image). Reading online some users suggest to do a reindex and i did it but after 11 hours my node isn't reindex yet... The process is still going on about the file <code>blk03375.dat</code>. How many blk*.dat it have to reindex? Is this the right procedure for my error?
<a href="https://i.sstatic.net/hE8G3.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/hE8G3.jpg" alt="errors" /></a></p>

<bitcoin-core><bitcoind><full-node><error><leveldb>
LevelDB error after power outage
Niko
# LevelDB error after power outage

(Asked by: username_0 on 2023-05-02)

After a power outage, starting bitcoind I recieved this errors (circled in the image). Reading online some users suggest to do a reindex and i did it but after 11 hours my node isn't reindex yet... The process is still going on about the file `blk03375.dat`. How many blk\*.dat it have to reindex? Is this the right procedure for my error?
[![errors](https://i.sstatic.net/hE8G3.jpg)](https://i.sstatic.net/hE8G3.jpg)

**Tags:** bitcoin-core, bitcoind, full-node, error, leveldb


---

## 1 answers

### Answer by username_1 on 2023-05-02. Score: 1 | Accepted answer

This is the right procedure, although you could have tried a `reindex-chainstate` first since the corruption looks related to the chainstate. It is faster since it only rebuilds the UTxOs index, without the blocks index.

It's to be expected that the reindex takes in the order of hours or days depending on your machine. The number of `blk*****.dat` varies, but after 11 hours and being at the `3375`th `blk` file you are probably close to completion. A more accurate way of tracking the progress would be to look at the `debug.log`'s `UpdateTip` messages.


---

