# \[SOLVED\] Multiple panics during initial synchronisation
**URL:** https://forum.syncthing.net/t/solved-multiple-panics-during-initial-synchronisation/16816
**Category:** Support
**Created:** [May 17, 2021, 12:47pm UTC](https://forum.syncthing.net/t/solved-multiple-panics-during-initial-synchronisation/16816 "2021-05-17T12:47:36Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@tomasz86](https://forum.syncthing.net/u/tomasz86)
#### Post date: [May 17, 2021, 12:47pm UTC](https://forum.syncthing.net/t/solved-multiple-panics-during-initial-synchronisation/16816/1 "2021-05-17T12:47:37Z")
I have just had experienced these four panics in sequence while doing the initial synchronisation between two devices. The first device is an old one, while the second one was starting from zero, i.e. everything was being downloaded from scratch.
```
[XZZTD] 2021/05/17 21:22:34 WARNING: Fatal error: bnroh-e3h4v Get(xxx): filling Blocks: open xxx\index-v0.14.0.db\001093.sst: The system cannot find the file specified.
Panic at 2021-05-17T21:22:34+09:00
panic: filling Blocks: open x: The system cannot find the file specified.
```
[panic-20210517-212234.log](https://forum.syncthing.net/uploads/short-url/tzQ26KFx5AjhGWAQIpeoZvFZZza.log) (75.0 KB)
```
[XZZTD] 2021/05/17 21:22:46 WARNING: Fatal error: bnroh-e3h4v GetGlobal(xxx): device present in global list but missing as device/fileinfo entry
Panic at 2021-05-17T21:22:46+09:00
panic: device present in global list but missing as device/fileinfo entry
```
[panic-20210517-212246.log](https://forum.syncthing.net/uploads/short-url/aeSKo0MNbqVOt80oGjGJNPrlT5X.log) (81.0 KB)
```
[XZZTD] 2021/05/17 21:33:58 WARNING: Fatal error: bnroh-e3h4v Get(xxx): filling Blocks: open xxx\index-v0.14.0.db\001371.sst: The system cannot find the file specified.
Panic at 2021-05-17T21:33:58+09:00
panic: filling Blocks: open x: The system cannot find the file specified.
```
[panic-20210517-213358.log](https://forum.syncthing.net/uploads/short-url/8OO4N5sx161QJ9bfyrX9HbAcNEI.log) (75.6 KB)
```
[XZZTD] 2021/05/17 21:34:42 WARNING: Fatal error: bnroh-e3h4v GetGlobal(xxx): device present in global list but missing as device/fileinfo entry
Panic at 2021-05-17T21:34:42+09:00
panic: device present in global list but missing as device/fileinfo entry
```
[panic-20210517-213442.log](https://forum.syncthing.net/uploads/short-url/4QdCQdcZwThGtnyEQqk8jyUc38r.log) (90.6 KB)
I have wiped the database since then, and now I’m doing a second trial, but I have no idea what the culprit might have been. I can only say that the hardware itself is in good shape and 100% stable.
**Edit** : I forgot to mention that this is Syncthing v1.16.0 with a couple of minor custom changes, and also with [https://github.com/syncthing/syncthing/commit/0d054f9](https://github.com/syncthing/syncthing/commit/0d054f9) cherry-picked on top of it.
---
### Author:  [@imsodin](https://forum.syncthing.net/u/imsodin)
#### Post date: [May 17, 2021, 1:09pm UTC](https://forum.syncthing.net/t/solved-multiple-panics-during-initial-synchronisation/16816/2 "2021-05-17T13:09:52Z")
The first and third panic is the database panicking because it is missing an internal file on disk, i.e. something in index-v0.14.0.db got deleted (or the db is otherwise corrupted). Everything else is likely just an effect/consequence of said corruption.
Usually db corruption implies bad storage, but a missing file sounds more like something else meddling with the directory the db is stored in.
---
### Author:  [@tomasz86](https://forum.syncthing.net/u/tomasz86)
#### Post date: [May 17, 2021, 5:36pm UTC](https://forum.syncthing.net/t/solved-multiple-panics-during-initial-synchronisation/16816/3 "2021-05-17T17:36:30Z")
Yeah, I’m not sure what exactly had happened, but I removed all folders, restarted from scratch, and everything has synced properly this time 👍.
---
### Author:  [@system](https://forum.syncthing.net/u/system)
#### Post date: [June 16, 2021, 5:36pm UTC](https://forum.syncthing.net/t/solved-multiple-panics-during-initial-synchronisation/16816/4 "2021-06-16T17:36:32Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.