[Enhancement]: complete rescan after reboot #2906

Closed
opened 2026-04-25 00:11:45 +02:00 by adam · 1 comment
Owner

Originally created by @Proxyyy87 on GitHub (Jul 19, 2025).

Type of Enhancement

None

Describe the Feature/Enhancement

I use audiobookshelf with Proxmox and if i restart the entire system with the NAS where the audiobooks are storaged, the scan after the reboot needs a long time.
Nothing has changed only the mounted folder lost for a short time the connection. If the files are on the drive with ABS it works without scan.

Why would this be helpful?

The scan needs a long time with a lot of files on the NAS.

Future Implementation (Screenshot)

Safe the Information, so no rescan is needed like the normal behavior

Audiobookshelf Server Version

2.26.1

Current Implementation (Screenshot)

No response

Originally created by @Proxyyy87 on GitHub (Jul 19, 2025). ### Type of Enhancement None ### Describe the Feature/Enhancement I use audiobookshelf with Proxmox and if i restart the entire system with the NAS where the audiobooks are storaged, the scan after the reboot needs a long time. Nothing has changed only the mounted folder lost for a short time the connection. If the files are on the drive with ABS it works without scan. ### Why would this be helpful? The scan needs a long time with a lot of files on the NAS. ### Future Implementation (Screenshot) Safe the Information, so no rescan is needed like the normal behavior ### Audiobookshelf Server Version 2.26.1 ### Current Implementation (Screenshot) _No response_
adam added the enhancement label 2026-04-25 00:11:45 +02:00
adam closed this issue 2026-04-25 00:11:45 +02:00
Author
Owner

@nichwall commented on GitHub (Jul 19, 2025):

What do the scan logs say?

You are probably running into https://github.com/advplyr/audiobookshelf/issues/1447. Audiobookshelf checks the inode to detect file moves, but this is set by the file system and are generally not stable for network drives. When you run a scan after a reboot, the server is likely updating the inodes for everything that changed (which would be everything). If the inodes/file is unchanged, then the scan completes much faster.

@nichwall commented on GitHub (Jul 19, 2025): What do the scan logs say? You are probably running into https://github.com/advplyr/audiobookshelf/issues/1447. Audiobookshelf checks the inode to detect file moves, but this is set by the file system and are generally not stable for network drives. When you run a scan after a reboot, the server is likely updating the inodes for everything that changed (which would be everything). If the inodes/file is unchanged, then the scan completes much faster.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2906