DB main.songs_fts not found

[Alcyon007]

Describe the bug
Once scan stops, it becomes impossible to continue scanning the paths to the music on the music-server, even in version 62.

To Reproduce
Steps to reproduce the behavior:

1. audiomuse-ai-musicserver first start
2. add 2 paths
3. scan first path - Scan in Progress in counting and new songs are found
4. cancel the scan
5. scan the second path - Scan in Progress is freeze.

Log info on restart:

=== AudioMuse Music Server Container Starting ===
=== Starting Supervisor ===
Music Server Backend will be available on port 8080
Music Server Frontend will be available on port 3000
All logs will be displayed below:
2026/05/02 01:05:33 DB integrity check OK
2026/05/02 01:05:33 Checking/Updating album_path for existing songs...
2026/05/02 01:05:33 migrateDB: warning - could not create songs_fts virtual table (fts5 may be unavailable): no such module: fts5
2026/05/02 01:05:33 migrateSongIDsToUUID: songs.id is already TEXT, migration complete
2026/05/02 01:05:33 migrateDB: failed to backfill date_added: no such table: main.songs_fts
2026/05/02 01:05:33 migrateDB: failed to backfill date_updated: no such table: main.songs_fts
2026/05/02 01:05:33 migrateDB: summary: columns_added=0 songs_migrated=0 date_added_backfilled=0 date_updated_backfilled=0
2026/05/02 01:05:33 migrateDB: completed migrations (idempotent)
2026/05/02 01:05:33 Scheduled library scan is disabled.
2026/05/02 01:05:33 Scheduled analysis is disabled.
[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.

• using env: export GIN_MODE=release
• using code: gin.SetMode(gin.ReleaseMode)

Expected behavior
Full scan or path scan should continue where it left and go on.

Screenshots
None.

Environment
Proxmox clusters v9.1.9

• 1st node, LXC (audiomuser-music-server)

• 2nd node, LXC (Worker)

  OS: [Debian]
  Deployment: [Docker Compose]
  AudioMuse-AI Version: [v1.0.4.0]
  Lyrion Music Server Version : 9.1.0 - 1771315634 @ Thu Feb 19 13:51:07 UTC 2026
  Browser: [Firefox 150.0.1 (64 bits)]
  HP Z4 G4 Workstation, 3,60 gigahertz Intel Xeon W-2133, Multi-core (6 total) Hyper-threaded (12 total) - 12 cores dedicated to worker
  RAM: [8+2 GB (of 128 GB) DDR4]
  Disk: [Nvme]

[Alcyon007]

Hi,

Situation remains the same with update 63.

Thank you for your helpful advice.

[NeptuneHub]

Basically I was using an FTS5 index to have faster search2 and search3 query, but it was broken.

I did some fix and start the build of the version 64, it should be ready in 30-60 minutes. Please update, restart the container and run a new scan. It should fix the issue, if not, please share the updated log.

Thanks.

[Alcyon007]

Hello, and thank you for fixing the bug!
It is now possible to scan the music collection in multiple passes.

However, I’ve noticed that the ALBUM report fails to display all albums when the “All Genres” category is selected (example: total number of albums = 2,185, number of album covers displayed for “All Genres” = 9).

Thanks.

[NeptuneHub]

Can you explain it better? Can you explain step by step what you do ?
You directly go on the album section, and moving the filter it show only 9 when instead count more ?

[Alcyon007]

1. Log into audiomuse-ai-musicserver
2. Add a path with a substancial number of music files
3. Start New Analysis
4. Start Clustering
5. Clic on ALBUM
6. Select a music genre
7. Note the total number of albums displayed numerically in the upper-left corner of the window
8. Count the albums displayed visually

The two values should match (as far as I understand)

[NeptuneHub]

I decided that I don't want to become crazy with Artist and Album view and from now on this will be removed from frontend.

The reason are multiple:

• AudioMuse-Ai Music server core is Sonic Analysis, that is a totally different way of navigate your music. You have a song in mind, you type and from that song you start creating similar one. No metadata anymore that can be wrong.
• Wrong metadata also means that the music server need to have multiple fallback logic to show Artist and Album view. This make everything complicated and erorr prone.

I know that someone could not like this decision, but I want to do something different. That could be good or bad but different.
Next release will not have anymore those view so I'm going to clsoe this issue as unpplanned.