starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Bug]: Unraid HDD wakes up from standby when Audiobookshelf ui (and library) is opened #3059

New Issue
Open
opened 2026-04-25 00:13:20 +02:00 by adam · 1 comment
adam commented 2026-04-25 00:13:20 +02:00
Owner
Copy Link
Copy Source

Originally created by @inject3d on GitHub (Oct 28, 2025).

What happened?

With Unraid I have a nvme for appdata where audiobookshelf with metadata is stored. media is stored on cache and hdd. Primarily, the cache is accessed first, hdd stays in standby most of the time.

But when audiobookshelf is opened and I guess the library overview is accessed the HDD spins up. It seams that it tries to read through the media folder.

What did you expect to happen?

I would expect that audiobookshelf only accesses the metadata from the appdata folder which is stored on the nvme and I would expect that it only spins up if media is accessed or the filesystem detects a change or a period check is running. (which was disabled)

During that time I did not press play or anything. There was one book which I could continue reading but it is not active.

Steps to reproduce the issue

  1. Open audiobookshelf
  2. Open library

Audiobookshelf version

2.30

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

If the issue is being seen in the UI, what browsers are you seeing the problem on?

Chrome

Logs

Additional Notes

No response

Originally created by @inject3d on GitHub (Oct 28, 2025). ### What happened? With Unraid I have a nvme for appdata where audiobookshelf with metadata is stored. media is stored on cache and hdd. Primarily, the cache is accessed first, hdd stays in standby most of the time. But when audiobookshelf is opened and I guess the library overview is accessed the HDD spins up. It seams that it tries to read through the media folder. ### What did you expect to happen? I would expect that audiobookshelf only accesses the metadata from the appdata folder which is stored on the nvme and I would expect that it only spins up if media is accessed or the filesystem detects a change or a period check is running. (which was disabled) During that time I did not press play or anything. There was one book which I could continue reading but it is not active. ### Steps to reproduce the issue 1. Open audiobookshelf 2. Open library ### Audiobookshelf version 2.30 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Linux ### If the issue is being seen in the UI, what browsers are you seeing the problem on? Chrome ### Logs ```shell ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:13:20 +02:00
adam commented 2026-04-25 00:13:20 +02:00
Author
Owner
Copy Link
Copy Source

@inject3d commented on GitHub (Oct 28, 2025):

Just found a similar discussion here https://github.com/advplyr/audiobookshelf/discussions/3900

@inject3d commented on GitHub (Oct 28, 2025): Just found a similar discussion here https://github.com/advplyr/audiobookshelf/discussions/3900
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#3059
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?