# Orthanc stopped reindexing StorageDirectory after crash — how to resume safely?
**URL:** https://discourse.orthanc-server.org/t/orthanc-stopped-reindexing-storagedirectory-after-crash-how-to-resume-safely/6308
**Category:** General
**Created:** [November 3, 2025, 2:05pm UTC](https://discourse.orthanc-server.org/t/orthanc-stopped-reindexing-storagedirectory-after-crash-how-to-resume-safely/6308 "2025-11-03T14:05:38Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@HenrikPLind](https://discourse.orthanc-server.org/u/HenrikPLind)
#### Post date: [November 3, 2025, 2:05pm UTC](https://discourse.orthanc-server.org/t/orthanc-stopped-reindexing-storagedirectory-after-crash-how-to-resume-safely/6308/1 "2025-11-03T14:05:38Z")
Hi everyone,
I’m having issues with Orthanc crashing while it was reindexing the `.dcm` files from the `StorageDirectory`.
I have a very large dataset, so this reindexing process normally takes a couple of weeks to complete.
After the crash, when I restarted Orthanc, it no longer continued reindexing. As a result, I can’t download or interact with the studies and series that haven’t yet been reindexed — Orthanc reports errors such as _“The specified path does not point to a regular file.”_
Is there any way to resume the internal indexing process from where it stopped, without starting everything over (e.g., without having to rebuild or re-import the entire dataset)?
Alternatively, is there a command or REST endpoint that can safely re-trigger this internal reindexing for the unprocessed data?
**Setup:**
- Orthanc 1.12.1 (Windows, PostgreSQL plugins)
- StorageDirectory on a network-mounted drive (`C:\SymLink\Orthanc`)
- Using the standard `indexer-plugin.db` automatically created by the PostgreSQL Indexer plugin
Best regards,
Henrik
---
### Author:  [@alainmazy](https://discourse.orthanc-server.org/u/alainmazy)
#### Post date: [November 4, 2025, 2:15pm UTC](https://discourse.orthanc-server.org/t/orthanc-stopped-reindexing-storagedirectory-after-crash-how-to-resume-safely/6308/2 "2025-11-04T14:15:32Z")
Hi,
No, there is no way to resume the indexing where it was even with the latest advanced-storage plugin.
If you really have a huge amount of data to index and want to be able to resume indexing, I would strongly recommend that you use the advanced-storage plugin and write your own python script that list the files and call `/plugins/advanced-storage/adopt-instance` for each file individually. This is actually equivalent to what the “indexer mode” is doing but you’ll have full control on it.
([Reference API](https://orthanc.uclouvain.be/book/plugins/advanced-storage.html#rest-api-extensions))
Note that I already recommended you to use the advanced-storage plugin [back in June](https://discourse.orthanc-server.org/t/help-with-index-migration-from-sqlite-to-postgresql-using-python-orthanc-tools/5930/10)
Best,
Alain